Delivery drones and a fire crew shared one UK sky by making separate traffic systems talk

On 21 October 2026, delivery drones and fire-and-rescue drones flew inside the same four-kilometre block of sky over a town in Lancashire, northern England. The block was a temporary danger area, airspace set aside for the exercise, capped at 800 feet above mean sea level. Four organisations shared it under the UK's civil aviation regulator, the Civil Aviation Authority (CAA): ANRA Technologies, which supplies drone traffic-management services; Wing, a delivery operator running its own vertically integrated platform; Manna Air Delivery, a delivery operator flying on ANRA's service; and Lancashire Fire and Rescue Service. Unmanned Airspace reported it from the ground, and it changed no UK airspace rule. The demonstration shows where the constraint has moved: away from the aircraft and the size of the airspace carve-out, toward whether separately built traffic-management systems can be trusted to talk before takeoff.

Each operator declared its flight intentions before launch, and the two platforms exchanged those intentions using ASTM F3548-21, a published specification telling separately built traffic-management services how to share flight information. The standard splits the job into named roles, from strategic coordination, which detects conflicts between planned routes, to conformance monitoring and constraint management. The consortium also ran automated interoperability testing on the open-source InterUSS Platform, which is test infrastructure, not a certificate. The UK programme reuses the FAA's Dallas foundations, the same standard and the same distributed service-provider model, rather than building a British architecture. The project also has a public funding line: the CAA awarded its Airspace Modernisation Support Fund to the consortium in May 2025, according to the consortium's announcement.

The UK implementation network's stated target is a 95% conformity rate, meaning how closely each flight follows the agreed plan, and the Chorley evaluation published no achieved conformity rate, no flight count, no aircraft count and no conflict-free record. The operating-scale numbers in public come from Texas, where Flytrex and Wing flew at the same time on 30 of 31 active days between January and February 2026, roughly 8,000 overlapping flights, with every operational intent deconflicted and zero reported airspace conflicts, often sharing the sky for more than ten hours a day, according to the operators' own figures as reported by DroneXL. The US counterpart is the FAA's UTM Operational Evaluation, the programme testing that traffic-management architecture, which counted 17 service providers and operators as of January 2026. Dallas was a commercial operation and Chorley a single demonstration, so the two are not like for like.

Strategic deconfliction coordinates planned intent and stops there. It does not broadcast a dedicated in-flight emergency or contingency state from one operator to another, according to Shai Karassikov, Flytrex's product manager and co-chair of the US UTM Tech Committee. Planned route changes travel across the network, but each operator handles its own emergency and contingency landing under its own separate approvals. The UK exercise ran on the same standard and the same stated strategic mechanism, and the consortium release does not describe contingency-state sharing either, so the arrangement in Lancashire may have the same shape. Neither the regulator nor the participants has confirmed that publicly. If shared operations at scale turn out to need private carve-outs again, Chorley was an artefact rather than an operating model.

Chorley is step one of a three-step path the regulator has set out for shared commercial drone operations. Stuart Lindsey, the CAA's head of airspace modernisation, called it step one, with step two, after the evaluation, being new prioritisation arrangements for safety-of-life drone operators, and later steps adding networked remote ID, the broadcast that identifies a drone in flight, and further participants elsewhere in the UK. The announced demonstration comes before the part that decides who flies first. The regulator's concept of operations puts multi-operator shared environments, with strategic deconfliction and approved detect-and-avoid systems, in the 2026-2027 stage, and high-risk environments, where tactical deconfliction and electronic conspicuity, meaning aircraft broadcasting their position to others, become mandatory, in 2028 and later, when the CAA says such high-integrity solutions are "not yet widely available for routine commercial use". Industry and regulators were vague on when shared operations reach commercial scale: one industry expert quoted by Unmanned Airspace asked, "Why delay?", while others, speaking privately, floated as early as next year.

The United States and Europe are moving in opposite directions on priority in shared airspace. In the United States, the FAA blew past the 1 February 2026 deadline for Part 108, the rule covering complex beyond-visual-line-of-sight operations, in which a remote pilot flies without seeing the aircraft, and the contested provisions would give some operators presumptive right-of-way over crewed aircraft; more than half of roughly 3,100 substantive comments addressed that question alone, according to DroneXL. In Europe, EASA's Notice of Proposed Amendment 2026-103 proposes a "U-space light" category for airspace where traffic density does not require strategic deconfliction at all, and its survey of 11 member states found 496 of 2,486 active operational authorisations concerned beyond-visual-line-of-sight operations, of which only 89 were reported as economically viable, concentrated in Germany and Norway.

Each delivery base also needs site-by-site local planning consent, because the CAA does not grant planning permission and the 28-day temporary-use rule does not cover a hub that flies every day, according to sUAS News's analysis of the planning problem. Aviation approval does not unlock national scale on its own. The standard is open for revision too: ASTM work item WK85414 has been opened to revise F3548-21.

Step two, the regulator's prioritisation arrangement for safety-of-life operators, has not been published. If a fire crew and a delivery operator want the same four-kilometre block in the same minutes, who goes first, and who settles it when their separately built systems disagree?