Three Operators, Two Traffic Systems, One Sky: What the UK's Chorley UTM Trial Actually Proved

Getting drones from several operators to share a piece of sky takes more than good aircraft. The traffic-management software each operator relies on has to agree on who is flying where and when. A demonstration in Chorley, Lancashire, tested that problem with a commercial delivery giant, a smaller delivery operator and an emergency service all flying in the same block of airspace. They did it without putting everyone on one shared system.

DroneDJ reported on Nov. 11 that ANRA Technologies, Wing, Manna Air Delivery and Lancashire Fire and Rescue Service (LFRS) had completed the trial with UK Civil Aviation Authority (CAA) approval. Commercial delivery drones and emergency-service drones flew beyond visual line of sight (BVLOS) and within visual line of sight (VLOS) inside a single Temporary Danger Area, and the operators exchanged flight intentions before each mission.

The airspace itself was not the hard part. The software was.

What was actually tested?

Each operator used a UTM (uncrewed traffic management) provider, and the providers were not the same. ANRA supplied UTM services to Manna and the fire service. Wing flew on its own vertically integrated UTM platform. According to DroneDJ, the two systems exchanged information using ASTM F3548-21, the industry standard for interoperability between UAS Service Suppliers (USSs). Automated testing ran through the open-source InterUSS Platform.

In practice, Wing did not need to join ANRA's system, and ANRA's customers did not need to join Wing's. The systems exchanged flight intentions so conflicts could be spotted and resolved before takeoff. Unmanned Airspace reports that Wing, Manna and LFRS shared strategic deconfliction and operational data under CAA supervision.

Unmanned Airspace dates the event to Oct. 21. It describes that day as the first operational evaluation of multiple BVLOS operators sharing airspace under federated UTM in the UK. Operators in the programme are aiming for 95% conformity to the agreed flight plan, which in plain terms means staying close to the plan they declared to the network.

Why federated, and why Dallas?

There are two broad ways to run low-altitude drone traffic. One gives a single provider authority over a region. The other, the federated model, lets several competing providers operate side by side, provided they talk to each other through common standards and under common rules. Chorley tested the second.

The UK did not design this model from scratch. Unmanned Airspace says the Chorley event was the first iteration of a "UK UTM Implementation" programme under the CAA's Airspace Modernisation Strategy, designed along the lines of the FAA's Dallas programme. The outlet cites more than 2.4 million coordinated drone flights in the US since January 2026, and US drone delivery companies operating up to one flight manager per 80 autonomous drones. Those US figures show what the approach looks like at scale. Nothing at Chorley came close to that volume, and the numbers should not be read as a forecast for the UK.

The original 2025 funding announcement made the connection explicitly. The CAA awarded an Airspace Modernisation Support Fund (ASF) grant to a consortium led by ANRA Technologies UK Ltd, with LFRS, Manna and Wing as partners. The grant funded what the announcement called the UK's first operational demonstration of multi-UTM service provider support for overlapping BVLOS operations in shared airspace. The project supports the Airspace Modernisation Strategy, builds on lessons from the US UTM Implementation, and was planned as multi-phase live trials covering interoperability, governance frameworks and cooperative operating principles.

Why include a fire service?

Mixing delivery drones with a blue-light operator was a deliberate choice, and it leads straight into the programme's next phase. Stuart Lindsey, the CAA's Head of Airspace Modernisation, described Chorley, according to Unmanned Airspace, as the first step in a three-step process toward scalable commercial BVLOS operations. The next step, after close evaluation of the system's performance, is new prioritisation arrangements for safety-of-life drone operators. In principle, that means a fire service drone heading to an incident would take precedence over delivery traffic, including traffic on a different provider's network.

Chorley showed that the operators could coexist. It did not yet show that one could take precedence over the others. Getting that right across separate providers is likely to be harder than shared awareness. It would need agreed rules about who counts as a priority operator, how quickly other providers must respond, and who is accountable if they do not.

Unmanned Airspace also says network Remote ID (NetRID) is planned for the programme, along with new participants, and that the same ecosystem will be launched in other parts of the UK in the next development stage.

What the participants are saying

ANRA founder and CEO Amit Ganjoo highlighted three operators sharing the same airspace with "the governance framework in place." That governance point matters more than it might seem. Standards like F3548-21 define how systems exchange messages. They do not by themselves settle who resolves a dispute between providers or who answers to the regulator when a conformance failure on one network affects another.

According to DroneDJ, the consortium wants to turn the evaluation into a repeatable framework that can be used across the UK, organised around five areas:

technical interoperability
common operational procedures
governance and accountability
easier onboarding of new operators
continued regulatory alignment with the CAA

Giancarlo Buono, Group Director of Safety, Airspace and Regulatory Group at the CAA, said the exercise provides valuable evidence to support routine BVLOS operations and airspace modernisation.

Why It Matters

BVLOS operations have traditionally relied heavily on segregated airspace or individually coordinated permissions, according to DroneDJ. Chorley itself ran inside a Temporary Danger Area. That approach is hard to scale: a country cannot keep creating a new segregated block of sky every time another delivery company, police force or infrastructure inspector wants to fly.

The federated approach tested at Chorley offers another route. Operators choose their own UTM provider, and the providers coordinate through published standards and open-source conformance testing. For vertically integrated players like Wing, this means they do not have to hand their traffic to a competitor's system. For smaller operators and public services, it means they can join through a third-party provider such as ANRA without building their own stack. For the regulator, it means oversight of an ecosystem governed by shared rules, rather than a single gatekeeper.

The choice of model will shape who controls low-altitude airspace in the UK and how easily new entrants can get in. By building on the Dallas lessons, the CAA is signalling a competitive, standards-based approach over a single-provider one, at least in this first iteration.

The caveats

The sources do not report results against the 95% conformity target. Without that data, nobody outside the project can tell how closely the drones followed their declared plans, how often deconfliction had to step in, or whether the cross-provider exchange caused any delays.

The trial also took place inside a Temporary Danger Area. Unmanned Airspace describes it as a 4km by 4km area with an altitude ceiling of 800ft above mean sea level. That was a controlled environment, not the open, unsegregated airspace that routine commercial BVLOS will eventually require. Unmanned Airspace reports that industry and regulators were coy about when commercial operations in shared airspace could be launched and scaled, and the safety-of-life prioritisation step has yet to be implemented and tested.

Chorley matters because it was the first time this was done in the UK, not because the problem is solved. Two separate UTM systems kept a global delivery company, a smaller delivery operator and a fire service coordinated in the same sky, under regulatory supervision and using a public standard. The next phases will show whether the setup can handle priority traffic, more operators and regions beyond Lancashire.