The UK has described the architecture for routine BVLOS. Now it has to work between organisations

The CAA’s concept moves the discussion beyond isolated trials and towards the information exchanges that commercial operations will depend on.

The UK Civil Aviation Authority published an Airspace Architecture Concept of Operations on 30 July 2026. Its purpose is straightforward: describe how drone operations could move from isolated trials and bespoke approvals towards routine commercial use alongside crewed aircraft.

The CAA identifies several pieces that have to mature together: electronic visibility between airspace users, conflict-avoidance systems, reliable communications, digital traffic-management services and better information sharing between operators and air traffic services.

None of those is a single product purchase. They form an operating architecture, with different organisations responsible for different decisions.

What the architecture has to connect

A map can show a route and a restricted area. Routine BVLOS needs more than that. The planned route has to remain connected to the aircraft, the operator’s approvals and the current airspace state. Relevant changes have to reach the right person soon enough to matter. Afterwards, the organisation needs a record that explains what actually happened.

The CAA’s document is careful to call this a vision that will evolve through testing and industry feedback. That is appropriate. A digital architecture should be proved through real handoffs, not judged by how complete it looks on paper.

Consider an infrastructure inspection that crosses several local areas. The operator manages the aircraft and remote pilot. The asset owner cares about the inspection window and the condition of the route. Air traffic services need the information relevant to their role. A nearby airport or emergency-service operator may have a separate concern. Giving everybody the same raw feed would not solve the problem.

The awkward handoffs deserve most of the attention

Programmes often work well inside one organisation and become fragile at the boundary with another. A permit is stored in an inbox. A route change is discussed by phone but never reaches the shared record. Aircraft maintenance data sits with the fleet team while the dispatcher sees only availability. An incident reviewer later has to reconstruct the sequence from several exports.

For an enterprise operator, AerialEye keeps planning, live flight information, fleet readiness, compliance records and survey deliverables within one operating system. It is not a substitute for a CAA authorisation or an approved safety case. Its value is in making the operator’s own evidence easier to maintain and review.

SkyGrid addresses the wider airspace view. It brings mapped zones, flight information and structured event records together for authorised teams. External connections are validated and scoped per deployment. SkyGrid does not separate aircraft, direct a remote pilot or replace air traffic services.

Shared information, separate responsibilities

A shared interface is useful precisely because responsibilities remain separate. An operator should see what it needs to conduct the mission. A city or infrastructure owner may need activity around a corridor. An aviation authority needs information that supports oversight. Each should have access appropriate to its role, without assuming that visibility transfers legal authority.

Cooperative identity can help make those views more useful. For compatible legacy and mixed-brand fleets, SkyTag provides operator-controlled Remote ID and can connect the aircraft to the Aerial Grid environment. Platform compatibility, communications coverage and jurisdiction-specific compliance still have to be confirmed before deployment.

The UK concept covers aircraft, operators, communications, digital services, air traffic organisations and regulators. No single platform owns that system. A credible deployment should say which part each tool supports, which data it receives and who remains accountable for the decision.

What should be tested next

The next demonstrations should spend less time proving that a drone can complete a long route and more time testing the seams: a late restriction, a loss of communications, a changed inspection window, an aircraft swap, an emergency-service priority or a request for the flight record weeks later.

If the architecture handles those ordinary complications, routine BVLOS becomes easier to trust. If it only works when every input arrives on time and every participant uses the same system, it remains a trial arrangement with a larger diagram.

The CAA has described the intended architecture. Operators, infrastructure owners and technology providers now have to prove that information can move between them without obscuring who remains responsible for the flight.

Talk to Aerial Grid about a scoped BVLOS operations or airspace-integration assessment.

Editorial note: This article is independent analysis of the UK CAA publication. Aerial Grid did not author the concept, does not claim participation in the CAA programme and does not provide air traffic control or regulatory approval.

Issued by Aerial Grid AG.

Editorial sources

UK Civil Aviation Authority: Airspace Architecture Concept of Operations announcement, 30 July 2026