EASA U-space Drone Airspace Framework

1. The Regulatory Framework

Commission Implementing Regulation (EU) 2021/664 of 22 April 2021 on a regulatory framework for the U-space, together with Implementing Regulation (EU) 2021/665 (amending Regulation (EU) 2017/373 to integrate U-space with manned aviation) and Implementing Regulation (EU) 2021/666 (amending Regulation (EU) No 923/2012 on the rules of the air), constitute the U-space regulatory package. The regulations entered into force on 12 May 2021 and have applied since 26 January 2023. They are directly applicable in all Member States; designation of U-space airspace is performed by each Member State under Article 3 of 2021/664 following an airspace risk assessment.

The regulation defines U-space airspace as a UAS geographical zone designated by Member States where UAS operations are allowed only with the support of U-space services. Article 5 makes the use of four mandatory U-space services a precondition for operating in U-space airspace: network identification service (Article 8), geo-awareness service (Article 9), UAS flight authorisation service (Article 10), and traffic information service (Article 11). Member States may additionally require a weather information service (Article 12) and a conformance monitoring service (Article 13). Services are provided by certified U-space Service Providers (USSPs) under Article 14, with certification issued by the Member State competent authority.

The Common Information Service (CIS), defined in Article 5 and detailed in Article 6, provides the shared operational data layer that USSPs and Air Traffic Service providers consume. CIS provision is allocated by Member States either to a single CIS provider or to USSPs collectively. The USSP-to-USSP and USSP-to-ATS coordination is structurally federated: USSPs do not merge into a single airspace controller; they exchange credentialed information through CIS and direct interfaces. AMC and GM material in Decision 2022/022/R issued by the EASA Executive Director, plus the SESAR-developed CORUS-XUAM concept, provide the technical guidance over the regulatory text.

2. The Architectural Requirement

Reduced to its architectural core, 2021/664 requires that every UAS operation in U-space airspace be associated with a credentialed operator intent — a flight authorisation request expressing the operator's planned 4D trajectory, the operator's identification, the certification basis of the UAS and the operator, and the priority class — that is evaluated by USSPs against other authorised intents and against geo-awareness and traffic information at the time of decision. The intent is the load-bearing object: it is what is authorised, what is monitored against by conformance services, and what is reconciled with manned-aviation traffic by the integration with Regulation 2017/373.

The architecture must support graduated fidelity. A small leisure UAS in the open category contributes a different intent fidelity than a BVLOS specific-category cargo operation, and an emergency-services operation under Article 4(2) public-interest exception contributes a different priority class than a commercial photography flight. The flight-authorisation service must evaluate composite admissibility across heterogeneous intents from heterogeneous USSPs, with the credentialed authority of each USSP and each operator weighted into the decision. This is intrinsically the operator-intent primitive: a graduated, credentialed intent fidelity ladder for mixed-fleet coordination.

Cross-USSP and cross-Member-State federation is the second structural property. A drone delivery service operating across a metropolitan U-space airspace served by multiple USSPs cannot be subject to incompatible authorisation decisions; the USSPs must reconcile through CIS without merging. A cross-border operation must reconcile across Member State competent authorities. The structural property is cross-mesh reconciliation: substrate-to-substrate exchange of credentialed observations under a shared authority taxonomy, without consensus or central authority. EASA's role under the SES (Single European Sky) framework defines the taxonomy; USSPs and CIS operate the substrate.

3. Why Procedural and Bolt-On Compliance Fails

Early USSP implementations follow a portal-and-database pattern: an operator submits a flight plan to a USSP web portal, the USSP checks against a database of authorised flights and geo-awareness zones, and issues an authorisation token. This pattern fails the architectural requirement for two structural reasons. First, the intent is reduced to a flight plan record rather than a credentialed observation: the operator's certification basis, the UAS configuration, the priority class, and the operational context are inputs to a decision but not structural elements of the intent itself. The intent has no authority chain that downstream services (conformance monitoring, traffic information, ATS integration) can re-evaluate independently.

Second, USSP-to-USSP coordination through CIS becomes a database-replication problem rather than a credentialed-observation reconciliation. When multiple USSPs serve the same U-space airspace, their separately maintained databases drift unless reconciled at high frequency, and the reconciliation has no structural notion of which USSP holds the authoritative observation about a given operation. The portal pattern degrades into operational confusion when traffic density rises or when adjacent USSPs disagree about a marginal authorisation.

Conformance monitoring is the operational failure mode. Article 13 conformance monitoring requires real-time comparison of actual UAS state against the authorised intent. A bolt-on conformance service watches telemetry against a static flight plan record and triggers an alert when the deviation exceeds threshold. The deviation may, however, be a structurally valid response to weather, traffic, or emergency — without a credentialed-intent chain, the conformance service cannot distinguish a legitimate intent revision from non-conformance, and either over-alerts (degrading operational utility) or under-alerts (degrading safety). The structural mismatch is that intent is not a static record; it is a continuously credentialed object the substrate maintains.

4. What The Operator-Intent Primitive Provides

The AQ operator-intent primitive supplies graduated fidelity tiers in which an operator's intent enters the substrate as a credentialed observation at the fidelity tier appropriate to the operator's certification, the UAS configuration, and the operational context. Tier definitions are published in the authority taxonomy: from minimal (network identification only, open-category leisure) through standard (full 4D trajectory plus contingency) to maximal (4D trajectory plus contingency plus tactical reconfiguration authority for high-priority public-interest operations). Each tier carries different observation rights, different admissibility weight, and different conformance-monitoring depth.

Element by element against 2021/664: Article 8 network identification maps to the credentialed-identity element of the intent. Article 9 geo-awareness maps to the substrate's geo-fenced authority taxonomy — a UAS geographical zone is a published authority configuration that the admissibility evaluation consumes. Article 10 flight authorisation maps to composite admissibility evaluation against other authorised intents and the published taxonomy, producing graduated outcomes (authorised, authorised with conditions, deferred pending verification, refused). Article 11 traffic information maps to the recursive closure: every authorisation decision and every conformance observation re-enters the chain as credentialed traffic information for other operations.

Article 13 conformance monitoring maps to the substrate's continuous evaluation of actual state against the authorised intent at its tier-appropriate fidelity. A tier-one operation has a tighter conformance band than a tier-three operation; a deviation that exceeds the tier band is a credentialed observation that re-enters the chain and may trigger graduated USSP actuation (advisory to operator, intent revision, authorisation withdrawal, contingency activation). The graduated actuation property of governed actuator execution is precisely what conformance monitoring requires beyond binary alerting.

The cross-mesh reconciliation property between USSPs through CIS is the structural answer to the federation problem. USSPs operate independent substrates over their respective service areas; CIS is the credentialed-observation exchange channel. A USSP receives credentialed authorisations from peer USSPs as inputs to its own admissibility evaluation, without merging the substrates. A cross-border operation is reconciled across Member State competent authorities through their respective USSPs' substrates, with the SES authority taxonomy providing the shared credential frame. The architecture scales linearly with the number of USSPs and Member States rather than quadratically.

5. Compliance Mapping

Article 3 (designation of U-space airspace) maps to the published geo-authority taxonomy admissible into the substrate. Article 5 (mandatory U-space services) maps to the umbrella structural property: the four mandatory services are properties of the substrate, not separately engineered components. Article 6 (Common Information Service) maps to cross-mesh reconciliation between USSP substrates. Article 7 (general requirements for U-space service providers) maps to the credentialed-authority class for USSPs in the taxonomy.

Article 8 (network identification) maps to authority-credentialed observation at the UAS-identity level. Article 9 (geo-awareness) maps to the geo-fenced admissibility configuration. Article 10 (flight authorisation) maps to composite admissibility evaluation with graduated outcomes. Article 11 (traffic information) maps to the recursive closure property. Article 12 (weather information) and Article 13 (conformance monitoring) map respectively to environmental observation modalities and continuous-state admissibility evaluation. Article 14 (USSP certification) maps to the regulator-authority class for issuing USSP credentials into the taxonomy.

Integration with Regulation 2017/373 (ATS) under Implementing Regulation 2021/665 maps to cross-mesh reconciliation between U-space USSP substrates and ATS provider substrates, with controlled-airspace authority taxonomies bridging the boundary. Integration with Regulation 923/2012 (SERA) under Implementing Regulation 2021/666 maps to admissibility configurations consistent with the rules of the air. SESAR CORUS-XUAM concept guidance maps to operational-tier admissibility configurations the substrate uses for urban air mobility.

6. Adoption Pathway

Adoption is led by USSPs because Article 14 certification places the operational obligation on them. Member State competent authorities (typically the national civil aviation authority) are the second adoption tier because they certify USSPs and operate the regulatory authority issuance into the substrate's taxonomy. CIS providers are the third tier; under most Member State allocations, CIS is operated either by a single designated entity or by USSPs collectively, with the substrate's cross-mesh reconciliation property providing the technical answer to the collective-CIS allocation.

The transition path leverages SESAR investments. The SESAR JU and CORUS-XUAM concept materials, the EASA AMC/GM in Decision 2022/022/R, and Member State pilot deployments (notably the early French, Polish, and Italian U-space designations) provide a body of operational experience that becomes the initial admissibility configurations of the substrate. Existing UTM platforms operated by drone-service companies are absorbed as USSP-credentialed substrates rather than displaced. Cross-border harmonisation with FAA UTM, UK CAA, and Swiss FOCA frameworks is enabled by the cross-mesh reconciliation property — substrates do not need to be identical, only credentialed under reconciled taxonomies. By the time U-space airspace designations reach metropolitan-scale density, the substrate is the operational compliance object that competent authorities audit and that USSPs interoperate over.