China Drone Delivery’s Evidence of Activation: CAAC Standards Turn IDs Into Dispatch Readiness

A dispatch clock now starts at activation

On paper, drone delivery has always hinged on permissions: you fly, you operate within an authorization, you keep records. In China, the new center of gravity is different. CAAC’s mandatory national standards require real-name registration and activation controls that make unmanned aircraft inoperable before activation and inoperable again after deactivation—turning operator identity status into a gate that must hold up at dispatch. (CAAC, 2025-12-24; SCIO, 2025-12-10)

That is why “evidence of activation” matters. When operational identification specifications demand continuous identity, location, speed, and status reporting during startup and throughout flight, the compliance question shifts from “Do we have permission for the route?” to “Was the fleet activation state correct, and did identification reporting function continuously from takeoff through landing?” (CAAC, 2025-12-24; China Daily, 2025-12-11)

For commercial drone delivery operators, this is operational redesign, not paperwork. You are not simply maintaining a pilot’s file and a flight log. You are building a workflow that can prove, on demand, that identification readiness and activation state were aligned with operational permission submissions—and that the fleet behaved like a regulated system, not a collection of launches. In fast-scaling delivery networks, the downside arrives early: one “unactivated” aircraft can become a network-wide delay.

What the CAAC shift changes

CAAC says two mandatory national standards have been approved and released under SAMR’s standardization framework: one for “Requirements for Real-Name Registration and Activation of Civil Unmanned Aircraft,” and one for “Specifications for the Identification of Civil Unmanned Aircraft System Operations.” Both are set to take effect on May 1, 2026. (CAAC, 2025-12-24; SCIO, 2025-12-10)

The “real-name registration and activation” standard is explicit about functional control: a drone must be inoperable before activation and inoperable after deactivation. Activation is therefore not an internal checkbox, but a system property that can be checked—and it changes delivery operations by making dispatch contingent on activation state confirmation, not just registration completion. (SCIO, 2025-12-10)

Meanwhile, the “operational identification” specification reframes identification from a “broadcast feature” into an operational requirement. Media reporting describes automatic transmission of identity, location, speed, and status information to regulators upon startup and throughout the flight process, enabling real-time management of flight activities. (China Daily, 2025-12-11)

Together, the two standards create a new operational logic for delivery-by-drone:

1. Registration and activation must be correct before a drone can be considered dispatch-ready.
2. Identification must be functioning continuously through flight to provide the operational evidence regulators expect.
3. Activation and identification readiness must become workflow steps on the dispatch line, not isolated pilot checks.

Evidence of activation becomes proxy airworthiness

Airworthiness is traditionally a model-level question: is the aircraft certified and fit for service? In China’s delivery context, “evidence of activation” functions as a proxy airworthiness signal for sandbox-scale launches. Activation gating and identification reporting are required system behaviors that regulators can interpret as operational fitness for lawful flight.

The operational identification specification is also described as requiring rolling storage of operational identification information, with flight record storage capacity for not less than 120 flight hours and a rolling update interval not greater than 10 seconds. Even if a company never hears the word “audit,” the storage requirement changes how compliance evidence is engineered—driving how operators design data retention, retrieval, and system integrity checks. (GB 46750-2025 PDF excerpt)

CAAC’s communication also supplies sector scale indicators. It states that in 2024 nearly 20,000 entities obtained UAV operation certificates, the number of registered UAV exceeded 2 million, and cumulative annual flight hours within the statistical scope surpassed 26 million hours, with up to 26,000 UAVs simultaneously in the air. Those figures explain why regulators are moving from fragmented enforcement toward standardized operational traceability at scale. (CAAC, 2025-12-24)

What operators must operationalize is the linkage: if operational permission submissions are built on identification and activation status, then compliance becomes a chain-of-custody workflow—activation state confirmation, identification module function checks, startup-to-landing evidence continuity, and post-flight record availability. Treat activation readiness as “someone in the team will handle it,” and scaling delivery will force you into standardized operational controls.

Map activation states to dispatch permission

The standards do not only demand compliance; they demand a specific way of demonstrating it. Because activation can render aircraft inoperable before activation and after deactivation, operators must treat activation as a state machine and map it to operational permission submissions and mission scheduling. (SCIO, 2025-12-10)

“Dispatch-line workflow” replaces “pilot-level process.” A delivery network is effectively a just-in-time dispatch system: the compliance decision must be made right before launch, using evidence that is time-stamped and auditable.

Operationally, the mapping can be framed as a control loop with four checkpoints that must agree:

• Permission context: which operational permission (route, time window, sandbox scope, and operator identity) the mission is scheduled under.
• Activation context: whether the specific airframe is currently in the “active/operable” state required by the real-name registration and activation standard.
• Identification continuity context: whether the identification module is ready at startup and continues producing identification data at the required update cadence through landing.
• Evidence continuity context: whether recorded identification information is retrievable for the required retention window (not less than 120 flight hours) for later regulator review.

To operationalize this, companies typically need to:

• Create pre-dispatch check gates that verify activation status for each airframe before mission assignment (not just before takeoff), then hard-block assignment if activation state evidence cannot be produced for the exact airframe and timestamp.
• Bind mission logs to aircraft identity and activation timestamps so evidence can be reconstructed as a timeline linking permission submission → activation confirmation → startup identification behavior → landing and record retention availability.
• Treat identification readiness as a runtime requirement. Operational identification specifications require startup-through-landing reporting, not a one-time setup; “ready” means the system can generate identification information at launch and maintain the rolling update interval (no more than 10 seconds) until mission completion, with records stored to satisfy the 120-flight-hour rolling retention constraint.

Quantitatively, the evidence design now has hard constraints. Rolling storage for at least 120 flight hours and an update interval not exceeding 10 seconds mean operators must budget storage systems, define retention windows, and implement retrieval logic that supports regulator-style requests. (GB 46750-2025 PDF excerpt)

A subtle but important point follows: if dispatch software can schedule missions before activation completes, a “permission exists but activation was wrong” scenario can create enforcement exposure. Evidence of activation becomes the compliance center of gravity because it makes dispatch-time controls part of regulatory defensibility.

Real-world case signals for delivery firms

These standards are new, so delivery firms’ readiness should be read through documented sandbox participation and operationalization decisions that preceded May 1, 2026.

One signal comes from Hong Kong’s low-altitude regulatory sandbox. SF Express-linked operations offer a visible cue that delivery operators are treating regulatory proof and operational readiness as inseparable. The company announced a collaboration with Phoenix Wings for cargo drones in a sandbox context. Phoenix Wings is described as having obtained CAAC’s nation’s first pilot license for drone aviation operations in 2018, with a rural logistics validation site in Ganzhou. That timeline matters because it shows an early linkage between delivery pilots and CAAC-regulated permission pathways. (S.F. Express HK, 2025-04-17)

Another signal is CAAC’s research reporting on low-altitude connected drone safety testing. In a CAAC-published report describing a low-altitude connected drone flight safety test, it explains that identity registration was performed via a drone manufacturer app, including personal identity information (name, ID card number, phone number, address). While this is not the same as the 2026 mandatory national standards, it demonstrates that CAAC has long been thinking in terms of how identity-linked systems feed into operational supervision. For delivery operators, it supports the inference that regulators expect identity-linked systems to be operationally connected, not siloed. (CAAC, low-altitude connected drone safety test report)

A third signal comes from CAAC’s earlier institutional framing of tracking and surveillance system implementation. CAAC discussed building a civil aircraft tracking and surveillance system with phases up to 2025 and described objectives around continuous surveillance and emergency response. Again, this is not a delivery-by-drone implementation policy, but it aligns with why identification readiness is becoming a system-level requirement rather than an “operator best practice.” (CAAC, 2013-05-15 roadmap)

Finally, industry reporting around the new national standards describes a specific operational constraint: drones must transmit identity and status information automatically from startup throughout flight. For delivery networks, that implies they will need operational evidence producible for every dispatch, not only for incident cases. The standard effectively forces operational identification into the operational lifecycle—exactly what an evidence-based approach depends on. (China Daily, 2025-12-11)

Taken together, these examples are not proof of any single company’s compliance architecture. They do show a measurable direction: pilots and tests that connect identity registration to operational monitoring reduce the gap between “who the operator is” and what the system does at runtime. In that sense, the May 1, 2026 standards primarily penalize operational drift—dispatching aircraft whose runtime evidence (activation operability and continuous identification data) cannot be reconstructed to match permission context—rather than requiring documentation only after the fact.

Engineering constraints for dispatch-line software

For commercial delivery firms, the standards change what “good operations” looks like in software and process terms. The identification specification’s described behavior is not optional: it requires operational identification information transmission and storage constraints, including rolling storage with capacity for at least 120 flight hours and frequent rolling updates. (GB 46750-2025 PDF excerpt)

In parallel, the real-name registration and activation standard implies that physical and software activation controls must ensure a drone is inoperable before activation and after deactivation. That shifts engineering priorities toward activation state synchronization across hardware, fleet management software, and dispatch scheduling. (SCIO, 2025-12-10)

The CAAC announcement may not name delivery platforms, but the engineering implication is narrow: operators must build an auditable pipeline that can (1) attest activation operability for a specific airframe at a specific time, and (2) verify identification data continuity at the required cadence until landing, then (3) retain the resulting evidence for regulator-style retrieval.

That usually clusters into three functional layers:

• Airframe activation attestation layer: a fleet-service mechanism that can produce activation state evidence tied to airframe identity and time of dispatch, and that can prevent mission assignment when evidence is missing or inconsistent.
• Identification runtime telemetry and evidence layer: system components that can confirm that identification data is being generated and stored continuously from startup through landing, meeting the operational update interval (no more than 10 seconds) and producing a records set retrievable against the 120-flight-hour rolling retention requirement. (GB 46750-2025 PDF excerpt)
• Dispatch and permission binding layer: mission planning and scheduling logic that ties the permission context to the specific airframes that are currently activatable and currently producing identification evidence, so “permission exists” and “runtime evidence exists” are not separable decisions.

This is governance-by-workflow. The standards turn compliance evidence into an operational artifact that must exist at dispatch time, at flight time, and in retained records after flight.

The scale indicators from CAAC underline why this matters now. With registered UAVs exceeding 2 million and cumulative annual flight hours surpassing 26 million hours in 2024, regulators have strong incentives to ensure identification and activation readiness are standardized, auditable, and automatable. Delivery networks are exactly where network operations can amplify compliance failures into systemic disruptions. (CAAC, 2025-12-24)

What changes next for operators

Because the standards take effect on May 1, 2026, the timeline for operational redesign is tight. CAAC and SAMR’s communication is unambiguous that these two mandatory national standards will be effective from that date. (CAAC, 2025-12-24; SCIO, 2025-12-10)

Between now and then, the evidence-of-activation model points to three pragmatic steps:

1. Map activation states to dispatch decisions, with a pre-flight gate requiring activation confirmation—not merely registration completion.
2. Build identification evidence pipelines aligned with rolling storage and update constraints, including retention logic that can support regulator-style requests.
3. Integrate evidence production into mission planning so permissions submissions can be defended against “wrong aircraft state at launch” narratives.

Policy recommendation: CAAC and local aviation authorities should publish implementation guidance that treats activation state confirmation and identification evidence continuity as audit-ready artifacts for commercial delivery operators in sandbox contexts. The goal should be to reduce interpretive variability on what constitutes “evidence of activation” rather than only stating what the standards require. This recommendation follows directly from how the standards convert system behavior into operational permission readiness. (CAAC, 2025-12-24)

Forecast with timeline: by Q3 2026, delivery operators that already ran sandbox routes should be able to demonstrate end-to-end “activation-to-identification evidence continuity” for routine dispatches, not only incident-driven cases, because identification reporting is required from startup through the entire flight process and because operational evidence storage constraints are explicit. Operators who do not redesign dispatch-line workflows will likely experience higher operational downtime during audits and enforcement checks between May 1, 2026 and the end of 2026. This forecast is consistent with the standards’ effective date and their operational behavior requirements. (CAAC, 2025-12-24; China Daily, 2025-12-11)

If regulators treat identification readiness as operational fitness, delivery networks will treat it that way too. Build an activation-first, evidence-by-design dispatch system—and prove on every flight that permission met reality at startup.