Detailed reference material on the U-space (EU) and UTM (ICAO/global) frameworks for UAS Traffic Management. This folder expands the summary in topics/u_space.md into per-aspect files so each can be read on its own.

Files in this folder#

• overview.md — what U-space and UTM are, the EU/global distinction, and where the frameworks sit in the ATM ecosystem.
• components.md — the service catalogue (mandatory and optional), the actor model (USSP, CISP, competent authority, operator), and the ICAO UTM Edition 4 core service taxonomy.
• blocks.md — the U-space maturity model: U1 (foundation), U2 (initial), U3 (advanced), U4 (full); mermaid progression flow.
• threads.md — the seven functional axes of UTM/U-space: identification, authorisation, traffic information, conformance, geo-fencing, weather, and the ATC interface.
• modules.md — anatomy of the flight authorisation service end-to-end, with a worked example showing actor interactions.
• enablers.md — CNS, network, regulatory, certification, human factors, and institutional prerequisites.
• performance_objectives.md — KPA matrix, KPIs, and performance framework for U-space/UTM services.
• timeline.md — historical milestones from 2011 to 2026 and beyond, with a Year-keyed table.
• references.md — consolidated ICAO and authoritative external references for everything in this folder.

Reading order#

Start with overview.md and components.md to understand the concept and actors. Read blocks.md for the U1-U4 maturity progression. threads.md shows the functional decomposition; modules.md gives a worked example. enablers.md and performance_objectives.md are best opened on demand.

Source basis#

Content is grounded in:

• ICAO Annex 2 (Rules of the Air), Appendix 4 — RPAS operating rules.
• ICAO Doc 10019 (Manual on Remotely Piloted Aircraft Systems, 1st edition).
• ICAO Doc 9868 (PANS-TRG), Chapter 8 — remote pilot licensing.
• ICAO UTM Framework Editions 1-4 (2019-2023): https://www.icao.int/utm-guidance
• Commission Implementing Regulation (EU) 2021/664 — U-space regulatory framework, applicable 26 January 2023: https://eur-lex.europa.eu/eli/reg_impl/2021/664/oj/eng
• Commission Implementing Regulation (EU) 2021/665 and (EU) 2021/666.
• EASA Easy Access Rules for U-space (May 2024): https://www.easa.europa.eu/en/domains/air-traffic-management/u-space
• SESAR CORUS-XUAM U-space ConOps edition 4 (September 2023): https://www.sesarju.eu/projects/CORUSXUAM
• FAA UTM Concept of Operations v2.0 (March 2020): https://www.faa.gov/sites/faa.gov/files/2022-08/UTM_ConOps_v2.pdf

The scaling problem that created UTM#

Traditional air traffic management handles thousands of commercial aircraft per day via direct voice communication and radar surveillance. A controller accepts or rejects individual requests, issues clearances, and separates traffic. This model works well at the scale of manned aviation — a busy sector handles perhaps 30-50 aircraft per hour.

Scalable unmanned aviation breaks that model. Credible projections for drone operations at maturity — last-mile delivery, infrastructure inspection, urban air mobility, emergency response, precision agriculture — imply tens of thousands of simultaneous operations in a single metropolitan area. No controller workforce can handle that volume on a one-operation-one-clearance basis.

UAS Traffic Management (UTM) is the response: an ecosystem of digital services, automated by design, that enables large numbers of unmanned aircraft to access low-level airspace safely without direct controller involvement in each operation.

ICAO UTM — the global framework#

ICAO defines UTM as a specific aspect of air traffic management for UAS that manages UAS operations safely, economically, and efficiently through the provision of facilities and a seamless set of services in collaboration with all parties and, where necessary, with the manned aviation community.

ICAO has developed its UTM Framework through four iterative editions (2019-2023), each adding depth:

• Edition 1 (2019): foundational concepts — registration, identification, tracking, communications, geofencing.
• Edition 2 (2020): UTM-ATM boundaries, transitions, and exchange of information.
• Edition 3 (2021): UTM risk assessment, contingency procedures, UTM service provider roles, separation and deconfliction.
• Edition 4 (May 2023): core UTM services taxonomy, UTM-ATM harmonization interface, AAM (Advanced Air Mobility) considerations.

The UTM Framework is guidance, not binding SARPs. ICAO's RPAS Panel (RPASP) is developing the SARPs that will eventually make UTM provisions normative in the Annexes.

U-space — the European regulatory implementation#

U-space is the European regulatory implementation of UTM. It is governed by a three-regulation package adopted in April 2021 and applicable from 26 January 2023:

• Regulation (EU) 2021/664 — the core U-space regulatory framework.
• Regulation (EU) 2021/665 — ATM/ANS provider obligations in U-space airspace.
• Regulation (EU) 2021/666 — electronic conspicuity obligation for manned aircraft in U-space airspace.

U-space is not a specific piece of technology or a single system. It is a regulatory construct: a designated airspace volume in which defined services are provided by certified service providers under the oversight of the competent authority.

UTM vs U-space: key distinctions#

Where U-space/UTM sits in the ATM ecosystem#

The critical point is the interface layer: ATC retains authority for manned aviation; U-space services manage UAS operations; the CISP (plus the USSP-ATS interface) ensures mutual situational awareness and prevents conflicts between the two worlds.

The ASBU link#

ICAO ASBU Block 2 includes RPAS-B1/2 modules addressing integration of Remotely Piloted Aircraft Systems into controlled airspace. These modules presuppose the existence of a functioning UTM/U-space-like service layer. The progression from RPAS-B1 (segregated RPAS corridors) to RPAS-B2 (integrated non-segregated operations) mirrors the U1-to-U3 maturity progression in the SESAR ConOps.

References#

• Annex 2 (Rules of the Air), Appendix 4 — RPAS general operating rules in international air navigation.
• Doc 10019 (Manual on Remotely Piloted Aircraft Systems), Chapter 1, §1.2 — Chicago Convention Article 8 and the ICAO regulatory concept for RPAS integration.
• ICAO UTM Framework Edition 4 (May 2023) — global UTM concept, services, UTM-ATM interface (authoritative source — not in local library; see https://www.icao.int/utm-guidance).
• Commission Implementing Regulation (EU) 2021/664, Articles 1-4 — U-space airspace definition, USSP certification, mandatory service regime (authoritative source — not in local library; see https://eur-lex.europa.eu/eli/reg_impl/2021/664/oj/eng).
• SESAR CORUS-XUAM U-space Concept of Operations edition 4 (2023) — U1/U2/U3/U4 maturity framework and UAM integration (authoritative source — not in local library; see https://www.sesarju.eu/projects/CORUSXUAM).

The service catalogue#

U-space and UTM are service ecosystems. The components are the services themselves, the actors who provide and consume them, and the information infrastructure that ties the ecosystem together.

1. Mandatory U-space services (EU 2021/664)#

Four services must be provided by every certified USSP in any designated U-space airspace.

1.1 Network identification#

Network identification enables continuous processing of UAS remote identification throughout the entire duration of the flight. The USSP receives remote identification broadcasts from the UAS (using the network identification method — typically a radio broadcast of ID, position, altitude, operator ID, and emergency status) and makes this data available to authorised users in real time. Regulatory authorities can identify any UAS flying in U-space airspace without physically stopping the aircraft.

Network identification is distinct from and complementary to direct remote identification (broadcast from the UAS, detectable with short-range receivers). The network method provides centralised aggregation and distribution.

1.2 Geo-awareness#

Geo-awareness delivers to UAS operators the latest information on airspace constraints applicable to their planned or ongoing operation. This includes:

• UAS geographical zones (designated prohibited, restricted, or conditional areas for UAS operations).
• Standard airspace structure (ATZ, CTR, TMA, restricted areas).
• Temporary flight restrictions and dynamic restrictions activated after the flight was authorised (for example, emergency TFR for an emergency helicopter route).

Geo-awareness is the mechanism by which the regulatory picture that the competent authority and ATS units maintain is continuously pushed to operators and UAS systems. A UAS with a geo-awareness service subscription can enforce geo-fencing autonomously.

1.3 UAS flight authorisation#

The flight authorisation service validates the proposed operation and issues an authorisation confirming that the 4D operational volume (lateral boundary, altitude band, time window) is:

• Free of conflict with other notified active authorisations.
• Clear of activated geo-zone restrictions.
• Compatible with notified manned aircraft operations in the same volume.

Each authorisation carries the authorised 4D volume, any deviations from the request, and conditions imposed by the USSP or the competent authority. Strategic deconfliction (separation in space-time planning before operations begin) is the core function.

The authorisation is not an ATC clearance. It does not supersede the authority of ATC in controlled airspace. In controlled airspace, the USSP must also interface with the ATS unit through the CISP.

1.4 Traffic information#

Traffic information provides the UAS operator with real-time position data on manned aircraft operating in the same U-space airspace. This enables the remote pilot (or an onboard autonomy system) to maintain situational awareness and take action to remain well clear when manned aircraft are detected nearby.

Traffic information comes from the CISP, which aggregates manned aircraft electronic conspicuity data (from transponders, ADS-B, ADS-L, and other sources). Regulation (EU) 2021/666 obligates manned aircraft in U-space airspace to be electronically conspicuous, closing the gap that existed when light aircraft (without transponders) could be invisible to U-space services.

2. Optional services (Art. 12-13 EU 2021/664)#

Member States may mandate additional services based on an airspace risk assessment.

2.1 Conformance monitoring#

Conformance monitoring detects when a UAS deviates beyond tolerance from its authorised operational volume. On detecting a breach, the USSP must:

1. Alert the UAS operator to the deviation.
2. Alert other UAS operators in the vicinity.
3. Alert other USSPs operating in the same airspace.
4. Alert the relevant ATS unit, which must acknowledge the alert.

Conformance monitoring closes the loop between the pre-flight authorisation and the actual flight, providing a safety net against navigational errors, command-and-control link failures, or deliberate violations.

2.2 Weather information service#

Provision of meteorological data relevant to the planned or ongoing UAS operation. UAS are significantly more weather-sensitive than commercial aircraft — wind gusts, icing, reduced visibility, and precipitation can render an operation unsafe or illegal. A weather information service provides METAR/SPECI data, wind forecasts, and real-time sensor data relevant to the operational volume.

3. ICAO UTM Edition 4 core services (global taxonomy)#

ICAO Edition 4 (2023) identifies a broader set of core UTM services for global harmonization:

• Strategic deconfliction — arrangement, negotiation, and prioritisation of intended operational volumes, routes, or trajectories to minimise the likelihood of airborne conflicts.
• Tactical conflict advisory and alert — real-time alerting through suggestive or directive information on UA proximity to other airspace users.
• Manned aircraft interface — real-time manned aircraft position information so that UA remain well clear.
• Conformance monitoring — deviations from authorised volumes.
• Emergency and contingency management — procedures for lost command-and-control link, emergency landings, UTM/ATM handover.
• Registration and identification — operator and aircraft identity, providing accountability.

4. Actors in the ecosystem#

4.1 U-space Service Provider (USSP)#

The USSP is a certified legal entity authorised by the competent authority to provide U-space services. To be certified, a USSP must demonstrate capability to provide at minimum the four mandatory services, meet information security requirements, and implement the required interfaces with the CISP and ATS units.

Multiple USSPs may operate simultaneously in the same U-space airspace. They must interoperate — a UAS operator subscribing to USSP A and a UAS operator subscribing to USSP B must achieve mutual strategic deconfliction. This interoperability is ensured via the CISP.

4.2 Common Information Service Provider (CISP)#

The CISP is a neutral entity designated by the competent authority. Its function is to collect, aggregate, and disseminate the common static and dynamic data that all USSPs need to provide their services:

• Static data: airspace structure, geographical zones, prohibited areas.
• Dynamic data: TFRs, activated restrictions, manned aircraft positions, weather.
• Cross-USSP operational data: active flight authorisations from all USSPs (for deconfliction purposes).

The CISP is the interoperability hub. Because it holds all authorisations from all USSPs, it enables any USSP to deconflict against any other operator's flight. EASA policy prevents a CISP from simultaneously operating as a USSP in the same airspace to avoid conflict of interest.

4.3 Competent authority#

The national civil aviation authority (or a body it designates) responsible for:

• Conducting the airspace risk assessment and designating U-space airspace.
• Certifying USSPs.
• Designating the CISP.
• Determining which optional services are mandatory in each airspace.
• Enforcement and oversight.

4.4 UAS operator#

The operator holds the flight authorisation and is responsible for compliance with its terms, geo-awareness obligations, remote identification requirements, and any applicable operational rules. Operators access U-space services through their chosen USSP.

4.5 ATS unit#

The ATS unit (ATC or AFIS) retains full authority for manned aviation and, in controlled airspace, for the overall management of the airspace. The ATS unit receives common information from the CISP and is alerted by USSPs when conformance breaches occur or when emergency procedures are activated. The ATS unit can impose constraints on U-space operations or close U-space airspace in controlled airspace via the competent authority.

5. Information infrastructure#

The CISP and the USSP-to-USSP interoperability layer require a well-defined information exchange standard. In Europe, this relies on the ASTERIX standard for manned aircraft surveillance data and evolving SWIM-compatible interfaces for the common information services. The ICAO UTM Framework Edition 4 advocates for global harmonization of UTM data exchange formats.

References#

• Commission Implementing Regulation (EU) 2021/664, Articles 8-15 — definitions of mandatory and optional services, USSP requirements, CISP requirements (authoritative source — not in local library; see https://eur-lex.europa.eu/eli/reg_impl/2021/664/oj/eng).
• Commission Implementing Regulation (EU) 2021/666, Art. 1 — electronic conspicuity obligation for manned aircraft in designated U-space airspace (authoritative source — not in local library).
• ICAO UTM Framework Edition 4 (May 2023), Chapter 3 — core UTM services taxonomy (authoritative source — not in local library; see https://www.icao.int/utm-guidance).
• EASA Easy Access Rules for U-space (May 2024) — AMC and GM to Regulation (EU) 2021/664 (authoritative source — not in local library; see https://www.easa.europa.eu/en/domains/air-traffic-management/u-space).
• Annex 2 (Rules of the Air), Appendix 4, §1.7 — RPAS equipment and performance requirements for the specific airspace in which the flight is to operate.

The maturity model#

U-space is not a single switch to be flipped. The SESAR CORUS (Concept of Operations for European UTM Systems) project, originally published in 2019 and extended through the CORUS-XUAM project (ConOps edition 4, September 2023), describes a stepwise progression through four maturity levels: U1, U2, U3, and U4. Each level enables a wider set of operations while building on the services established in the previous level.

The maturity levels are analogous in purpose to ASBU Blocks: they define an achievable, coherent bundle of capability at each step rather than mandating a single big-bang deployment.

Progression overview#

U1 — Foundation services#

U1 establishes the foundational layer. Without U1, there is no accountability or awareness baseline.

Key services at U1:

• UAS operator registration (national UAS registry).
• Electronic identification: UAS operators and their aircraft are identified and traceable.
• Static geo-awareness: operators can query published geographical zones, prohibited areas, and airspace structure before flight.

Operations supported: low-risk, typically VLOS (Visual Line of Sight), lightweight UAS in uncontrolled airspace, with basic regulatory traceability.

U1 does not yet provide real-time dynamic services. It is the administrative and identity foundation that makes U2 trustworthy.

U2 — Initial services#

U2 introduces the four mandatory U-space services of EU 2021/664 and enables planned BVLOS (Beyond Visual Line of Sight) operations in designated airspace.

Key services added at U2:

• Dynamic geo-awareness: real-time delivery of activated TFRs, emergency restrictions, and updates to geographical zones.
• UAS flight authorisation: strategic deconfliction against other authorised operations and manned traffic.
• Network identification: continuous real-time identification of UAS during flight.
• Traffic information: real-time manned aircraft positions.

Operations supported: commercial BVLOS at low-medium density in both uncontrolled and controlled airspace (subject to ATS coordination). Typical use cases at U2: infrastructure inspection, pipeline survey, rural last-mile delivery.

U2 requires a functioning USSP ecosystem — certified USSPs and a designated CISP. The EU 2021/664 package defines the regulatory conditions for U2-level operations.

U3 — Advanced services#

U3 targets more complex, higher-density operations, including urban and semi-urban areas where airspace is congested and the cost of separation failure is high.

Key services added at U3:

• Conformance monitoring: automated detection of, and alerting for, deviations from authorised volumes.
• Conflict advisory and alert: real-time proximity alerting for nearby UAS, providing suggestive or directive deconfliction information.
• Capacity management and traffic prediction: forecasting demand in U-space airspace, managing saturation of popular corridors.
• Automated DAA assistance: ground-based systems augmenting the onboard detect-and-avoid capability.

Operations supported: high-density BVLOS in urban areas, complex multi-operator corridors, mixed UAS/manned airspace. U3 begins to accommodate lighter Urban Air Mobility operations.

U3 demands mature technical infrastructure: reliable C2 (command and control) links, low-latency data exchange, and interoperating USSPs via an operational CISP.

U4 — Full services#

U4 is the long-term vision. At U4, U-space fully integrates with manned ATM, supports high levels of autonomy, and enables passenger-carrying UAM (eVTOL) operations.

Key characteristics at U4:

• Automated separation between UAS and between UAS and manned aircraft.
• Full ATM-UTM convergence: shared situational awareness, dynamic airspace reallocation, automated conflict resolution between the two systems.
• UAM vertiport management: integration of departure and arrival sequencing at vertiports into U-space services.
• High-autonomy operations: reduced or zero real-time human intervention for routine operations.

The CORUS ConOps notes that U4 is not fully defined in the current document since it heralds interoperation between U-space and manned aviation at a level that requires additional SARPs development, eVTOL certification frameworks, and operational experience from U2 and U3 deployments.

Relationship to the EU regulatory package#

EU 2021/664 mandates the four services that characterise U2 in the SESAR ConOps terminology. The regulation does not use the U1-U4 labels; those are a ConOps construct. However, the regulatory structure maps cleanly:

• U1: pre-regulation registration and identification requirements (already in place under earlier EU drone regulations).
• U2: what EU 2021/664 defines as the minimum for a designated U-space airspace (applicable from 26 January 2023).
• U3 and U4: achievable under the 2021/664 framework through Member State risk assessment triggering optional services, and through future SARPs/regulation as the ecosystem matures.

Pakistan and APAC context#

Outside Europe, most jurisdictions are at early U1/U2 levels. A typical APAC civil aviation authority's UTM roadmap would:

1. Establish a UAS registration and e-identification system (U1 baseline) as a prerequisite for regulatory oversight.
2. Designate pilot U-space airspace or UTM airspace at one or two locations (industrial park, port, urban testbed) and certify the first UTM service providers (U2 level).
3. Build experience before mandating conformance monitoring and enabling high-density BVLOS (U3 migration).
4. Engage with the ICAO RPASP and the UTM Framework process to ensure national implementation remains harmonised with the evolving global standard.

References#

• SESAR CORUS-XUAM U-space ConOps edition 3.10 (2022) / edition 4 (September 2023) — U1/U2/U3/U4 model and UAM integration (authoritative source — not in local library; see https://corus-project.eu and https://www.sesarju.eu/projects/CORUSXUAM).
• Commission Implementing Regulation (EU) 2021/664, Articles 8-15 — mandatory U-space services constituting the U2 regulatory floor (authoritative source — not in local library; see https://eur-lex.europa.eu/eli/reg_impl/2021/664/oj/eng).
• ICAO UTM Framework Edition 4 (May 2023) — stepped UTM implementation approach, core services by complexity level (authoritative source — not in local library; see https://www.icao.int/utm-guidance).
• EUROCONTROL U-space Implementation Monitoring Report (2020) — initial tracking of U1/U2 service readiness across European States (authoritative source — not in local library; see https://www.eurocontrol.int).

The seven functional axes#

U-space and UTM can be decomposed into seven functional threads. Each thread is a coherent axis of capability that can be analysed, designed, and implemented semi-independently, though all seven interact at execution time. Together they constitute the complete service ecosystem that makes scalable unmanned aviation possible.

Thread 1 — Identification#

The identification thread covers everything needed to know who is operating, what aircraft is in the air, and where it is at any moment.

Key functions:

• UAS operator registration — national registry linking legal entity to a registered operator ID.
• UAS registration — unique serial number and, where mandated, a registration mark linked to the operator.
• Remote identification (broadcast) — the UAS transmits a standard RF signal (typically 2.4 GHz or 900 MHz) carrying: UAS ID, current position, altitude, course/speed, operator ID, and emergency status.
• Network identification — the USSP aggregates broadcast identification data and makes it available to authorised parties (regulators, law enforcement).
• Authentication — assurance that the transmitted identity is genuine (cyber-threat: spoofing of identification broadcasts).

Standards in this thread include ASTM F3411 (Remote ID standard) and EUROCAE ED-282 / RTCA DO-392 for remote identification interoperability.

Thread 2 — Authorisation (Strategic deconfliction)#

The authorisation thread manages the pre-flight negotiation of operational volumes and issues the flight authorisation.

Key functions:

• Flight intent submission: operator submits a 4D operational volume (or trajectory) to the USSP.
• Geo-zone validation: the USSP checks the intent against active prohibited and restricted zones.
• Strategic deconfliction: the USSP checks the intent against all other active authorisations in the same airspace (via the CISP cross-USSP data pool).
• Authorisation issuance: the USSP issues an authorisation confirming the 4D operational volume, with any imposed conditions.
• ATS coordination: in controlled airspace, the USSP coordinates with the ATS unit via the CISP before issuing the authorisation.

The authorisation thread is the primary safety mechanism. Strategic deconfliction in 4D space before operations begin is far more efficient than tactical conflict resolution in the air.

Thread 3 — Traffic information#

The traffic information thread provides UAS operators with real-time situational awareness of manned aviation in their operational environment.

Key functions:

• Aggregation of manned aircraft surveillance data from multiple sources: ADS-B, transponder SSR returns redistributed via the CISP, ADS-L (used by light aircraft in Europe).
• Redistribution to USSPs, which push the data to operators whose authorised volumes are proximate to detected manned traffic.
• Triggering of operator alerts when a manned aircraft enters or approaches the authorised operational volume.

This thread depends on Thread 1 (Identification) on the manned side: Regulation (EU) 2021/666 makes electronic conspicuity mandatory for manned aircraft in U-space airspace so that light aircraft (which may not carry transponders) are visible to USSPs.

Thread 4 — Conformance monitoring#

The conformance monitoring thread runs during the flight and provides a closed-loop safety net.

Key functions:

• Real-time comparison of the UAS's reported position and altitude against the authorised operational volume.
• Detection of breach when the UAS goes outside the authorised volume beyond defined tolerance margins.
• Automated alerting cascade:
  1. Alert to the UAS operator.
  2. Alert to other UAS operators in the vicinity.
  3. Alert to other USSPs in the same airspace.
  4. Alert to the relevant ATS unit (which must acknowledge).
• Logging of conformance data for regulatory oversight.

Conformance monitoring is an optional service under EU 2021/664 that Member States activate based on airspace risk assessment. It becomes mandatory in complex or high-density U-space airspace.

Thread 5 — Geo-fencing and geo-awareness#

The geo-fencing/geo-awareness thread manages the dynamic airspace picture and ensures UAS operations stay within applicable constraints.

Key functions:

• Maintenance of a dynamic map of UAS geographical zones: prohibited zones, restricted zones (with conditions), conditional zones.
• Authoritative distribution of that map to USSPs and operators via the CISP, with update latency low enough to catch newly activated TFRs before or during flight.
• Onboard geo-fencing: the UAS's flight management system enforces geo-zone compliance autonomously, preventing the aircraft from entering prohibited space even if connectivity is lost.
• Dynamic TFR management: when an emergency helicopter is dispatched or a major public event activates a temporary restriction, the new constraint propagates to all active operators in the affected area within seconds.

This thread is the bridge between the regulatory airspace picture (maintained by the competent authority and ATS units) and the operational reality of individual UAS flights.

Thread 6 — Weather information#

The weather thread provides UAS-relevant meteorological data, distinct from standard aviation MET products which are designed for aircraft flying at altitude and speed well beyond small UAS performance envelopes.

Key functions:

• Wind speed and direction at low levels (0-300 ft AGL), including gusts and turbulence relevant to multirotor operations.
• Precipitation type and intensity (icing risk for electric aircraft; camera degradation for inspection missions).
• Visibility at low level (affects safe operations of BVLOS aircraft relying on ground-based sensors).
• Micro-scale forecasting for urban canyons where wind effects differ dramatically from synoptic forecasts.

The weather information service is optional under EU 2021/664, but is expected to become standard in U3 and U4 environments where automated decision-making replaces manual meteorological checks.

Thread 7 — ATC interface#

The ATC interface thread manages the boundary and coordination between UTM/U-space and conventional air traffic management.

Key functions:

• CISP-to-ATC data sharing: the ATS unit receives aggregated UAS traffic pictures from the CISP for situational awareness.
• Authorisation coordination: in controlled airspace, the USSP must obtain agreement from the ATS unit before issuing a flight authorisation (or the ATS unit participates in the CISP-mediated deconfliction process).
• Constraint injection: the ATS unit can push constraints into the UTM system (for example, closing a portion of U-space airspace due to an IFR traffic surge) via the CISP.
• Contingency/emergency handover: when a UAS declares an emergency or experiences a C2 link failure, the UTM system escalates to ATC via defined protocols; ATC may take command authority.
• UTM-ATM boundary management: defining which airspace is UTM-managed and which is ATC-managed, and the conditions for transitions.

This thread is the most complex because it requires bilateral trust between two fundamentally different systems — one voice-driven and authority-based (ATC), the other automated and service-based (UTM).

Nested hierarchy of functions (auto-viz trigger)#

• Identification thread
  • Operator registration
    • National registry linkage
    • Legal entity verification
  • Aircraft identification
    • Broadcast remote ID
    • Network aggregation
• Authorisation thread
  • Pre-flight
    • Geo-zone validation
    • Strategic deconfliction
  • In-flight
    • Authorisation amendment
    • Emergency re-authorisation

References#

• Commission Implementing Regulation (EU) 2021/664, Articles 8-15 — mandatory and optional service definitions across Threads 1-6 (authoritative source — not in local library; see https://eur-lex.europa.eu/eli/reg_impl/2021/664/oj/eng).
• Commission Implementing Regulation (EU) 2021/666, Article 1 — electronic conspicuity obligation supporting Thread 3 (traffic information) (authoritative source — not in local library).
• ICAO UTM Framework Edition 4 (May 2023), Chapters on UTM-ATM interface and emergency/contingency management — Thread 7 (authoritative source — not in local library; see https://www.icao.int/utm-guidance).
• SESAR CORUS-XUAM ConOps edition 4 (2023) — functional decomposition of U-space services supporting the thread model (authoritative source — not in local library; see https://www.sesarju.eu/projects/CORUSXUAM).
• Annex 2 (Rules of the Air), Appendix 4, §1.7 — RPAS shall meet performance and equipment requirements for the specific airspace, grounding Thread 1 and Thread 2 in Annex law.

Choosing the module to dissect#

The flight authorisation service is the central module of U-space. It is the point at which all other services converge: identification provides actor accountability; geo-awareness provides the constraint picture; traffic information provides the manned aircraft picture; conformance monitoring will verify the authorised operation in flight. Understanding the flight authorisation service end-to-end reveals how the ecosystem works as an integrated system.

Worked example: last-mile delivery BVLOS in a peri-urban U2 airspace#

Context#

An operator is running a commercial last-mile delivery operation in a designated U-space airspace over a medium-density suburban area. The airspace is Class G, surface to 300 ft AGL. A USSP (Provider Alpha) is certified for the airspace. The CISP for the airspace is separately designated. The operator has registered their UAS fleet and obtained a UAS operator certificate.

Step 1 — Operator submits flight intent#

The operator's dispatch system calls the USSP API with:

• Operator ID (registered)
• UAS serial number (registered)
• Flight volume: a 3D polygon (lateral boundary with 10 m buffer around the planned route) + altitude band (surface to 120 m AGL)
• Time window: T+0 to T+15 minutes (15-minute delivery window)
• Mission type: cargo, BVLOS

The USSP receives the intent and begins validation.

Step 2 — Geo-zone validation (Thread 5)#

The USSP queries the CISP for all active geo-zones overlapping the submitted 4D volume:

• No prohibited zones active in the volume.
• One conditional zone (school grounds) active 09:00-16:00 local time: the intended flight window is 14:30-14:45, which falls within the active restriction.
• The USSP rejects the original intent and returns a constraint to the operator: the route must be adjusted to avoid the school zone.

The operator adjusts the lateral boundary to pass 50 m clear of the school boundary and resubmits.

Step 3 — Strategic deconfliction (Thread 2)#

The USSP queries the CISP for all active flight authorisations in the same 4D volume:

• Flight Auth #1347: an inspection UAS operating for a utilities company, volume overlapping the eastern segment of the intended route, time window 14:20-14:50 (concurrent).
• The USSP calculates a space-time conflict: both operations use the same altitude band through the same lateral corridor during the same time window.

The USSP applies the conflict resolution rules. Inspection operations (Flight Auth #1347) have earlier time priority. The USSP offers the delivery operator two alternatives: a) Delay departure by 10 minutes (volume is clear by 14:50). b) Accept an alternative corridor 30 m further north.

The operator accepts option (a).

Step 4 — ATS coordination (Thread 7)#

The U-space airspace is in Class G, uncontrolled. No ATS coordination is required for Class G. (If the airspace were designated within controlled Class D, the USSP would have submitted a coordination request to the ATS unit via the CISP before issuing the authorisation; the ATS unit would have responded with acceptance or constraints.)

Step 5 — Authorisation issuance#

The USSP issues Flight Authorisation #1351:

• Operator ID: [operator reference]
• UAS serial: [aircraft reference]
• Authorised volume: [adjusted 4D polygon]
• Valid: 14:50:00 to 15:05:00 local
• Conditions: maintain within authorised volume; activate network identification before take-off; conformance breach tolerance 30 m lateral / 15 m vertical
• Expires if not activated (take-off) by 15:05:00

The authorisation is written to the CISP so all other USSPs in the airspace are aware of it for deconfliction against their own requests.

Step 6 — In-flight: network identification (Thread 1)#

The UAS activates its remote identification transmitter on take-off. Network identification broadcasts propagate to the USSP. The USSP confirms active identification and begins real-time tracking of the UAS position relative to the authorised volume.

Step 7 — In-flight: traffic information (Thread 3)#

At 14:53:20, the CISP detects a manned aircraft (light aircraft, ADS-L transponder, VFR flight) entering the U-space airspace at 400 ft AGL, 300 m to the north of the UAS route.

The USSP pushes a traffic advisory to the operator: "Manned aircraft detected 300 m north, 400 ft AGL, converging bearing 240 deg." The operator's ground control station displays the alert.

The manned aircraft is above the UAS at 400 ft and passes clear. No action required; the advisory is logged.

Step 8 — In-flight: conformance monitoring (Thread 4)#

At 14:55:10, the UAS experiences a wind gust and drifts 12 m east of the authorised lateral boundary. The USSP's conformance monitoring module detects the breach (12 m exceeds the 10 m warning threshold but is within the 30 m tolerance):

• Warning alert sent to operator (yellow level — advisory).
• The operator's autopilot corrects; UAS returns to authorised volume within 4 seconds.

If the deviation had reached 30 m, the conformance monitoring would have issued a red alert to the operator, nearby operators, other USSPs, and the ATS unit (even though the airspace is Class G, the ATS unit holds the log for safety oversight).

Step 9 — Completion and logging#

The UAS lands at the delivery location at 14:58:40. The operator closes the operation via the USSP API. The USSP marks Authorisation #1351 as completed and submits the conformance log to the CISP. The CISP archives the record for regulatory oversight purposes.

What this example illustrates#

The flight authorisation module demonstrates that U-space is an end-to-end transaction system, not a static database. The six mandatory/optional services interact in sequence: geo-awareness and strategic deconfliction shape the authorisation; network identification and traffic information provide real-time situational awareness during flight; conformance monitoring closes the loop. The CISP is the neutral data fabric connecting all participants.

References#

• Commission Implementing Regulation (EU) 2021/664, Articles 9, 10, 12, 13 — flight authorisation service requirements, USSP obligations, conformance monitoring obligations (authoritative source — not in local library; see https://eur-lex.europa.eu/eli/reg_impl/2021/664/oj/eng).
• Commission Implementing Regulation (EU) 2021/666, Article 1 — electronic conspicuity requirements enabling Step 7 (traffic information) (authoritative source — not in local library).
• ICAO UTM Framework Edition 4 (May 2023) — strategic deconfliction service definition, contingency procedures (authoritative source — not in local library; see https://www.icao.int/utm-guidance).
• EASA Easy Access Rules for U-space (May 2024), AMC and GM to Article 10 — guidance on flight authorisation service, deconfliction algorithms, and operator notification protocols (authoritative source — not in local library; see https://www.easa.europa.eu/en/domains/air-traffic-management/u-space).

What an enabler is#

An enabler is a prerequisite that must be in place before a U-space or UTM service can deliver its intended benefit. Deploying a USSP platform without the underlying enablers does not produce a working service ecosystem; it produces an expensive system that cannot function safely at scale.

Enablers fall into six categories.

1. CNS and communications infrastructure#

Command and control (C2) link#

Every BVLOS UAS operation requires a reliable, low-latency C2 link between the remote pilot station and the UAS. Without a continuous C2 link, the remote pilot cannot respond to conformance alerts, modify the trajectory, or activate contingency procedures. C2 link requirements include:

• Link reliability (minimum availability, typically 99.99% for safety-critical applications).
• Latency and throughput appropriate to the UAS type and operation.
• Spectrum allocation: dedicated protected spectrum or licensed spectrum with interference management.
• Frequency bands: L-band, C-band, and emerging 5G NR (New Radio) for urban/peri-urban operations; satellite-based C2 (Iridium, Starlink) for remote operations.

ITU/WRC frequency allocations for UAS C2 are a constraint on global deployment; different regions use different bands.

Network connectivity for USSP/CISP#

USSP and CISP platforms require reliable internet connectivity with defined quality-of-service parameters to deliver services in real time. Low-latency data exchange between USSPs (via the CISP) drives the timeliness of strategic deconfliction.

Surveillance and positioning#

Ground-based surveillance (ADS-B, MLAT) may be used by the CISP to track UAS positions for conformance monitoring (supplementing network identification broadcasts). GNSS is the primary positioning source for UAS; augmented GNSS (SBAS, GBAS, or RTK for precision applications) improves accuracy for low-level operations in cluttered urban environments.

Electronic conspicuity for manned aircraft#

Regulation (EU) 2021/666 requires manned aircraft in designated U-space airspace to broadcast electronic conspicuity signals. This requires general aviation aircraft to carry ADS-B Out (1090 MHz) or ADS-L (900 MHz, Europe) devices. The enabling infrastructure is a receiver network or the manned aviation's own transponder/ADS-B systems being readable by the CISP.

2. Regulatory and certification framework#

UAS operator certificate and UAS registration#

Before any UAS can fly in U-space airspace, the operator must be registered in the national UAS registry, and the UAS must carry a serial number and, where mandated, a registration mark. This is the administrative foundation (U1 baseline) on which all subsequent services depend.

USSP certification#

The competent authority must have a functioning certification process for USSPs. Regulation (EU) 2021/664 sets the requirements; EASA provides the AMC and GM. Without certified USSPs, there can be no designated U-space airspace.

Airspace risk assessment#

The competent authority must complete an airspace risk assessment to designate U-space airspace, determine which optional services are mandatory, and specify the applicable geo-zones. The risk assessment methodology is not prescribed in EU 2021/664; EASA provides guidance through the Easy Access Rules.

RPAS operating rules (Annex 2)#

For international operations, Annex 2, Appendix 4 provides the operating rules framework: authorization from the State of take-off, compliance with applicable airspace rules, equipment requirements. States must implement these through national legislation.

Remote pilot licensing#

PANS-TRG (Doc 9868), Chapter 8 defines the ICAO RPL (Remote Pilot Licence) competency framework. States must implement national remote pilot licensing schemes aligned with the ICAO competency model. A licensed remote pilot pool is a prerequisite for safe large-scale BVLOS operations.

3. Technical standards and interoperability#

Remote identification standards#

Remote identification requires harmonised technical standards so that receivers from one manufacturer can decode broadcasts from any compliant UAS. Relevant standards: ASTM F3411 (used in the US); EUROCAE ED-282 / RTCA DO-392 (European counterpart); and emerging ICAO harmonization work. Without common standards, identification systems are fragmented.

USSP-CISP interface standards#

All USSPs in a U-space airspace must exchange data with the CISP in a common format. EASA's AMC/GM and EUROCONTROL guidance define the interfaces; SWIM-compatible protocols are the direction of travel for convergence with ATM information management.

UTM-ATM interface#

The interface between USSP/CISP systems and ATC systems requires agreed message formats, latency requirements, and authentication. EUROCONTROL and EASA are developing reference implementations; global harmonization is an ICAO UTM Framework priority.

Cybersecurity#

USSP and CISP platforms are critical digital infrastructure. EU 2021/664 (as amended by Regulation 2023/203 from 22 February 2026) adds mandatory information security risk assessment, information security management, and incident response requirements for USSPs. Without cybersecurity governance, U-space systems are vulnerable to spoofing (false identification), injection of false geo-zone data, or disruption of flight authorisation services.

4. Airspace and procedure design#

U-space airspace designation#

Competent authorities must design and designate U-space airspace in a way that interfaces cleanly with the existing airspace structure. In uncontrolled airspace, this is straightforward. In controlled airspace (Class B-E), the designation requires coordination with the ATS unit and a defined coordination procedure.

Geo-zone management processes#

Geo-zone publication and update processes must be operationally aligned with the speed at which the dynamic picture changes. A TFR for an emergency helicopter must propagate to all USSPs and operators in seconds. This requires integration between the air traffic services NOTAM/TFR management systems and the CISP data pipeline.

UAS flight rules#

The SESAR CORUS-XUAM project developed a draft concept for U-space Flight Rules (UFR) — a UAS-specific equivalent of VFR/IFR that defines right-of-way, altitude rules, and separation responsibilities within U-space airspace. UFR is a conceptual enabler at U3/U4 level.

5. Human factors and training#

Remote pilot training#

Remote pilots flying BVLOS must be trained for:

• Emergency and contingency procedures (C2 link loss, UAS malfunction, communication failure).
• Interaction with U-space services: reading flight authorisations, responding to conformance alerts, interpreting traffic information.
• Aeronautical knowledge: airspace structure, weather interpretation, aviation safety culture.

Operator organisation and procedures#

The UAS operator must implement a safety management system, standard operating procedures for U-space operations, and crew resource management principles adapted to remote operations.

6. Institutional and inter-State#

International harmonization#

For BVLOS operations that cross national borders, States must harmonize their UTM frameworks. An operator flying a cross-border delivery mission requires compatible flight authorisation systems on both sides of the border. ICAO's UTM Framework provides the principles; bilateral agreements fill the operational gaps.

Competent authority cooperation#

When U-space airspace is designated in controlled airspace, the competent authority (CAA) and the ATS unit (ANSP) must cooperate closely. In some States these are the same entity; in others they are separate organisations requiring formal agreement on roles, responsibilities, and data sharing.

Law enforcement access#

Regulation (EU) 2021/664 requires that the competent authority can access real-time identification data. Law enforcement agencies need defined processes to access UAS identification data from USSPs or the CISP when investigating incidents or enforcing restrictions.

Summary dependency map#

References#

• Annex 2 (Rules of the Air), Appendix 4 — RPAS authorization requirements and airspace compliance obligations underpinning the regulatory enabler category.
• Doc 9868 (PANS-TRG), Chapter 8, §8.1.3 — ICAO RPL competency framework as the basis for remote pilot training programmes.
• Commission Implementing Regulation (EU) 2021/664, Articles 14-16 — USSP certification requirements, competent authority obligations, and information security provisions (authoritative source — not in local library; see https://eur-lex.europa.eu/eli/reg_impl/2021/664/oj/eng).
• Commission Implementing Regulation (EU) 2021/666, Article 1 — electronic conspicuity obligation enabling the traffic information service (authoritative source — not in local library).
• ICAO UTM Framework Edition 4 (May 2023) — cybersecurity and UTM-ATM interface principles (authoritative source — not in local library; see https://www.icao.int/utm-guidance).
• EASA Easy Access Rules for U-space (May 2024) — AMC and GM on USSP certification, airspace risk assessment, and information security (authoritative source — not in local library; see https://www.easa.europa.eu/en/domains/air-traffic-management/u-space).

The performance lens#

U-space and UTM are not deployed as abstract good governance. They are deployed because they are expected to deliver measurable benefits across the canonical Key Performance Areas (KPAs) drawn from the ICAO Global ATM Operational Concept (Doc 9854) and the GANP performance framework. Mapping U-space services to KPAs allows states, ANSPs, and operators to build the business case and to track whether deployments are delivering the promised benefits.

Key Performance Areas applicable to U-space/UTM#

The eleven KPAs from Doc 9854 / ICAO performance framework apply; the following seven are directly relevant to U-space/UTM at operational scale.

Safety#

Safety is the primary KPA. The central safety claim of U-space is that systematic strategic deconfliction, conformance monitoring, and traffic information reduce the probability of mid-air collision or ground impact to an acceptable level. Safety KPIs:

• Rate of unresolved strategic conflicts per 1,000 flight authorisations (target: near zero).
• Conformance breach rate (breaches per flight hour).
• Mid-air collision rate per 100,000 UAS flight hours.
• Incident and serious incident rate per 100,000 UAS operations.

Capacity / access#

U-space's core value proposition is enabling large numbers of UAS operations simultaneously. Capacity KPIs:

• Peak simultaneous authorised operations per unit volume of U-space airspace (operations per km2 per hour).
• Flight authorisation processing time (median, 95th percentile).
• Authorisation denial rate (operations rejected due to conflict or geo-zone; indicates whether capacity headroom is adequate).
• Queuing time for authorisation under high demand.

Security#

UAS introduce novel security threats: the identification thread must prevent spoofing; the authorisation thread must prevent unauthorised operations; the CISP must be cyber-resilient. Security KPIs:

• Remote identification failure rate (UAS in U-space airspace without valid identification broadcast).
• Geo-zone violation rate (authorised operations that breach a prohibited zone).
• Cybersecurity incidents affecting USSP or CISP availability.

Interoperability#

Multiple USSPs must interoperate for deconfliction to work. Interoperability KPIs:

• Cross-USSP deconfliction latency (time from filing with USSP A to conflict check against USSP B's operations via the CISP).
• API conformance rate of USSPs to common interface standards.
• Cross-border coordination coverage (proportion of border-crossing BVLOS routes covered by bilateral UTM harmonisation agreements).

Access and equity#

U-space should be open to all authorised operators, not just large commercial players. Access KPIs:

• Time-to-certification for new USSPs (indicates barriers to entry).
• Proportion of designated U-space airspace with at least two competing USSPs (market contestability).
• Latency and cost of flight authorisation for small operators vs. large operators.

Environment#

Low-level UAS operations have a different environmental footprint from commercial aviation but are not zero-impact, particularly at scale. Environment KPIs:

• Energy consumption per unit of cargo delivered (kWh/kg/km).
• Noise exposure from UAS operations in residential U-space airspace.
• Proportion of UAS fleet using electric propulsion (battery/fuel cell).

Predictability#

Operators and downstream logistics depend on reliable delivery windows. Predictability KPIs:

• Standard deviation of actual delivery time vs. planned delivery time.
• Rate of flight authorisation amendments required after initial issue (indicates instability in the deconfliction picture).
• USSP service availability (uptime).

KPA contribution by maturity level#

The following matrix scores each KPA by its principal benefit at each U-space maturity level (1 = some benefit, 2 = clear benefit, 3 = primary driver).

Performance objectives (selected)#

PO 1 — Enable safe BVLOS operations at commercial scale#

Measured by: authorisation processing time, strategic conflict rate, mid-air collision rate. Delivered by: flight authorisation service (Thread 2), strategic deconfliction via CISP, conformance monitoring.

PO 2 — Maintain manned aviation safety in shared airspace#

Measured by: UAS proximity events to manned aircraft per 100,000 UAS flight hours, ATC workload increase due to UAS. Delivered by: traffic information service (Thread 3), geo-awareness (Thread 5), the ATC interface thread (Thread 7).

PO 3 — Ensure accountability and regulatory traceability#

Measured by: remote identification failure rate, proportion of UAS operations with complete audit trail. Delivered by: network identification service (Thread 1), CISP archiving.

PO 4 — Enable a competitive market of U-space service providers#

Measured by: number of certified USSPs per designated airspace, new USSP certification time. Delivered by: interoperability standards (USSP-CISP interface), EASA certification framework.

Reporting and oversight#

• At EU level, EASA and national competent authorities monitor USSP performance against the certification standards defined in EU 2021/664.
• EUROCONTROL's U-space Implementation Monitoring Reports track readiness and deployment progress across European States.
• At ICAO level, the RPASP and the UTM Advisory Group collect global UTM implementation data to inform future editions of the UTM Framework and eventual SARPs.

Why performance data matters for planning#

A state deploying its first UTM service providers needs to demonstrate a credible safety case before opening high-density U-space airspace. The performance objectives and KPIs above provide the language to build that safety case: what safety level is required, how it is measured, and which services deliver each component of the target level. This mirrors the ASBU approach where modules are justified by their contribution to defined KPAs, not by the technology itself.

References#

• Commission Implementing Regulation (EU) 2021/664, Articles 8-16 — implicit performance requirements embedded in service definitions (flight authorisation deconfliction, conformance monitoring alert thresholds) (authoritative source — not in local library; see https://eur-lex.europa.eu/eli/reg_impl/2021/664/oj/eng).
• ICAO UTM Framework Edition 4 (May 2023) — safety and performance principles for UTM systems (authoritative source — not in local library; see https://www.icao.int/utm-guidance).
• Doc 9854 (Global ATM Operational Concept), Chapter 2 — KPA framework applicable to all ATM/UTM services.
• EUROCONTROL U-space Services Implementation Monitoring Report (2020) — early tracking of service deployment and readiness metrics (authoritative source — not in local library; see https://www.eurocontrol.int).
• SESAR CORUS-XUAM ConOps edition 4 (2023) — performance requirements and KPI targets for U2/U3 operations (authoritative source — not in local library; see https://www.sesarju.eu/projects/CORUSXUAM).

Two timelines to track#

As with any emerging aviation framework, keep two timelines distinct:

1. The regulatory and institutional timeline — when frameworks, regulations, and guidance were published.
2. The operational deployment timeline — when services went live at scale.

Key milestones table#

Regulatory preparation period (2021-2023)#

The two-year gap between adoption (April 2021) and applicability (January 2023) of the EU U-space package was used by:

• EASA: developing AMC and GM; producing draft guidance on USSP certification; convening consultation.
• Member States: beginning designation of pilot U-space airspace, establishing national registration systems, and adapting national oversight frameworks.
• Industry: USSP and CISP providers building and testing platforms against the regulatory requirements; participating in SESAR demonstration campaigns.

Key dates for Annex 2 RPAS provisions#

The Annex 2 RPAS chapter has two parallel sets of provisions — the pre-November 2026 provisions (aligned with national certification frameworks) and the post-November 2026 provisions (fully aligned with Annex 8 and Annex 6 Part IV). This dual-track structure means that until 25 November 2026, States are permitted to use national frameworks consistent with ICAO SARPs; from 26 November 2026, full alignment with the new ICAO certification standards is expected.

Looking ahead#

• SARPs development: the ICAO RPAS Panel (RPASP) is working on additional SARPs to embed UTM concepts normatively in the Annexes.
• AAM integration: eVTOL passenger-carrying operations will require U4-level services and additional certification standards beyond the current U-space regulatory package.
• Global harmonization: the ICAO UTM Framework process aims to converge national UTM implementations (FAA, EASA, CAAC, CASA, JCAB) around common principles; a future edition may propose consensus text for Annex-level SARPs.

References#

• Annex 2 (Rules of the Air), Amendment history table (lines 415, 426, 431, 439) — RPAS amendment milestones including UASSG, RPASP, and 26 November 2026 certification provisions.
• Doc 10019 (Manual on Remotely Piloted Aircraft Systems), Chapter 1, §1.2.13-§1.2.17 — UASSG establishment (2007), Circular 328 (2011), first RPAS SARPs (2012) historical sequence.
• ICAO UTM Framework Edition 4 (May 2023) — current edition (authoritative source — not in local library; see https://www.icao.int/utm-guidance).
• Commission Implementing Regulation (EU) 2021/664, Article 23 — applicability date 26 January 2023 (authoritative source — not in local library; see https://eur-lex.europa.eu/eli/reg_impl/2021/664/oj/eng).
• EASA Easy Access Rules for U-space (May 2024) — compilation of regulatory evolution and AMC/GM history (authoritative source — not in local library; see https://www.easa.europa.eu/en/domains/air-traffic-management/u-space).
• FAA UTM ConOps v2.0 (March 2020) — US implementation milestone (authoritative source — not in local library; see https://www.faa.gov/sites/faa.gov/files/2022-08/UTM_ConOps_v2.pdf).

Primary ICAO documents#

• Annex 2 — Rules of the Air, Appendix 4 (RPAS operating rules): §1.1-§1.7 general operating rules; §2.1 certification; §2.2 operator certificate; §2.3 remote pilot licensing. Key RPAS amendment dates: 2012 (first SARPs), 2021 (Amdt 47 — RPAS certificates and authorizations), 2026 (Amdt 49 — full Annex 8/6 alignment applicable 26 November 2026).
• Annex 2 — Rules of the Air, §1 Definitions: normative definitions of remotely piloted aircraft (RPA), remotely piloted aircraft system (RPAS), and detect and avoid.
• Doc 10019 — Manual on Remotely Piloted Aircraft Systems (RPAS), 1st edition. Chapter 1 §1.2: Chicago Convention Article 8 background, ICAO UASSG history, Circular 328 origin. Chapter 10 §10.2-§10.3: DAA hazards and airspace integration requirements.
• Doc 9868 — PANS-Training (PANS-TRG), Chapter 8: Remote Pilot Licence (RPL) competency framework, RPAS instructor qualifications, RPL examiner requirements.
• Circular 328 — Unmanned Aircraft Systems (UAS), March 2011: the first ICAO circular providing States with an overview of integration issues that RPAS raise across the Annexes.
• ICAO UTM Framework Edition 4 (May 2023): UTM definition, core UTM services (strategic deconfliction, tactical conflict advisory, manned aircraft interface, conformance monitoring, emergency/contingency management), UTM-ATM interface principles, Advanced Air Mobility considerations. Authoritative source — not in local library. URL: https://www.icao.int/sites/default/files/left-menu-pdfs/UTM%20Framework%20Edition%204.pdf
• ICAO UTM Framework Editions 1-3 (2019, 2020, 2021): foundational UTM concepts, iterative expansion to ATM boundaries and deconfliction. Not in local library. Landing page: https://www.icao.int/utm-guidance

EU regulatory documents#

• Commission Implementing Regulation (EU) 2021/664 of 22 April 2021: U-space regulatory framework; mandatory services (Articles 8-11); optional services (Articles 12-13); USSP requirements (Article 14); competent authority obligations (Article 15); applicable from 26 January 2023. Not in local library. URL: https://eur-lex.europa.eu/eli/reg_impl/2021/664/oj/eng
• Commission Implementing Regulation (EU) 2021/665 of 22 April 2021: amends Regulation 2017/373 — ATM/ANS provider requirements in U-space airspace designated in controlled airspace; applicable from 26 January 2023. Not in local library.
• Commission Implementing Regulation (EU) 2021/666 of 22 April 2021: amends SERA.6005 — electronic conspicuity obligation for manned aircraft in U-space airspace; applicable from 26 January 2023. Not in local library. URL: https://eur-lex.europa.eu/eli/reg_impl/2021/666/oj
• Commission Implementing Regulation (EU) 2023/203: amends EU 2021/664 to add information security risk assessment, IS management, and incident response provisions for USSPs; applicable from 22 February 2026. Not in local library.
• EASA Easy Access Rules for U-space (May 2024 edition): consolidated Regulation (EU) 2021/664 text with AMC and GM (Issue 1 and subsequent updates). Not in local library. URL: https://www.easa.europa.eu/en/document-library/easy-access-rules/easy-access-rules-u-space-regulation-eu-2021664

SESAR documents#

• SESAR CORUS U-space Concept of Operations (volumes 1 and 2, 2019): foundational EU U-space ConOps; U1/U2/U3 service maturity model; operational concept for European UTM. Not in local library. URL: https://www.sesarju.eu/sites/default/files/documents/u-space/CORUS%20ConOps%20vol2.pdf
• SESAR CORUS-XUAM U-space ConOps edition 3.10 (July 2022 preliminary) / edition 4 (September 2023): extension to urban air mobility; vertiport management; U4 elaborated; eVTOL passenger-carrying operations. Not in local library. URL: https://corus-project.eu and https://www.sesarju.eu/projects/CORUSXUAM

FAA documents#

• FAA UTM Concept of Operations v2.0 (March 2020): US reference architecture; USS (UAS Service Supplier) network; UTMS-FAA interface; UAS Volume Reservations; performance authorizations; security. Not in local library. URL: https://www.faa.gov/sites/faa.gov/files/2022-08/UTM_ConOps_v2.pdf

EUROCONTROL publications#

• EUROCONTROL U-space Services Implementation Monitoring Report (2020): first pan-European tracking of U-space service deployment readiness; baseline data on national U1/U2 progress. Not in local library. URL: https://www.eurocontrol.int/sites/default/files/2020-09/uspace-services-implementation-monitoring-report-2020-1-1.pdf

External links (authoritative sources)#

• https://www.icao.int/utm-guidance - ICAO UTM Guidance landing page
• https://www.easa.europa.eu/en/domains/air-traffic-management/u-space - EASA U-space domain
• https://eur-lex.europa.eu/eli/reg_impl/2021/664/oj/eng - EU 2021/664 full text
• https://skybrary.aero/articles/regulation-2021664-u-space-regulatory-framework - SKYbrary summary
• https://www.sesarju.eu/projects/CORUSXUAM - SESAR CORUS-XUAM ConOps publications
• https://www.faa.gov/sites/faa.gov/files/2022-08/UTM_ConOps_v2.pdf - FAA UTM ConOps v2.0