This folder contains ten files covering the integration of commercial space launch and re-entry operations into civil airspace. The lens is ATM management, not rocket engineering.

Files and reading order#

Source basis#

Primary ICAO library sources used across this folder:

• Doc 10184 (ICAO Assembly Resolutions, 41st Session, 2022) — Resolutions A40-26 (CST) and A41-8 (New Entrants).
• Doc 10209 (AN-Conf/14 Report, 2022) — §3.14 Space transport operations; distinction from higher airspace operations; guidance material mandate.
• Annex 11 (Air Traffic Services) — §2.33 danger/restricted/prohibited areas; formal definition of danger area.
• Doc 9554 (Activities Potentially Hazardous to Civil Aircraft Operations) — §3.2(c) launch and recovery of space vehicles; full coordination and NOTAM regime.
• Doc 10218 (ICAO Legal Committee 39th Session Report) — §3.11 re-entry of space objects; air law / space law interface.

External primary sources:

• FAA 14 CFR Part 450 (2021) — streamlined launch/re-entry licensing.
• FAA Space Data Integrator (SDI) programme.
• FAA airspace integration guidance for commercial space.
• ICAO Space Learning Group / Space Transport portal.

What commercial space integration is#

Commercial space integration is the discipline of managing the coexistence of commercial space launch and re-entry vehicles in airspace shared with conventional civil aviation. Its purpose is to protect conventional aircraft from debris hazards while minimising the ATM efficiency cost imposed by space operations — and to build, over time, the capability for both communities to operate from the same airspace simultaneously rather than sequentially.

The topic is bounded by the ATM interface, not by propulsion physics or vehicle design. The questions it addresses are:

• How is the airspace above a launch corridor reserved, closed, and reopened?
• What data does an ATC unit need in real-time to manage the transition?
• How does the launch window affect downstream traffic flows, and who coordinates that?
• What governance framework allocates responsibility between the launch licensing authority and the air traffic services provider?
• How does the system evolve from today's static segregation toward the dynamic integration that high-frequency operations require?

Where commercial space sits in the ICAO framework#

Space vehicles are not "aircraft" within the meaning of the Chicago Convention. They do not continuously derive lift from the atmosphere; they are therefore outside Annex 2 (Rules of the Air) and outside the standard Annexes 1 (Licensing), 6 (Operations), and 8 (Airworthiness). This creates a structural gap: a launch vehicle transiting controlled airspace at transonic speeds is generating hazards to which the full SARPS framework does not apply.

ICAO has addressed this gap at the Assembly level rather than through the Annexes. Resolution A40-26 (adopted at the 40th Session, 2019) was the first consolidated statement of ICAO's mandate in the areas where commercial space transport intersects with civil aviation:

• Accommodation of CST in airspace.
• Joint use of infrastructure.
• Co-location of airports and spaceports.
• Use of aircraft as launchers.
• Phases of flight of space vehicles that use the atmosphere for lift.

Resolution A41-8 (41st Session, 2022) brought space operations into the broader "new entrants" framework alongside UAS, directing ICAO to review SARPs and develop guidance material for harmonised integration, and calling on States to facilitate integration without compromising safety.

The Fourteenth Air Navigation Conference (AN-Conf/14, 2022, Doc 10209 §3.14) established that space transport operations are a distinct workstream from higher airspace operations (HAO), identified NOTAM coordination, ATFM concerns, and real-time data sharing as the immediate operational issues, and called for ICAO guidance material to address them. The conference also reiterated the need for collaboration with UNOOSA and COPUOS, recognising that air law and space law are subject to different legal regimes.

The legal tension#

The ICAO Legal Committee (39th Session, Doc 10218, §3.11) recorded a South African proposal to align space law with aviation law, noting the risk posed by re-entry of space objects to aviation safety. The proposal did not advance in that form; the consensus was that significant technical work was already ongoing and that space law and air law remained distinct regimes. This tension — growing operational overlap between domains governed by different legal frameworks — is the defining structural characteristic of the topic.

National frameworks#

In the absence of ICAO SARPs for commercial space, States with active launch programmes have developed national frameworks. The most operationally mature is the United States:

• FAA Office of Commercial Space Transportation (AST) issues licences under 14 CFR Part 450 (effective 2021), the streamlined launch and re-entry rule.
• FAA ATO Space Operations manages airspace coordination: Aircraft Hazard Areas (AHAs), TFRs, altitude reservations, and telemetry links.
• The Space Data Integrator (SDI), fielded from 2020, provides near- real-time vehicle telemetry to ATO units and enables early AHA closure.

Other active national frameworks include those of Russia (Roscosmos), France (CNES at Guiana Space Centre, Kourou), Japan (JAXA), and China (CNSA). Each feeds into the ICAO coordination regime through their national AIS/NOTAM offices and ATS authorities.

Why frequency matters#

Early commercial space operations were infrequent enough that static temporal segregation — close the airspace for the window, reopen it afterwards — imposed a small cost on conventional ATM. As launch frequency rises (the FAA licensed hundreds of commercial space launches in the years following Part 450's introduction), the cumulative delay and rerouting cost becomes a network-level ATM problem. This is why dynamic integration tools — real-time telemetry, performance-based AHA sizing, collaborative planning between launch operators and ANSPs — are the next required capability step.

References#

• Doc 10184 (Assembly Resolutions in Force, 41st Session, 2022), Resolution A40-26 — ICAO mandate in CST; intersection areas with civil aviation.
• Doc 10184, Resolution A41-8 — New Entrants framework; direction to ICAO to review SARPs and develop guidance for space operators.
• Doc 10209 (AN-Conf/14 Report, 2022), §3.14 — Space transport operations workstream; NOTAM coordination, ATFM concerns, real-time data sharing; UNOOSA/COPUOS collaboration.
• Doc 10218 (ICAO Legal Committee, 39th Session Report), §3.11 — Re-entry risk to aviation safety; air law / space law distinction.
• Annex 11 (Air Traffic Services), Chapter 2, §2.33 — Danger area definition and promulgation requirements.
• Doc 9554 (Activities Potentially Hazardous to Civil Aircraft Operations), Chapter 3, §3.2(c) — Launch and recovery of space vehicles.
• 14 CFR Part 450 — US streamlined launch and re-entry licensing, effective 2021 (authoritative source — not in local library).

The ATM interface for commercial space operations is built from six component families. Each family is described below: its function, the normative basis, and current operational state.

1. Aircraft Hazard Area (AHA) and danger area designation#

An Aircraft Hazard Area is the defined volume of airspace within which the probability of a conventional aircraft being struck by launch vehicle debris, jettisoned stages, or re-entry fragments does not exceed 1 in 1 000 000 per operation. In US practice, the AHA is implemented as either a Temporary Flight Restriction (TFR) under 14 CFR 91.143 or a stationary Altitude Reservation (ALTRV). In ICAO-framework States, the equivalent tool is the danger area under Annex 11, §2.33.

AHA geometry derives from trajectory analysis: the nominal flight path plus a three-sigma lateral/longitudinal/vertical dispersion envelope based on vehicle performance and failure probability. The result is a volume that is typically wider at the lower altitude bands (where a propulsion failure produces the widest debris footprint) and narrows as the vehicle climbs through controlled airspace.

The Annex 11 standard requires each danger area to be as small as practicable and to be contained within simple geometrical limits so as to permit ease of reference (§2.33.5 Recommended Practice). This requirement drives the precision trajectory analysis that is needed to avoid unnecessarily large airspace closures.

Key component facts:

• Location, size, and duration are calculated per launch.
• Promulgated via NOTAM (at least 7 days advance notice per Annex 15 / Doc 9554; AIRAC cycle recommended for recurring operations).
• In the US, the ATO publishes an Airspace Management Plan per operation.
• AHAs may be layered: different volumes for different flight phases (initial climb, transonic regime, upper atmosphere transit).

2. Launch and re-entry phases in the ATM context#

The flight profile of a launch vehicle creates different ATM challenges at each phase:

• Pre-launch hold and countdown — airspace is reserved but not yet activated; conventional traffic continues routing plans.
• Initial climb (0 to ~FL 600 / approximately 18 km) — vehicle transits controlled airspace; AHA active; TFR or danger area closes the volume to non-participating aircraft.
• Transonic and supersonic regime — maximum lateral dispersion; largest horizontal footprint; highest potential for debris field.
• Upper atmosphere / edge of controlled airspace — vehicle exits the altitude band where ATC separation applies; AHA may be deactivated for lower altitude bands as cleared.
• Re-entry (for orbital or sub-orbital vehicles) — reverse sequence; AHA re-activated for the descent corridor; re-entry heating phase produces debris risk if vehicle breaks up.

Sub-orbital vehicles (which do not reach orbital velocity) transit the climb and re-entry phases within a shorter time window but with a smaller horizontal footprint; the profile is more akin to a ballistic arc than a sustained trajectory.

3. Spaceports and airport co-location#

A spaceport is a launch and landing facility for space vehicles. It may be co-located with or adjacent to an existing airport (Class C/D/E airspace), a remote coastal site, or an offshore platform. Co-location creates ATM complexity beyond the launch window: runway sharing, taxiway routing, and the need for approach path deconfliction when the space vehicle is on final approach for a runway landing (SpaceX Falcon 9 and Starship return-to-launch-site profiles are operational examples).

Assembly Resolution A40-26 specifically recognises spaceport co-location as within ICAO's mandate. Doc 9554 §3.2(c) and §3.5 require that ATS authorities coordinate launch and recovery operations even when the spaceport is located within existing controlled airspace, because the launch trajectory may extend into adjacent FIRs.

4. Real-time data and the Space Data Integrator (SDI)#

The Space Data Integrator is the FAA's first operational tool for near-real-time situational awareness of a launch vehicle in flight. It receives telemetry data — position, altitude, speed, trajectory deviation — from the launch operator's ground station and displays it at FAA ATO facilities. SDI does not issue ATC clearances and does not replace the published AHA; it supplements it by confirming vehicle performance against the nominal trajectory.

SDI's primary operational benefit is enabling early AHA closure. When the vehicle confirms normal performance and safely clears a designated altitude band, the ATO can close (deactivate) the corresponding portion of the AHA in near-real-time, rather than holding the full published window duration. The FAA reports that airspace has been reopened within approximately three minutes of vehicle transit in operationally nominal scenarios.

The SDI model is the architectural precedent for the broader dynamic integration concept: a data link between launch operator and ANSP that carries trajectory conformance information and enables event-driven airspace management rather than schedule-driven management.

5. ATFM coordination#

A launch window affecting a major oceanic or continental route creates an ATFM problem in addition to an airspace problem. Flights already airborne or in the planning horizon need alternative routing or delay absorption. The current regime treats this as a hazardous-activity coordination process under Doc 9554, which requires coordination with "all air traffic services authorities responsible for providing services in the airspace concerned" (§3.5). The NOTAM and the AIRAC cycle are the primary notification tools.

AN-Conf/14 (Doc 10209 §3.14) explicitly listed ATFM concerns as a gap requiring ICAO guidance material. The gap is that there is no standard equivalent of the airline-ANSP collaborative decision-making (CDM) framework for launch operators and ANSPs.

6. Licensing authority interface with ATS authority#

A structural feature of the current regime is the separation between the launch licensing authority (FAA/AST, CNES, JAXA, etc.) and the air traffic services authority (FAA ATO, DGAC, JCAB, etc.). The licensing authority evaluates safety (debris probability, public risk); the ATS authority manages the airspace. Coordination between them is procedural rather than integrated. 14 CFR Part 450 formalises this by requiring licence applicants to demonstrate ATO coordination as part of the licence application.

The path to dynamic integration requires tightening this interface: real-time telemetry data must be authorised to cross from the launch operator to the ATS authority; trajectory updates must be translated into AHA modifications in time frames compatible with ATC planning horizons.

References#

• Annex 11 (Air Traffic Services), Chapter 2, §2.33 — Danger area definition; requirement for small, simple geometry; promulgation.
• Doc 9554 (Activities Potentially Hazardous to Civil Aircraft Operations), Chapter 3, §3.2(c) — Launch and recovery of space vehicles as hazardous activity.
• Doc 9554, Chapter 3, §3.5 — Coordination with all ATS authorities in affected airspace.
• Doc 9554, Chapter 4, §4.3 — NOTAM publication with seven-day advance notice; AIRAC cycle for recurring operations.
• Doc 10209 (AN-Conf/14 Report, 2022), §3.14 — ATFM concerns and real-time data sharing as gaps requiring ICAO guidance.
• Doc 10184 (Assembly Resolutions, 41st Session), Resolution A40-26 — Spaceport co-location within ICAO mandate.
• FAA Space Data Integrator (SDI), https://www.faa.gov/newsroom/space-data-integrator-sdi-0 — near-real-time telemetry for AHA closure (authoritative source — not in local library).
• 14 CFR Part 450 — AHA definition; ATO coordination requirement; licence application process (authoritative source — not in local library).

For this topic the "Blocks" axis maps integration maturity: how the relationship between commercial space operations and conventional ATM evolves from today's static segregation toward a fully dynamic, data-driven coexistence. The three-stage model below is derived from the FAA's own roadmap, the AN-Conf/14 guidance-material mandate (Doc 10209 §3.14), and the general ICAO principles on flexible airspace use cited in A41-8.

Stage 1 — Static Segregation#

Defining characteristic. The airspace closure is determined entirely before the launch, based on worst-case trajectory analysis. The published window is held in full regardless of actual vehicle performance. No real-time data link exists between the launch operator and ATC.

Tools used. Danger area or TFR activated by NOTAM for the full window. Conventional traffic is rerouted or held before and during the window. The window includes pad time, launch countdown, vehicle transit, and a post-transit clearance margin.

Operational cost. Delay and rerouting proportional to the window duration and the traffic density in the affected volume. At low launch frequencies (a few per year per site), this cost is manageable. At the higher frequencies (multiple per week) now characteristic of high-rate launch sites, the cumulative delay becomes a network-level ATM problem.

Current applicability. This is still the norm in most States with launch capability. It is also the baseline for any new launch programme. Doc 9554 and Annex 11 provide the full normative basis for Stage 1.

Representative enabling documents. Annex 11 §2.33; Doc 9554 §3.5–4.4; Annex 15 Chapter 5 (NOTAM specifications).

Stage 2 — Reduced / Dynamic Hazard Areas#

Defining characteristic. The AHA geometry is reduced from the worst-case envelope to a performance-based envelope calculated against the specific vehicle and trajectory. A near-real-time telemetry link allows the ATS authority to confirm vehicle performance and close AHA sectors (altitude bands, lateral segments) as the vehicle clears them, rather than holding the full window.

Tools used. FAA SDI (fielded from 2020) is the primary operational implementation. The operator transmits position and deviation data; the FAA ATO unit confirms clear-of-AHA and issues early airspace reopening notification. ATFM coordination is more formalised, with traffic management initiatives aligned to the launch window and early- release procedures activating when nominal performance is confirmed.

Operational gain. The FAA reports that AHAs have been cleared and airspace reopened in approximately three minutes after vehicle transit in nominal scenarios, against window durations that would otherwise extend 15 to 60 minutes.

Current applicability. Operational in the United States for licensed launches under 14 CFR Part 450. Not yet standardised at ICAO level; the AN-Conf/14 mandate for guidance material (Doc 10209 §3.14) is aimed partly at enabling other States and FIRs to implement equivalent capabilities.

What is needed to advance. Standardised data formats for telemetry exchange; agreements between launch operators and ATS authorities on data rights and security; liability frameworks for early AHA closure decisions.

Stage 3 — Just-in-Time Dynamic Integration#

Defining characteristic. The AHA is generated dynamically based on the actual, real-time trajectory conformance of the vehicle. Reservations are released automatically altitude-band by altitude-band as the vehicle clears each band. Conventional traffic planning treats the launch operator as a participant in the collaborative decision-making process — equivalent in concept to how an airline operations centre participates in network management.

Tools needed. This stage requires capabilities that are not yet standardised:

• Automated trajectory conformance monitoring with AHA boundary adjustment in near-real-time.
• Standardised data exchange protocol between launch operator systems and ANSP ATFM/ATM systems (analogous to FF-ICE for conventional flights).
• CDM framework integrating launch windows into network flow management plans.
• ICAO SARPs or guidance material defining the data interface and responsibility allocation.

Horizon. The AN-Conf/14 guidance material mandate (2022) is the first step. ICAO has not yet published SARPs for this stage. FAA is developing additional SDI capability and exploring integration with Traffic Flow Management System (TFMS). A reasonable horizon for initial ICAO guidance material is the mid-2020s; for SARPs, the early 2030s.

Relationship to ASBU framework. No formal ASBU module exists for commercial space integration. The analogous ASBU threads are NOPS (network operations), SWIM (information sharing), and the future RPAS-style new-entrant modules. Once ICAO develops SARPs, it is expected that commercial space integration will be incorporated as an extension of the new-entrant framework (Resolution A41-8).

Summary comparison#

References#

• Doc 10209 (AN-Conf/14 Report, 2022), §3.14 — NOTAM coordination, ATFM concerns, and real-time data sharing as gaps; guidance material mandate.
• Doc 10184, Resolution A41-8 — Flexible airspace use principle applied to new entrants including space operators.
• Annex 11 (Air Traffic Services), Chapter 2, §2.33.5 — Danger areas should be as small as practicable.
• Doc 9554, Chapter 3, §3.9(a) — Objective to select smallest possible airspace consistent with activity goals.
• FAA Space Data Integrator (SDI), https://www.faa.gov/newsroom/space-data-integrator-sdi-0 — Stage 2 implementation (authoritative source — not in local library).
• FAA Airspace Integration, https://www.faa.gov/space/airspace_integration — AHA sizing, early closure, Airspace Management Plans (authoritative source — not in local library).

Six functional axes together constitute the work programme for commercial space integration into ATM. The axis names follow the ASBU thread convention in form (functional area, not vehicle type).

Thread 1 — Airspace Design and Hazard Area Management (AHA)#

This thread covers the geometry and lifecycle of the airspace reservation used to protect conventional aircraft from launch and re-entry hazards.

Key activities:

• Trajectory analysis and AHA calculation (worst-case vs. performance- based envelope).
• Danger area and TFR designation; NOTAM preparation.
• Geometry optimisation: smallest practicable volume consistent with the 1-in-1 000 000 debris impact probability standard.
• Altitude-band zoning: separate AHA volumes for initial climb, transonic regime, and re-entry.
• Procedures for partial deactivation as the vehicle clears each band.

Normative basis: Annex 11 §2.33 (danger area designation); Doc 9554 §3.2, §3.5, §3.9 (coordination and minimisation principles); Annex 15 Chapter 5 (NOTAM specifications); 14 CFR Part 450 (AHA calculation requirements in the US).

Thread 2 — Real-Time Tracking and Space Data Integration (SDI)#

This thread covers the data link between launch operators and ATS authorities that carries near-real-time telemetry on vehicle position, altitude, speed, and trajectory conformance.

Key activities:

• Design and operation of telemetry feeds from launch operator ground stations to ATO/ACC units.
• Display integration in ATC working positions.
• Procedures for AHA early closure decisions based on telemetry confirmation.
• Data security and liability frameworks for sharing proprietary vehicle telemetry with government ATS authorities.
• Extension of SDI-type capability to oceanic FIRs (where there is no radar and the ATC unit relies entirely on satellite telemetry and ADS-C equivalents).

Normative basis: FAA Space Data Integrator (SDI) is the primary operational example. No ICAO SARP exists yet; AN-Conf/14 called for guidance material addressing real-time data sharing.

Thread 3 — ATFM and Network Flow Impact#

This thread addresses the consequences for the conventional air traffic flow management network when a launch window closes or restricts a significant route or airspace volume.

Key activities:

• Advance coordination between launch operators and ATFM network management units (weeks ahead for trajectory planning; minutes ahead for real-time release).
• Traffic Management Initiatives (TMIs): rerouting, miles-in-trail spacing, ground delay for flights that would transit the AHA.
• Early release procedures: cancelling a TMI as soon as the vehicle clears the AHA.
• ATFM cost quantification: delay minutes attributable to launch windows; trend analysis as launch frequency rises.
• Integration of launch schedules into network demand models used by ATFM planning units.

Normative basis: Doc 9554 §3.5 (coordination with all ATS authorities in affected airspace); Doc 10209 §3.14 (ATFM concerns cited as a gap by AN-Conf/14); ICAO Manual on Collaborative Air Traffic Flow Management (Doc 9971) for the general CDM framework.

Thread 4 — International and ICAO Harmonisation#

This thread covers the governance and regulatory work needed to create a globally consistent framework for commercial space-ATM integration.

Key activities:

• Development of ICAO guidance material for NOTAM coordination, ATFM, and real-time data sharing (AN-Conf/14 mandate).
• Coordination with UNOOSA, COPUOS, and the ICAO Space Learning Group.
• Eventual development of SARPs addressing: AHA data standards; liability for early closure; spaceport co-located operations; re-entry debris coordination.
• Bilateral FIR-to-FIR coordination agreements for transoceanic launch trajectories.
• Synchronisation with the ASBU framework once ICAO decides how commercial space integration will be reflected in the GANP.

Normative basis: Assembly Resolutions A40-26 and A41-8; AN-Conf/14 §3.14; Doc 9554 §3.4 (coordination for activities over the high seas); ICAO/UNOOSA/COPUOS cooperation mandate.

Thread 5 — Licensing and Regulatory Interface#

This thread addresses the coordination between the launch licensing authority and the ATS authority — two bodies with different mandates, different data, and different decision timelines.

Key activities:

• Licence application review: ATO coordination as a prerequisite for licence issue (as required by 14 CFR Part 450 in the US).
• AHA geometry verification: ATS authority review of the hazard calculation methodology.
• Contingency procedures: agreed AHA expansion protocols for off- nominal trajectories identified during countdown.
• Post-flight reporting: actual trajectory vs. AHA; debris impact data; network delay data.
• Cross-border notifications: the licensing State notifying ATS authorities in adjacent and downrange FIRs (Doc 9554 §3.5–3.6).

Normative basis: Doc 9554 §3.5–3.6 (notification and coordination requirements); 14 CFR Part 450 (ATO coordination mandate in licence application); Annex 15 Chapter 5 (NOTAM origination responsibilities).

Thread 6 — Transition Phases and Multi-User Airspace#

This thread addresses the operational procedures for managing the transition between "space-segregated" and "conventional ATM" modes, including spaceport departure and arrival sequences.

Key activities:

• Runway and taxiway procedures for co-located airport/spaceport operations.
• Approach path deconfliction when a space vehicle makes a powered vertical landing or winged landing on a shared runway.
• Coordination of the AHA activation/deactivation with the ATM unit holding pattern or diversion decisions for conventional aircraft.
• Contingency abort procedures: if a launch is scrubbed after TFR activation, rapid deactivation and conventional traffic resumption.
• Sub-orbital passenger service procedures: air traffic services applied to the conventional portions of the flight (below the effective altitude of airspace classification) and handoff to space operations authority for the sub-orbital arc.

Normative basis: Annex 11 §2.33.5 (danger areas as small as practicable); Assembly Resolution A40-26 (spaceport co-location within ICAO mandate); Doc 9554 §3.9 (coordination objectives including avoidance of closure or realignment of established ATS routes where alternatives exist).

Thread interdependencies#

The threads form a dependency chain in the direction of dynamic integration:

• Thread 1 (AHA geometry) sets the boundaries that Threads 2, 3, 5, and 6 must work within.
• Thread 2 (real-time data) is the enabler that unlocks the efficiency gains in Thread 3 (ATFM) and Thread 6 (transition).
• Thread 4 (international harmonisation) creates the standards that allow Thread 5 (licensing) to produce globally consistent outcomes.

References#

• Doc 9554, Chapter 3, §3.2(c), §3.5, §3.9 — Coordination requirements; minimisation of airspace closure; objectives for hazardous activity coordination.
• Annex 11, Chapter 2, §2.33 and §2.33.5 — Danger area designation and minimisation.
• Doc 10209 (AN-Conf/14 Report, 2022), §3.14 — ATFM concerns; real-time data sharing; guidance material mandate; UNOOSA/COPUOS collaboration.
• Doc 10184, Resolution A40-26 — Spaceport co-location; aircraft-as-launcher; ICAO mandate scope.
• Doc 10184, Resolution A41-8 — Flexible airspace use; SARPs review for new entrants including space.
• FAA Airspace Integration, https://www.faa.gov/space/airspace_integration — Threads 1, 2, 3 operational implementation (authoritative source — not in local library).

A module, in the ASBU sense, is the intersection of a Block (maturity stage) and a Thread (functional axis). For commercial space integration, the natural worked example is the management of a single orbital launch window using a dynamic Aircraft Hazard Area — the core operational unit of the Stage 2 capability.

Worked Module: Managing a Launch Window with a Dynamic AHA#

Thread: Airspace Design and Hazard Area Management (Thread 1) combined with Real-Time Tracking and Space Data Integration (Thread 2). Maturity stage: Stage 2 — Reduced / Dynamic Hazard Areas. Scenario: Orbital launch from a coastal spaceport, trajectory transiting Class A controlled airspace over approximately 12 minutes before the vehicle exits the top of the Flight Information Region. Nominal window: T-30 min to T+40 min (70-minute NOTAM activation).

Pre-launch phase (T-30 min to T-0)#

1. The launch operator activates the SDI data feed, confirming the telemetry link to the FAA ATO Space Operations position.
2. ATO Space Operations verifies the AHA coordinates match the published NOTAM and confirms no conflicting conventional traffic within the AHA.
3. Traffic Management Unit (TMU) activates the Traffic Management Initiative: affected en-route flights are rerouted to published alternatives; departures within the affected arrival flow receive ground delay or miles-in-trail spacing.
4. The TFR activation time is confirmed to all sectors whose airspace overlaps the AHA.
5. ATC sectors clear remaining aircraft out of the AHA. The AHA is formally activated.

Launch and initial climb (T-0 to T+4 min)#

6. Vehicle lifts off. SDI begins displaying vehicle position, altitude, speed, and lateral deviation against nominal trajectory.
7. ATO Space Operations monitors SDI. Controllers in the overlapping sectors have restricted display of the vehicle symbol; their primary obligation is to keep conventional traffic out of the active AHA.
8. If the vehicle deviates beyond the nominal trajectory by a defined threshold, the ATO Space Operations position alerts the controller team and the launch operator's Range Safety Officer.
9. If a launch abort occurs, the ATO Space Operations position broadcasts AHA deactivation to all sectors and cancels the TMI.

Transonic and upper atmosphere transit (T+4 to T+12 min)#

10. Vehicle reaches its maximum lateral dispersion altitude range (the wide point of the AHA funnel). SDI confirms the vehicle is tracking nominally.
11. As the vehicle climbs above the lower altitude band of the AHA (e.g. FL 180), ATO Space Operations confirms through SDI that the lower altitude band is clear and issues partial deactivation of the AHA for that altitude band.
12. Conventional traffic in the lower altitude band can be cleared by ATC immediately — no need to hold for the end of the published window.
13. Sequence repeats for each altitude band as the vehicle climbs through: FL 180 clear, then FL 240 clear, then FL 350 clear, until the vehicle exits the top of controlled airspace.

AHA closure and traffic resumption (T+12 to T+15 min)#

14. Vehicle exits the top of controlled airspace. SDI confirms the trajectory is nominal and the vehicle is clear of all AHA sectors.
15. ATO Space Operations transmits AHA deactivation to all sectors. Total active window duration: approximately 15 minutes.
16. The published NOTAM window of T+40 min (70 minutes total) was designed for the worst-case scenario. The actual closure at T+15 min saves approximately 25 minutes of AHA activation relative to the full window.
17. TMI cancelled. Traffic flows resume normal routing. Ground delay releases for departures that were held.

Post-operation#

18. ATO Space Operations deactivates the SDI display and archives the telemetry record.
19. The launch operator submits an actual-vs-nominal trajectory report to the licensing authority (FAA/AST) as required by 14 CFR Part 450.
20. The ATO Space Operations position logs delay statistics (ATFM delay minutes attributable to the launch window) for inclusion in network performance reports.

Quantitative impact summary for the worked example#

Note: figures are illustrative, derived from FAA SDI programme reporting that airspace has been reopened as little as three minutes after vehicle transit in nominal scenarios. Actual numbers depend on traffic density and route structure.

Contrast: Stage 1 (static) version of the same operation#

In Stage 1 (no SDI, no dynamic closure):

• The full 70-minute NOTAM window is held in all cases.
• No partial altitude-band releases are possible.
• All 30 affected en-route flights are rerouted regardless of whether the vehicle launches early, late, or on time.
• A scrubbed launch at T-5 min still holds the traffic for the remainder of the window unless a revised NOTAM can be issued (which has a minimum propagation time of 15–30 minutes via AFTN).
• The ATO has no in-flight confirmation of vehicle status; it relies entirely on radio communication with the launch site.

Key enablers required for the dynamic AHA module#

• Licensed SDI or equivalent telemetry data link from launch operator to ATS authority.
• ATO working position display integration for vehicle position.
• Agreed procedures for altitude-band partial closure (currently implemented via Letter of Agreement between FAA AST and FAA ATO).
• Trained ATO Space Operations controllers.
• Published contingency procedures for off-nominal vehicle performance.

References#

• Doc 9554 (Activities Potentially Hazardous to Civil Aircraft Operations), Chapter 3, §3.9 — Coordination objectives: smallest possible airspace, avoidance of ATS route closure.
• Doc 10209 (AN-Conf/14 Report, 2022), §3.14 — Real-time data sharing for airspace status as a key gap; ATFM concerns.
• FAA Space Data Integrator (SDI), https://www.faa.gov/newsroom/space-data-integrator-sdi-0 — three-minute airspace reopening benchmark (authoritative source — not in local library).
• FAA Airspace Integration, https://www.faa.gov/space/airspace_integration — AHA lifecycle and Airspace Management Plan process (authoritative source — not in local library).
• 14 CFR Part 450 — post-flight reporting requirements; ATO coordination in licence application (authoritative source — not in local library).

Enablers are the prerequisites that must be in place before a higher integration maturity stage can be achieved. They span communications and surveillance, procedures, training, regulation, certification, and institutional arrangements.

1. Communications, Navigation, and Surveillance (CNS)#

Telemetry data link#

The launch vehicle must carry a telemetry transmitter capable of broadcasting position, altitude, speed, and trajectory-deviation data to the ground station. The ground station must forward this data to the ATS authority in near-real-time. The SDI model relies on a TCP/IP link from the launch operator's ground system to the FAA NAS Enterprise Messaging Service (NEMS) infrastructure.

No ICAO SARP defines the telemetry data format for launch vehicles feeding ATC. The interface currently operates under bilateral agreements between individual launch operators and the FAA (or national ATS authority). Standardisation of the data format — analogous to how ADS-B or ADS-C standardised aircraft surveillance — is an open enabler requirement.

Surveillance coverage#

Conventional radar does not track launch vehicles above approximately FL 600 and is not available in oceanic/remote areas. For the transit phases that matter most to ATC (the first 60–90 seconds of flight through controlled airspace), secondary surveillance radar can detect the vehicle if it carries a Mode C/S transponder, but this is not standard on launch vehicles. The SDI telemetry feed is therefore the primary surveillance tool for ATC during a launch event.

For re-entry, the vehicle re-enters from above the coverage of most radars; the ATS authority relies again on operator telemetry plus advance knowledge of the nominal re-entry corridor.

GNSS dependency#

The launch vehicle's onboard position measurement (fed through the telemetry system) relies on GNSS. GNSS jamming or spoofing near a launch site degrades both the vehicle's guidance system and the SDI data quality. This is an emerging risk area as GNSS interference incidents near military conflict zones have increased.

2. Procedures#

AHA activation and partial closure procedures#

Each ATC facility that has airspace overlapping a launch AHA needs a facility-level procedure specifying: how the AHA is activated and deactivated; who has authority to issue a partial deactivation; what phraseology is used to advise pilots that an altitude band has reopened; and what contingency action to take if the vehicle deviates outside its AHA boundary.

In the US, these are captured in Letters of Agreement between FAA AST and the relevant ARTCC/TRACON facilities and in FAA Order 7110.65 (Air Traffic Control) section on space operations. At the ICAO level, no equivalent PANS-ATM provision exists yet.

NOTAM preparation and publication#

NOTAM preparation for a launch window is a specialised task requiring accurate coordinate conversion from the AHA geometry (which may be defined in launch trajectory coordinates) to the standard NOTAM geographic format. Errors in NOTAM geometry have contributed to incidents where aircraft penetrated active TFRs.

The AIRAC cycle is used for recurring operations at established launch sites. For new or modified trajectories, the Doc 9554 / Annex 15 minimum of seven days advance notice applies.

Contingency abort procedures#

If a launch is scrubbed or an abort occurs after AHA activation, the NOTAM deactivation message must reach all affected ATC units before traffic is cleared back into the previously restricted volume. The AFTN/SWIM NOTAM distribution network has a minimum propagation time that must be accounted for in the procedures.

3. Training#

ATC controller training#

Controllers at facilities that manage space operations require specialised training covering:

• Understanding launch vehicle flight profiles and what SDI/telemetry data represents.
• Partial AHA closure authority and procedures.
• Contingency procedures for off-nominal vehicle events (explosion, break-up, off-trajectory debris).
• Phraseology for advising pilots of AHA status.

This training is currently delivered by individual ANSPs (FAA Academy for US controllers). No ICAO standardised training curriculum exists for commercial space operations in ATC.

Pilot awareness#

Pilots in airspace adjacent to a launch corridor need to understand what an AHA NOTAM means, why a TFR may deactivate earlier than its published end time, and what to do if a TFR is not deactivated as expected. ICAO Annexes 1 and 6 do not address commercial space operations; pilot training syllabi do not typically include this topic.

4. Regulation and Certification#

Launch vehicle licensing interface with ATS authority#

14 CFR Part 450 (US) makes ATO coordination a licence requirement. No equivalent ICAO SARPs or PANS provision currently requires a launch operator to demonstrate ATS authority coordination as part of a national licence application. This gap means that in some States a launch can be licensed without the ATS authority having been formally consulted.

Liability framework for early AHA closure#

When the ATS authority closes an AHA early based on telemetry data, it assumes operational responsibility for the airspace. If a subsequent vehicle anomaly causes debris to reach altitude bands already cleared for conventional traffic, the liability question between the launch operator, the licensing authority, and the ATS authority is unresolved under current international law. This is a structural inhibitor to widespread adoption of Stage 2 dynamic closure procedures.

Space vehicle certification#

Space vehicles are not type-certificated under ICAO Annex 8. The absence of an international airworthiness framework for space vehicles means that the ATS authority cannot rely on the same airworthiness assurance it applies to aircraft when accepting a vehicle into the airspace planning process.

5. Institutional Arrangements#

ICAO Space Learning Group#

The Space Learning Group, operating under the ICAO Air Navigation Bureau with FAA chairmanship, is the primary ICAO forum for space-ATM integration work. It coordinates with UNOOSA and COPUOS on the boundary between air law and space law. The Group's work product is intended to feed the ICAO guidance material development mandated by AN-Conf/14.

ICAO/UNOOSA collaboration#

Assembly Resolution A40-26 and AN-Conf/14 both direct ICAO to coordinate with UNOOSA. UNOOSA maintains the space launch registry and has a different user community (national space agencies, commercial satellite operators) from ICAO's (States' civil aviation authorities, ANSPs, airlines). Building bridges between these two communities on shared airspace data is an institutional enabler for Stage 3.

Bilateral FIR-to-FIR agreements#

For transoceanic launch trajectories, the originating State's AIS distributes NOTAMs internationally but direct coordination between the launch site ATS authority and the oceanic FIR controlling authority is needed. Doc 9554 §3.5 requires this coordination, but the form and content of standing agreements between, for example, a US East Coast launch site and the Shanwick or Santa Maria Oceanic Control Area are managed bilaterally.

References#

• Doc 9554 (Activities Potentially Hazardous to Civil Aircraft Operations), Chapter 3, §3.5 — Coordination with all ATS authorities; bilateral agreement mechanisms.
• Doc 10209 (AN-Conf/14 Report, 2022), §3.14 — Guidance material mandate covering NOTAM coordination, ATFM, and real-time data sharing; institutional UNOOSA/COPUOS collaboration.
• Doc 10184, Resolution A40-26 — Mandate for ICAO/UNOOSA coordination on CST governance.
• Annex 15 (Aeronautical Information Services), Chapter 5 — NOTAM specifications; advance notice requirements; AIRAC cycle.
• FAA Space Data Integrator (SDI), https://www.faa.gov/newsroom/space-data-integrator-sdi-0 — telemetry link architecture (authoritative source — not in local library).
• 14 CFR Part 450 — ATO coordination as licence requirement; post-flight reporting (authoritative source — not in local library).

Performance framework#

No ICAO-published performance framework yet exists specifically for commercial space-ATM integration. The following applies the eleven Key Performance Areas (KPAs) from the Global ATM Operational Concept (Doc 9854) and the Manual on Global Performance (Doc 9883) to the commercial space integration domain. The numeric KPA matrix follows the convention established in the ASBU performance_objectives.md file for this workspace (1 = some benefit, 2 = clear benefit, 3 = primary driver).

The matrix is scored by integration stage (Stage 1 / 2 / 3) rather than ASBU Block, because no ASBU module catalogue yet covers this domain.

KPA definitions in this context#

KPA contribution by integration stage#

Safety is the primary driver across all stages. Capacity, efficiency, predictability, environment, and interoperability all improve materially between Stage 1 and Stage 3. Access and equity (fair access for space operators) is a Stage 1 concern already, since the static segregation model creates a regulatory barrier to entry for new launch operators who cannot obtain AHA approval.

Performance objectives#

PO-1: Ensure the probability of conventional aircraft debris impact is no greater than 1 in 1 000 000#

Primary KPA: Safety.

This is the foundational performance standard, derived from 14 CFR Part 450 and the underlying trajectory safety methodology. It is not yet an ICAO SARP. The standard requires that AHA geometry be calculated from a probabilistic debris dispersion model accounting for vehicle mass, trajectory, failure modes, and the density of conventional traffic in the corridor.

KPIs:

• Number of AHA boundary violations by conventional aircraft per year (target: zero).
• Post-flight actual trajectory vs. AHA boundary margin (distance from vehicle debris centre to AHA edge); trend over time.
• Number of cases where off-nominal vehicle trajectory exceeded the published AHA boundary.

PO-2: Minimise ATFM delay attributable to commercial space AHAs#

Primary KPA: Capacity; secondary: Flight efficiency, Environment.

The total delay imposed on the conventional ATM network by AHA activations is the most direct measure of the ATM cost of commercial space integration. It grows with launch frequency and shrinks as dynamic AHA closure capability is deployed.

KPIs:

• ATFM delay minutes per launch event (total and per affected flight).
• Number of conventional flights rerouted per launch event.
• AHA active duration (actual) vs. published window duration ratio. (A ratio of 0.2 means the AHA was cleared 80% earlier than the worst- case published window — the SDI model targets this range.)
• Annual total ATFM delay minutes attributable to commercial space operations; trend year-on-year as launch frequency and dynamic capability evolve.

PO-3: Reduce the time from vehicle transit clearance to AHA deactivation#

Primary KPA: Predictability; secondary: Capacity.

In Stage 1, the AHA remains active until the published end time regardless of vehicle performance. In Stage 2, telemetry allows early closure. In Stage 3, closure is automated by altitude band.

KPIs:

• Mean time from vehicle-clears-AHA (confirmed by SDI/telemetry) to AHA deactivation notification issued to ATC sectors (target: less than 3 minutes in Stage 2 per FAA SDI benchmark).
• Percentage of launches achieving early AHA closure vs. full window hold (target: greater than 80% in Stage 2 for nominal launches).

PO-4: Achieve internationally harmonised AHA data standards and NOTAM procedures#

Primary KPA: Interoperability.

Currently, AHA geometry and activation protocols differ between States. An ICAO guidance material document addressing NOTAM format, data sharing protocols, and cross-FIR coordination procedures would enable consistent treatment of launch corridors that cross multiple FIRs.

KPIs:

• Number of States that have published launch and re-entry coordination procedures conformant with ICAO guidance material.
• Number of bilateral FIR-to-FIR agreements for transoceanic launch corridors that include real-time data sharing provisions.
• NOTAM error rate for AHA coordinates (geometry errors requiring amendment after publication).

PO-5: Enable timely access for commercial space operators to shared airspace#

Primary KPA: Access and equity.

A static segregation regime with long lead times and uncertain AHA approval creates a high barrier to entry for new launch operators or new launch sites. A performance-based approval process with defined timelines and standardised methodology reduces this barrier.

KPIs:

• Mean time from AHA application to AHA approval (days) under national licensing frameworks.
• Number of launch licences issued per year (as a proxy for regulatory accessibility).
• Percentage of requested launch windows granted without modification to trajectory or timing.

Relationship to ICAO global performance monitoring#

ICAO has not yet established a reporting mechanism for commercial space-related ATM performance. AN-Conf/14 called for guidance material that would include performance metrics; once that material is published, it is expected to feed into the GANP review cycle alongside the ASBU module performance reporting.

In the interim, FAA publishes annual commercial space statistics that include launch frequency and AHA data. EUROCONTROL's Performance Review Body tracks delay attributable to space operations in European airspace on an ad hoc basis.

References#

• Doc 9854 (Global ATM Operational Concept) — the eleven KPA framework.
• Doc 9883 (Manual on Global Performance of the Air Navigation System) — KPI definitions and measurement methodology.
• Doc 10209 (AN-Conf/14 Report, 2022), §3.14 — Performance monitoring gaps; guidance material mandate.
• Doc 10184, Resolution A41-8 — Global harmonised framework for new entrants including performance measurement.
• FAA Airspace Integration, https://www.faa.gov/space/airspace_integration — AHA 1-in-1 000 000 safety standard; SDI three-minute benchmark (authoritative source — not in local library).
• 14 CFR Part 450 — probabilistic safety standard for AHA calculation; post-flight reporting (authoritative source — not in local library).

Two timelines to keep distinct#

When discussing commercial space integration dates, separate:

1. ICAO governance timeline — when ICAO Assemblies, conferences, and working groups acted on the topic.
2. Operational milestone timeline — when specific tools, rules, or capabilities became operational.

Key events table#

Key inflection points#

Three events define the modern structure of the topic:

1. AN-Conf/13 (2013) — ICAO first formally engages with CST as an air navigation conference topic. Produces the CST recommendation and establishes the regulatory agenda.

2. Assembly A40-26 (2019) and FAA SDI/Part 450 (2020-2021) — ICAO establishes its mandate; the US demonstrates Stage 2 integration capability. The combination defines the dual track: ICAO governance framework developing in parallel with national operational capability.

3. AN-Conf/14 (2022) — the transition from identifying the problem to mandating guidance material. The conference draws the boundary between space transport operations and higher airspace operations as distinct workstreams, and directs ICAO to fill the operational gaps.

References#

• Doc 10184 (Assembly Resolutions, 41st Session, 2022), Resolution A40-26 — Adopted at 40th Session (2019); defines ICAO CST mandate.
• Doc 10184, Resolution A41-8 — New Entrants; updated direction for space operations integration.
• Doc 10184, Resolution A41-3 — DPRK unannounced missile launches; principle that launches must not threaten civil aviation safety.
• Doc 10209 (AN-Conf/14 Report, 2022), §3.14 — Space transport workstream; guidance material mandate.
• Doc 10218 (ICAO Legal Committee, 39th Session), §3.11 — Air law / space law alignment; re-entry debris risk.
• FAA Space Data Integrator (SDI), https://www.faa.gov/newsroom/space-data-integrator-sdi-0 — SDI deployment 2020 (authoritative source — not in local library).
• 14 CFR Part 450, effective 27 March 2021 (authoritative source — not in local library).
• ICAO Thirteenth Air Navigation Conference, https://www.icao.int/Meetings/anconf13/Pages/default.aspx — 2013 AN-Conf/13 on CST (authoritative source — not in local library).

Consolidated ICAO and authoritative external references for the commercial space integration topic. Organised by source type.

ICAO Assembly Resolutions#

• Doc 10184 (Assembly Resolutions in Force, 41st Session, 2022), Resolution A40-26 — Commercial Space Transport (CST): defines ICAO's mandate in accommodation of CST in airspace, spaceport co-location, aircraft-as-launcher, lift-deriving flight phases; directs ICAO to coordinate with UNOOSA on CST governance.
• Doc 10184, Resolution A41-8 — New Entrants: places commercial space in the same framework as UAS; directs ICAO to review SARPs and develop guidance for harmonised integration within a global framework; recalls ICAO Global ATM Operational Concept principle that airspace restrictions should be transitory.
• Doc 10184, Resolution A41-3 — Unannounced missile launches by DPRK: establishes the principle that launches without advance notification violate the Convention on International Civil Aviation and threaten the safety of civil aviation.

ICAO Air Navigation Conferences#

• Doc 10209 (AN-Conf/14 Report, 2022), §3.14 — Space transport operations: distinct workstream from higher airspace operations; space vehicles do not meet the definition of aircraft; NOTAM coordination, ATFM concerns, stakeholder communication, real-time data sharing identified as immediate gaps; guidance material development mandated; UNOOSA/COPUOS collaboration called for.

ICAO SARPs and PANS#

• Annex 11 (Air Traffic Services), Chapter 2, §2.33 — Identification and delineation of prohibited, restricted, and danger areas; formal definition of danger area; promulgation requirements on initial establishment.
• Annex 11, Chapter 2, §2.33.5 — Recommended Practice: danger areas should be as small as practicable, contained within simple geometrical limits.
• Annex 15 (Aeronautical Information Services), Chapter 5 — NOTAM origination and publication; seven-day minimum advance notice for danger area activations; AIRAC cycle for recurring operations.
• Doc 9554 (Activities Potentially Hazardous to Civil Aircraft Operations), Chapter 3, §3.2(c) — Launch and recovery of space vehicles listed explicitly among activities requiring ATS coordination.
• Doc 9554, Chapter 3, §3.5 — Coordination with all ATS authorities responsible for airspace in the trajectory path; bilateral coordination for activities over the high seas.
• Doc 9554, Chapter 3, §3.9(a) — Coordination objective: smallest possible airspace; avoidance of ATS route closure or realignment unless no other options exist.
• Doc 9554, Chapter 4, §4.3 — NOTAM promulgation responsibility; seven-day advance notice standard; AIRAC cycle recommendation.

ICAO Legal Committee#

• Doc 10218 (ICAO Legal Committee, 39th Session Report), §3.11 — Re-entry of space objects: risk to aviation safety; South Africa proposal on alignment of air law and space law; ICAO-UNOOSA collaboration; distinction between air law and space law regimes.

ICAO performance and operational concept documents#

• Doc 9854 (Global ATM Operational Concept) — eleven KPA framework; trajectory management and flexible airspace use principles.
• Doc 9883 (Manual on Global Performance of the Air Navigation System) — KPI methodology; KPA definitions.
• Doc 9971 (Manual on Collaborative Air Traffic Flow Management) — CDM framework applicable by analogy to launch-ANSP coordination.

National regulatory documents#

• 14 CFR Part 450 (US Code of Federal Regulations, Title 14, Part 450) — Launch and Reentry Licensing, effective 27 March 2021; streamlined commercial space licensing; Aircraft Hazard Area (AHA) calculation requirement; ATO coordination as licence prerequisite; post-flight reporting (authoritative source — not in local library).

Authoritative external web sources#

• https://www.faa.gov/space/airspace_integration — FAA airspace integration overview: AHA lifecycle, SDI, Airspace Management Plans, TFR and ALTRV procedures.
• https://www.faa.gov/newsroom/space-data-integrator-sdi-0 — FAA Space Data Integrator (SDI): near-real-time telemetry, three-minute AHA closure benchmark.
• https://www.faa.gov/regulations_policies/faa_regulations/commercial_space — FAA commercial space regulations portal: 14 CFR Part 450 and related rules.
• https://www4.icao.int/space — ICAO space transport portal; Space Learning Group information.
• https://www.icao.int/new-and-emerging-activities-commercial-space-flight — ICAO new and emerging activities page for commercial space flight.
• https://www.icao.int/annual-report-2018/Pages/emerging-aviation-issues-commercial-space-transport.aspx — ICAO 2018 Annual Report on CST and AN-Conf/13 outcome.
• https://www.icao.int/Meetings/anconf13/Pages/default.aspx — ICAO Thirteenth Air Navigation Conference (AN-Conf/13, 2018) page.