Detailed working notes on ICAO airspace design. This folder expands the summary in topics/airspace_design.md into per-aspect files so each can be read on its own.

Files in this folder#

• overview.md — what airspace design is, regulatory anchor (Annex 11, PANS-ATM, PANS-OPS), and how planners use it.
• components.md — the building components of an airspace design: controlled vs. uncontrolled airspace, classes, ATS routes, TMAs, terminal procedures, holding, RNAV/RNP performance.
• blocks.md — airspace classes A–G as the structural "blocks" of controlled/uncontrolled airspace, including service and separation rules per class.
• threads.md — the design domains (en-route, terminal, aerodrome control zone, free route airspace, flexible use of airspace) and how they interlock.
• modules.md — anatomy of an airspace design "unit": route segment, TMA, sector, and how each is specified.
• enablers.md — supporting CNS infrastructure, separation standards, safety assessment, environmental assessment, and simulation.
• performance_objectives.md — KPAs (capacity, efficiency, environment, safety) and the KPIs that evidence them.
• timeline.md — Annex 11 amendment history, free route airspace evolution, and the PBN airspace concept timeline.
• references.md — consolidated ICAO and external references.

Reading order#

Start with overview.md, then components.md, then blocks.md and threads.md, then drill into modules.md, enablers.md, and performance_objectives.md. Use timeline.md for date context and references.md for citations.

Source basis#

Content is grounded in:

• ICAO Annex 11 (Air Traffic Services), in particular Chapter 2 (airspace classification, PBN, ATS route establishment, change-over points, significant points) and Appendix 1 (route designators).
• ICAO Doc 4444 (PANS-ATM), separation methods and minima, ATS surveillance services, ATFM and capacity management.
• ICAO Doc 8168 (PANS-OPS), Volumes I and II, instrument procedure design feeding SIDs, STARs, approaches and missed approach procedures into the airspace structure.
• ICAO Doc 9426 (Air Traffic Services Planning Manual), explicitly cited by Annex 11 §2.13 as guidance for ATS route establishment, sectorisation and airspace organisation.
• ICAO Doc 9613 (Performance-Based Navigation Manual), navigation specifications and route spacing criteria.
• ICAO Doc 9689 (Manual on Airspace Planning Methodology for the Determination of Separation Minima).
• ICAO Doc 9854 (Global ATM Operational Concept) for the performance framework against which a design is justified.
• EUROCONTROL Free Route Airspace concept and ERNIP Part 1 (Airspace Design Methodology) — regional realisation reference.

How this folder relates to the rest of the workspace#

topics/airspace_design.md is the public/clean version consumed by the web app. This topics_detailed/airspace_design/ folder is the longer treatment that supports it. Keep terminology aligned with the public file: ATS route, control area, TMA, CTR, airspace class, navigation specification, free route airspace, flexible use of airspace.

What airspace design is#

Airspace design is the structured organisation of a State's or region's airspace into Flight Information Regions (FIRs), control areas, terminal control areas, control zones, ATS routes, holding patterns, and reserved or restricted volumes, with associated classifications, navigation specifications, separation minima, and ATC sectorisation. It is the planning discipline that turns a volume of sky into a serviceable, safe, and efficient operating environment.

An airspace design is the upstream product. The downstream products are the AIP entries, instrument procedures, sector definitions, letters of agreement with neighbours, and controller training materials that the design generates.

Regulatory anchor#

Three ICAO instruments together define the design space.

Annex 11 — Air Traffic Services#

Annex 11 is the primary SARP. Key provisions:

• Chapter 2, §2.6 — classification of airspaces (Classes A–G), the service to be provided in each, and the separation applied.
• Chapter 2, §2.7 — performance-based navigation (PBN) operations; States prescribe navigation specifications, with reference to Doc 9613.
• Chapter 2, §2.10 — establishment of control areas, terminal control areas (TMAs), and control zones (CTRs).
• Chapter 2, §2.13 — establishment and identification of ATS routes, including protected airspace and safe spacing; expressly refers to Doc 9426 for guidance.
• Chapter 2, §2.14 — change-over points on VOR-defined route segments of 110 km / 60 NM or more.
• Chapter 2, §2.15 — significant points used to define ATS routes and to support position reporting.
• Chapter 2, §2.21 — establishment of minimum flight altitudes for each ATS route or control area.
• Appendix 1 — principles for the identification of navigation specifications and ATS routes other than SIDs and STARs.
• Attachment A — material related to VOR-defined ATS routes.

Doc 4444 — PANS-ATM#

The procedural counterpart. PANS-ATM Chapter 3 covers ATS system capacity and air traffic flow management. PANS-ATM Chapter 5 sets out separation methods and minima — the standards a design must respect when fixing route spacing, vertical envelopes, and sector size. Chapter 8 (ATS surveillance services) constrains design where surveillance separation applies.

Doc 8168 — PANS-OPS#

Volumes I and II of PANS-OPS govern the design of departure procedures, arrival procedures, holding, approach, and missed approach. The geometry produced by PANS-OPS is what a TMA must contain: an airspace design is incomplete until its terminal procedures fit inside the allocated control area with the obstacle and protection buffers required.

How planners use the framework#

For any candidate change to airspace structure — a new TMA, a new PBN STAR, a new free route area, a re-sectorisation — the design team answers four questions:

1. What operational benefit is targeted (capacity, flight efficiency, environmental impact, safety, accessibility)?
2. What structure is needed (route geometry, lateral and vertical limits, classification, navigation specification, holding, sector boundaries)?
3. What dependencies must be in place first (CNS coverage, fleet PBN equipage, controller training, AIP cycle, letters of agreement, environmental clearance)?
4. By when must the change be in service, and against which regional milestone (APAC Seamless ATM Plan, EUR ATM Master Plan, national air navigation plan)?

Why airspace design matters#

A poorly structured airspace caps capacity that ground systems and fleet equipage could otherwise unlock. Conversely, a well-structured airspace can deliver large efficiency gains (flight time, fuel, emissions) without new infrastructure — by re-routing, re-classifying, or de-cluttering the existing structure. Airspace design is therefore one of the highest-leverage activities in the GANP performance toolkit and feeds directly into the ASBU FRTO (Improved Operations through Enhanced En-Route Trajectories), APTA, CDO, CCO, and FUA modules.

Relationship to other topics in this workspace#

• PBN — supplies the navigation specifications used to define routes and procedures.
• ASBU — frames airspace design improvements as FRTO, APTA, CDO, CCO modules.
• FUA / Civil-Military — supplies the flexible-use mechanism that lets a design release reserved airspace dynamically.
• A-CDM, AMAN/DMAN, NOPS — operate the design once it is in place.

An airspace design is assembled from a small set of structural components. Each component has a definition in Annex 11, a procedural basis in Doc 4444 or Doc 8168, and a navigation basis in Doc 9613.

1. Controlled vs. uncontrolled airspace#

Annex 11 defines controlled airspace as "an airspace of defined dimensions within which air traffic control service is provided in accordance with the airspace classification." Anything outside the controlled volume is uncontrolled, and only flight information service and alerting service are provided. The first design decision for any volume is therefore: control the airspace, or leave it uncontrolled.

The decision is a function of traffic density, traffic mix (IFR/VFR/military), terrain, weather, surveillance and communication coverage, and the State's safety target level. Annex 11 §2.6 sets the service and separation that follows once a class is declared.

2. Airspace classes (A–G)#

Seven classes define the service and the separation provided. See blocks.md for the full per-class detail. The class assigned to a volume is the design lever that controls how much ATC effort and how much pilot responsibility the airspace consumes. Where two classes adjoin vertically, the less restrictive class applies at the common level (Annex 11 §2.6 Note).

3. Control areas, TMAs, and control zones#

Annex 11 distinguishes three primary controlled-airspace constructs:

• Control area — a controlled airspace extending upwards from a specified limit above the earth.
• Terminal control area (TMA) — a control area normally established at the confluence of ATS routes in the vicinity of one or more major aerodromes (Annex 11, definitions; §2.10).
• Control zone (CTR) — controlled airspace from the surface to a specified upper limit, surrounding an aerodrome.

Designers size lateral and vertical limits to contain departures, arrivals, holding, vectoring, and missed-approach geometry produced by PANS-OPS, with the required buffers.

4. ATS routes#

Annex 11 defines an ATS route as "a specified route designed for channelling the flow of traffic as necessary for the provision of air traffic services," characterised by:

• a designator (Appendix 1);
• track between significant points;
• distance between significant points;
• reporting requirements;
• lowest safe altitude.

Routes are established with protected airspace and safe lateral spacing (Annex 11 §2.13.1). The protection envelope and parallel route spacing depend on the navigation specification applied — closer spacing is permitted as accuracy and on-board performance monitoring improve (Doc 9613).

5. Significant points and change-over points#

• Significant points (Annex 11 §2.15) are the geographic anchors that define ATS routes and hold reporting. They may be navaid-based or named waypoints, expressed as 5LNC where required.
• Change-over points (Annex 11 §2.14) are mandatory on VOR-defined segments of 110 km / 60 NM or more, fixing the navaid each aircraft uses for primary reference.

6. Terminal procedures (SID, STAR, IAP)#

PANS-OPS Volume II defines the procedure design rules for SIDs, STARs, holding, approach, and missed approach. The TMA must contain the geometry these procedures produce, with the required obstacle and airspace protection buffers. PANS-OPS Volume I (Part III) governs departure procedure design and explicitly addresses CCO considerations; Part II/III addresses arrivals and CDO.

7. Holding patterns#

Holding pattern geometry, protection areas, and entry sectors are specified in PANS-OPS. Holding fixes are normally placed inside a TMA or terminal area with adequate vertical and lateral protection so that holding traffic does not foul the SID/STAR or adjacent sectors.

8. Reserved and restricted volumes#

Designs include prohibited, restricted, danger, and military areas (TRA/TSA). Modern designs treat these dynamically through the Flexible Use of Airspace (FUA) concept: civil and military shares are managed in time, not just in geography, so that civil traffic can use military volumes when not active.

9. Navigation specifications (PBN)#

Doc 9613 replaces sensor-specific routes with performance requirements. A navigation specification is defined by accuracy (95 percent total system error), integrity, continuity, functionality, and crew procedures. RNP specifications add on-board performance monitoring and alerting (OBPMA).

Typical applications:

• En-route oceanic / remote: RNP 10, RNP 4, RNP 2.
• En-route continental: RNAV 5, RNAV 2, RNP 2.
• Terminal SID/STAR: RNAV 1, RNP 1, A-RNP.
• Approach: RNP APCH (LNAV, LNAV/VNAV, LPV); RNP AR APCH for tailored procedures with reduced obstacle clearance corridors.

The State prescribes the navigation specification (Annex 11 §2.7.1), publishes it in AIP, and protects the route per Doc 9613.

10. Sectorisation#

The control area is divided into ATC sectors, each with a workload envelope (movements per hour, complexity, climb/descent mix). Sector boundaries are designed so that handoffs occur at low-workload points along the route, not in the middle of a turn or descent. Doc 9426 is the primary guidance document for sectorisation methodology.

11. Letters of agreement#

The design is incomplete without operational agreements with adjacent ANSPs, military authorities, and aerodrome operators that document transfer of control points, level allocation, coordination procedures, and abnormal/contingency arrangements.

Annex 11 §2.6 prescribes seven ATS airspace classes. Each class is a block of controlled or uncontrolled airspace with a defined service profile, separation rule, and pilot responsibility. The class is the single most important attribute the designer assigns to a volume: everything else (sectorisation, route spacing, communication requirements) follows from it.

Where two classes adjoin vertically at the same level, the less restrictive class applies at the common level (Annex 11 §2.6 Note).

Summary table#

Class A — "Controlled, IFR only"#

IFR flights only. ATC clearance required. All flights are positively separated. Used for upper airspace where the traffic is essentially all airline IFR. Common application: upper FIR levels (e.g. above FL245 in many European States, oceanic upper airspace).

Class B — "Controlled, IFR and VFR, all separated"#

Both IFR and VFR are admitted, both receive ATC clearance, and all flights are separated from each other. Heavy ATC workload because the controller must separate VFR from VFR. Used in dense terminal environments where VFR access is preserved but full separation is needed.

Class C — "Controlled, IFR / VFR separated; VFR / VFR informed"#

The most common class for busy TMAs and en-route control areas with mixed traffic. IFR is separated from IFR and from VFR; VFR receives traffic information on other VFR and avoids them. Provides ATC service to VFR without consuming the controller workload of VFR / VFR separation.

Class D — "Controlled, IFR / IFR separated; traffic info on VFR"#

IFR is separated from IFR. VFR is not separated, but receives traffic information on IFR and other VFR as practical. Common around medium- density aerodromes (CTR plus terminal area).

Class E — "Controlled, IFR / IFR separated; not for CTRs"#

IFR is separated from IFR. VFR access does not require clearance; VFR gets traffic information as far as practical. Class E is not used for control zones — a CTR must be Class A, B, C, or D. Class E is a useful en-route transition layer between dense terminal airspace and uncontrolled overlying airspace.

Class F — "Advisory service"#

Both IFR and VFR are admitted. Participating IFR receives an advisory service (separation from other participating IFR as practical, but not guaranteed). Flight information service is provided on request. Used selectively in some States as a transition class toward full Class E or D.

Class G — "Uncontrolled"#

Flight information service and alerting service only. No ATC separation. Pilots are responsible for traffic avoidance using see-and- avoid (VFR) or, for IFR in Class G where permitted, careful traffic self-coordination. Predominant in low-density continental and remote airspace below an upper controlled layer.

Choosing a class#

Annex 11 leaves the choice to the State, but the design test is:

1. What traffic mix is expected (IFR-only / IFR + VFR / VFR-dominant)?
2. What service does the user community need (ATC, advisory, FIS only)?
3. What CNS coverage exists (surveillance, two-way radio)?
4. What controller workload can the unit sustain (sector capacity)?
5. What is the safety target (collision risk versus ATC effort)?
6. How does the class fit the adjacent volumes — vertically and laterally — without creating awkward transitions for the pilot?

A common pattern in modern designs:

• Upper airspace — Class A (IFR only) for cruise traffic.
• TMA at major aerodromes — Class C (IFR + VFR with separation asymmetry).
• CTR at controlled aerodromes — Class D.
• En-route transition — Class E.
• Below the en-route structure — Class G (uncontrolled).

Operational consequences of class#

• Communication — A, B, C, D require continuous two-way communication; E and below relax this for VFR.
• Surveillance — Classes that promise IFR / VFR separation effectively require positive surveillance of VFR.
• Pilot equipage — transponder mandatory in classes that promise separation; airspace charts must declare requirements clearly.
• Workload — moving from D to C to B sharply increases controller workload per movement; the design must size sectors accordingly.

How class interacts with route design#

The route structure inside a Class A or B block is denser and tighter than the same volume in Class E. Free Route Airspace (FRA) is normally implemented in upper Class A (or upper-only Class C in some States), where ATC has full separation responsibility and the traffic is all IFR.

An airspace design is rarely a single object. It is the assembly of several design domains that interlock at defined boundaries. This file describes the five domains that any modern design has to reconcile: en-route, terminal, aerodrome control zone, free route airspace, and the flexible-use overlay.

1. En-route domain#

The en-route domain is everything from top of climb to top of descent. The design problem is to channel cruise traffic safely and efficiently across long distances while preserving sector workload.

Design levers:

• ATS route network. Geometry of routes between significant points; one-way vs. two-way; level allocations along the route.
• Navigation specification. Typically RNAV 5 / RNAV 2 / RNP 2 in continental airspace; RNP 4 / RNP 2 oceanic; RNP 10 legacy oceanic.
• Lateral and vertical separation. Set per Doc 4444; reduced spacing where surveillance and PBN allow.
• Sectorisation. Sector boundaries chosen to balance workload across positions and to avoid handoffs in turns or descents.
• Choke points. Where routes converge over short volumes — designed for capacity headroom, not for nominal load.
• Cross-FIR coordination. Letters of agreement, harmonised level allocation schemes, and ATFM regulations across boundaries.

The en-route domain hosts the FRTO (free route / direct routing) ASBU modules.

2. Terminal domain#

The terminal domain begins where en-route descent profiles intercept the TMA and ends at the runway threshold (and conversely on departure). The design problem is to deliver multiple flows safely onto a small number of runways at the rate the runways can absorb, with acceptable fuel and noise outcomes.

Design levers:

• TMA lateral and vertical limits. Sized to contain SIDs, STARs, holding, vectoring areas, and missed approaches with the buffers PANS-OPS requires (Annex 11 §2.10).
• Arrival / departure segregation. Parallel or independent SID and STAR systems where the traffic mix justifies; merging point design for multi-flow arrival.
• PBN procedures. RNAV 1 / RNP 1 / A-RNP STARs and SIDs; RNP APCH finals; RNP AR APCH for terrain-constrained or noise-sensitive approaches.
• CCO and CDO design. PANS-OPS Volume I procedures that allow unimpeded climb on departure and unrestricted descent on arrival (Annex 11 and PANS-OPS reference these as efficiency drivers).
• Sectorisation. Approach / final / departure splits sized to workload and runway throughput.
• Holding. Stack design with adequate vertical and lateral protection against the surrounding TMA volumes.
• Wake separation. Application of RECAT or pair-wise dynamic wake to maximise runway throughput.

The terminal domain hosts ASBU APTA, CDO, CCO, RSEQ, and SURF modules.

3. Aerodrome control zone (CTR)#

The CTR is the surface-to-upper-limit volume around an aerodrome. The design problem is to fuse runway operations, ground movement, and visual circuit traffic with the IFR streams arriving from and departing to the TMA.

Design levers:

• CTR class. Typically Class C or D; shape and ceiling chosen to contain the visual circuit and the early SID / late STAR segments.
• Surface routing. A-SMGCS-supported standard taxi routes, runway holding positions, and conditional clearances.
• Runway operations mode. Single-runway sequencing, mixed-mode, segregated mode, dependent / independent parallel approaches.
• VFR access. Reporting points, transit corridors, visual reference.
• Coordination with TMA approach control. Transfer points, release procedures, missed approach handling.

The CTR domain interfaces directly with Annex 14 (aerodromes) and the ASBU SURF and RATS modules.

4. Free Route Airspace (FRA)#

FRA is a design pattern for the en-route domain in which operators plan a user-preferred trajectory between defined entry and exit points without reference to a fixed published route network, optionally via intermediate waypoints.

Design principles:

• Cross-border seamless airspace. FRA is most valuable when it spans multiple FIRs — fragmenting it across borders reintroduces the route network at every boundary.
• CDM with users. Trajectory acceptability tested against ATC capacity, military activity, and regulated flows.
• Step-wise deployment. Night-only FRA, then weekend, then 24/7; partial FRA above a defined level, then full vertical extent.
• Retention of fixed structures only where needed — TMAs, military areas, choke points; the rest is direct.
• Full PBN underpinning. RNAV 5 minimum, normally RNP 2; routing via published waypoints to preserve flight plan handling.

FRA was introduced operationally by EUROCONTROL from 2008 and has been progressively deployed across European FABs. ICAO supports FRA through the PBN framework, the ASBU FRTO modules, and regional implementation guidance.

5. Flexible Use of Airspace (FUA)#

FUA is not a separate volume; it is a management overlay on the other domains. FUA replaces static civil / military segregation with time-shared use:

• Level 1 — strategic — long-term policy and structure agreed between civil and military authorities.
• Level 2 — pre-tactical — daily and weekly allocation of reservable volumes (TRA / TSA / CDR — conditional routes).
• Level 3 — tactical — real-time release of unused military airspace to civil traffic, and vice versa.

FUA is the mechanism that allows a design to keep training and operational military requirements while still offering civil users direct routing on most days. It is essential to making FRA worthwhile in airspace where military activity is non-trivial.

Domain interfaces#

The design is only as good as its interfaces:

• En-route to terminal — top-of-descent points, STAR entry fixes, and arrival level allocation must align with sector capacity and runway rate.
• Terminal to CTR — handoff levels, missed-approach containment, coordination with tower.
• FRA to fixed structure — transition between free routing and fixed routes at FRA exit points; AIP-published rules.
• FUA to all domains — FUA cells trim or grow the usable volume of the other domains depending on the day.

Failing any one interface degrades the whole design — which is why airspace design is best treated as a single integrated programme rather than as parallel domain-specific projects.

What a "design unit" is#

An airspace design is decomposed into discrete, deliverable units. The three principal units a design team specifies, certifies, and publishes are:

1. Route segment — a published ATS route or FRA segment between two significant points.
2. Terminal Control Area (TMA) — a control area established at the confluence of ATS routes near one or more major aerodromes.
3. ATC sector — an operational subdivision of a control area or TMA worked by a single controller team.

Each unit is the smallest thing that can be planned, designed, safety-assessed, AIP-published, simulated, certified, trained for, and operated as a coherent capability. A national or regional airspace design plan is the assembly of such units, plus their interfaces.

Anatomy of a route segment#

Anatomy of a TMA#

Anatomy of an ATC sector#

Specification artefacts produced for each unit#

A complete design unit is documented by:

1. Concept of operations. What the unit is for; what changes operationally for users and controllers.
2. Design dossier. Geometry, levels, classification, navigation specification, separation rules, sectorisation.
3. Safety assessment. Hazard identification, risk assessment, and mitigation per Annex 19 / State Safety Programme.
4. Environmental assessment. Noise contour analysis, fuel-burn modelling, CO2 estimate.
5. Capacity assessment. Sector throughput, runway throughput, network capacity simulation.
6. PANS-OPS package. Procedure design dossiers for any associated SID / STAR / IAP / missed approach.
7. AIP amendment. ENR / AD entries with charts.
8. Letters of agreement. With adjacent ANSPs and military authorities.
9. Training package. Controller training, pilot information (AIC), simulator scenarios.
10. Implementation date. Aligned with AIRAC cycle and regional plan milestones.

Worked examples#

Example 1 — A new RNP 2 cross-border en-route segment#

• Improvement. Direct routing between two FIRs replacing a dog-legged conventional route, saving roughly 30 NM per flight.
• Geometry. Two new significant points at the FIR boundary; RNP 2 navigation specification.
• Procedures. Doc 4444 separation minima for RNP 2 routes; AIP ENR 3.x publication.
• Enablers. Surveillance coverage, controller training, bilateral letter of agreement.
• KPIs. Track-mile efficiency (KEA), fuel burn per flight.

Example 2 — A re-designed Class C TMA with PBN STARs and CDO#

• Improvement. Replace radar-vectored downwind / base / final with closed-path RNP 1 STARs feeding RNP APCH; enable CDO from top of descent.
• Geometry. Re-sized TMA polygon to contain new STAR geometry; revised holding fixes; updated missed-approach areas.
• Procedures. PANS-OPS Vol II procedure design; PANS-ATM separation; AIP AD 2 plate replacement.
• Enablers. Fleet PBN equipage; AMAN to preserve sequence; controller training.
• KPIs. Excess fuel per arrival; arrival time variance; noise contour change.

Example 3 — A new free route airspace area above FL245#

• Improvement. Convert upper Class A from fixed network to FRA with cross-border continuity.
• Geometry. Defined entry / exit points; intermediate published waypoints; vertical envelope FL245 and above.
• Procedures. Trajectory acceptance rules; AIP ENR publication; flight plan format guidance via AIC.
• Enablers. RNP 2 fleet equipage; harmonised level scheme with neighbours; FUA Level 2/3 for military activity.
• KPIs. Direct routing percentage; KEP/KEA; fuel saved per flight.

An enabler is a supporting element without which a design unit (route segment, TMA, sector) cannot deliver its intended benefit safely and lawfully. Enablers are not the design itself; they are the preconditions a design assumes. ASBU planning makes them explicit. So should airspace design.

Enablers fall into seven categories.

1. CNS infrastructure#

Communications, navigation, and surveillance coverage that the design requires.

• Communications. VHF coverage with required redundancy; HF and satcom voice for oceanic / remote; CPDLC over VDL Mode 2 or FANS-1/A or ATN B1/B2 where used as a control channel; ground- ground voice / data interconnection between ACCs.
• Navigation. GNSS core constellation availability for the PBN specifications applied; SBAS where LPV approaches are used; GBAS at airports where GLS is used; conventional VOR / DME / ILS as retained back-up.
• Surveillance. SSR Mode S, ADS-B Out, and / or multilateration coverage matching the separation minima applied; ADS-C in oceanic / remote; primary radar where non-cooperative targets matter.

Coverage gaps directly cap the separation minima a designer can apply and therefore the route spacing and sector capacity achievable.

2. Separation standards#

The design must apply ICAO separation standards consistently:

• Doc 4444 — PANS-ATM, Chapter 5. Methods and minima — vertical, longitudinal, lateral, and combinations.
• Doc 4444 — PANS-ATM, Chapter 8. ATS surveillance services — separation minima with surveillance.
• Doc 9689 — Manual on Airspace Planning Methodology. The collision-risk methodology used to justify reduced separation in RVSM and RNP airspace.
• Doc 9613 — PBN Manual. Lateral and longitudinal route spacing for each navigation specification.

Choice of separation rule drives sector capacity, route spacing, and ultimately the throughput that the design can deliver.

3. Procedures (PANS) and SARPs#

The procedural framework anchored in ICAO PANS:

• Doc 4444 — PANS-ATM for ATS procedures.
• Doc 8168 — PANS-OPS, Volumes I and II for instrument procedure design (departures, arrivals, approaches, missed approach, holding) feeding SIDs, STARs, IAPs into the airspace structure.
• Doc 7030 — Regional Supplementary Procedures for region-specific rules (EUR, MID, ASIA/PAC, AFI, NAT, SAM, CAR).
• Annex 11 for the airspace classification and route establishment framework.
• Annex 14 where TMA / CTR design ties to aerodrome design surfaces.

4. Safety assessment#

Annex 19 (Safety Management) and Annex 11 §2.27 require that any significant change to the ATS system — including airspace re-design — be safety-assessed before implementation. Typical artefacts:

• Hazard identification workshop;
• Functional hazard analysis;
• Collision-risk modelling per Doc 9689 where reduced separation is proposed;
• Mitigation plan with monitoring KPIs;
• Sign-off in the State Safety Programme (Doc 9859 — Safety Management Manual);
• Post-implementation safety review.

5. Environmental assessment#

Modern airspace design is also an environmental product:

• Noise. Contour analysis around airports and under SID / STAR paths; constrained routings to avoid noise-sensitive areas where feasible.
• Fuel and CO2. Fuel-burn modelling for representative fleet mix; comparison against baseline.
• Local air quality. NOx / particulate analysis where relevant.
• Stakeholder engagement. Public consultation on changes that modify ground noise exposure.

ICAO's environmental framework (CAEP, the State Action Plan structure, and the ASBU CDO / CCO modules) sets the language used for these assessments.

6. Simulation and validation#

Designs are validated before AIP publication using:

• Fast-time simulation. Capacity, complexity, and conflict-rate modelling; comparison of variants.
• Real-time simulation. Controller-in-the-loop validation of sectorisation, procedures, and HMI changes.
• Live trials and shadow operations where appropriate, with safety oversight.
• Post-implementation monitoring against the KPIs declared in the safety and environmental assessments.

EUROCONTROL's NEST tool, SESAR validation methodology, and FAA TARGETS are common industry references; ICAO Doc 9426 lays down the planning methodology.

7. Regulatory, human-resource, and institutional enablers#

• Regulatory framework. State approval for PBN operations, operational authorisations, RVSM, special procedures (RNP AR); spectrum approvals.
• Human resources. Controller training, simulator validation, competency endorsements; pilot information through AIC; AIM officer training to publish to the new structure.
• Institutional. Letters of agreement with adjacent ANSPs; civil-military coordination forums; regional bodies (APANPIRG, MIDANPIRG, EANPG, GREPECAS) endorsing the design where it crosses borders.
• AIP cycle alignment. AIRAC date discipline so the new structure goes live on a single coordinated date with neighbours.

How enablers are managed in practice#

A national airspace design programme typically maintains an enablers register alongside the design dossier. Each enabler has:

• a category (CNS, separation, procedure, safety, environment, human, institutional);
• an owner (CAA, ANSP, military, airport);
• a target readiness date;
• a verification method.

A unit goes live only when all of its declared enablers are in place. Skipping an enabler — for example, declaring an RNP 1 STAR before the fleet is equipped, or commissioning a new TMA before controller training is complete — is the most common failure mode in airspace projects, and the one that ICAO Doc 9426 and Annex 19 are explicit about preventing.

The performance lens#

Airspace design is justified — and judged — against the Key Performance Areas (KPAs) of the Global ATM Operational Concept (Doc 9854) and the performance management methodology in Doc 9883 (Manual on Global Performance of the Air Navigation System). Every proposed change to the airspace structure should declare which KPAs it moves and which KPIs will evidence the move.

The chain is:

KPA  --(measured by)-->  KPI  <--(targeted by)--  Performance Objective  --(achieved by)-->  Airspace design unit

Primary KPAs for airspace design#

Of the eleven KPAs in Doc 9854, four are the daily currency of an airspace design programme: capacity, flight efficiency, environmental impact, and safety. Three more often surface as secondary objectives: predictability, flexibility, and access and equity.

Capacity#

The ability of the system to absorb traffic without degrading service. Levers: sector design, route spacing, runway configuration, FRA, level allocation, ATFM measures.

KPIs:

• Declared sector capacity (movements per hour).
• Sustained sector throughput vs. declared.
• Declared and achieved runway capacity.
• ATFM regulation rate; minutes of ATFM delay per flight.
• Network throughput at peak hour.

Flight efficiency#

How close actual or planned trajectories come to the user-preferred (usually great-circle, fuel-optimal) trajectory.

KPIs:

• KEP — flight efficiency of the last-filed flight plan vs. great circle.
• KEA — flight efficiency of the actual flown trajectory vs. great circle.
• Direct routing percentage.
• Free route airspace utilisation rate.
• Vertical efficiency (cruise altitude vs. fuel-optimum).

Environmental impact#

Fuel burn, CO2 emissions, NOx, and noise exposure attributable to the airspace structure.

KPIs:

• Fuel burn / CO2 per flight against a baseline.
• Excess fuel per arrival (CDO conformance).
• Excess fuel per departure (CCO conformance).
• Population exposure inside given noise contours.
• Track dispersion under PBN STARs / SIDs.

Safety#

The non-negotiable KPA. A design must demonstrate equivalent or better safety than the baseline before going live (Annex 19, Annex 11 §2.27, Doc 9859).

KPIs:

• Loss-of-separation events per flight hour.
• Airprox / serious incident rate per movement.
• STCA / MSAW alert rate (and false-alert rate).
• Runway-incursion severity-weighted rate (where the design touches the CTR / surface).

Secondary KPAs#

• Predictability — variance between planned and actual times (off-block, airborne, landing); ATFM slot adherence.
• Flexibility — ability of users to change route, level, or trajectory close to or during flight; FUA Level 3 utilisation.
• Access and equity — fair access to airspace for IFR / VFR / GA / military / commercial operators; military training time preserved under FUA.
• Cost-effectiveness — unit cost of ANS provision and benefit- cost ratio of the design (Doc 9082, Doc 9587).
• Interoperability — harmonisation across borders, common PBN specifications, harmonised level allocation schemes.

Performance Objectives for an airspace design programme#

Typical objectives (illustrative, consistent with ICAO and regional performance frameworks):

• PO — Increase en-route sector and network capacity. Measured by sector throughput and ATFM delay. Delivered by re-sectorisation, FRA introduction, dynamic configurations.
• PO — Reduce en-route flight inefficiency. Measured by KEP / KEA. Delivered by direct routings, FRA, optimum level access, removal of dog-legs.
• PO — Reduce fuel burn and CO2 per flight. Measured by fuel and CO2 per movement. Delivered by FRA, CDO / CCO enabling TMA design, optimum cruise levels.
• PO — Improve arrival predictability. Measured by standard deviation of actual vs. planned landing time. Delivered by AMAN / XMAN, sequencing-friendly STAR design, ACDM-coupled departures.
• PO — Reduce noise exposure under TMA flight paths. Measured by population inside published contours. Delivered by PBN STARs / SIDs avoiding sensitive areas, CDO / CCO design.
• PO — Maintain or improve safety performance. Measured by loss-of-separation rate, airprox severity, STCA alert rate. Delivered by safety assessment, monitoring, training.
• PO — Preserve access for all user classes. Measured by VFR access, military training time, GA route availability. Delivered by FUA, CDR design, transit corridors.

How performance is reported#

• Globally — ICAO ASBU implementation monitoring, GANP review cycle.
• Regionally
  • APAC: APANPIRG, Seamless ATM Plan progress reports.
  • MID: MIDANPIRG and the MID Air Navigation Strategy.
  • EUR: EUROCONTROL Performance Review Body, LSSIP cycle, NM performance dashboards.
  • NAT / CAR / SAM / AFI: respective ICAO regional offices.
• Nationally — State Action Plan (environment), State Safety Programme reports, the State's air navigation plan and post- implementation reviews.

Why performance discipline matters#

Without an explicit performance lens, airspace design slides into "build because we can": new sectors, new routes, new procedures with no measurable benefit. Tying every design unit to a KPA, a Performance Objective, and a KPI does three things:

1. Forces the team to state — before money is spent — what measurable problem the change fixes.
2. Gives the safety regulator and the economic regulator a common language for the business case (Doc 9587).
3. Provides the basis for the post-implementation review that the Annex 19 safety management framework requires.

Three timelines to keep distinct#

When discussing airspace-design dates, separate three things:

1. Annex 11 amendment timeline — when ICAO changed the SARPs that define the design space.
2. Free Route Airspace (FRA) deployment timeline — when FRA went from concept to large-scale operation, mainly in Europe.
3. PBN airspace concept timeline — when the navigation specifications underpinning modern airspace design were defined.

A national airspace plan is a fourth, local timeline; it should be expressed against milestones in the regional plan (APAC Seamless ATM Plan, EUR ATM Master Plan, MID Air Navigation Strategy).

Annex 11 amendment milestones#

Annex 11 has been amended dozens of times since 1950. The amendments that most affected airspace design as a discipline:

The current Annex 11 baseline (read with Doc 4444 and Doc 8168) is what governs new airspace design today.

Free Route Airspace deployment timeline#

FRA is the biggest single change to en-route airspace design since the move from beacon-to-beacon airways to RNAV.

Outside Europe, FRA-style direct routing has been adopted selectively (e.g. in oceanic and remote airspace via the User Preferred Routes concept, and in low-density continental upper airspace), but Europe remains the largest contiguous deployment.

PBN airspace concept timeline#

The PBN concept — and therefore modern PBN airspace design — has its own timeline in Doc 9613.

The Doc 9613 content, together with Doc 9426 (ATS Planning Manual) and Doc 9689 (Airspace Planning Methodology), is the standing reference library for an airspace design programme.

ASBU alignment for airspace design#

The ASBU framework (see topics_detailed/asbu/) gives airspace design a global delivery cadence:

Block 0 ........ from 2013 — PBN approaches everywhere; initial FRA in low-density airspace; FUA basics.
Block 1 ........ from 2019 — full FRA cross-border; XMAN; A-RNP; richer terminal PBN.
Block 2 ........ from 2025 — initial trajectory-based operations interacting with airspace design.
Block 3 ........ from 2031 — fully performance-based, network-centric, trajectory-based airspace.

A given State's airspace design plan picks the modules within these windows that match its traffic, fleet, terrain, and investment cycle.

How to read a date in an airspace-design document#

When an airspace document uses a date, identify which timeline it belongs to:

• "Annex 11 Amendment 50, applicable date 2018" — SARP change.
• "FRA target date 1 January 2022" — regional regulatory milestone (here, EU).
• "Doc 9613 5th edition, 2023" — PBN framework publication date.
• "TMA re-design effective AIRAC 2024-09-05" — national publication.
• "ASBU Block 1 from 2019" — global notional availability of the module set.

Mixing these up leads to false claims about a State being "behind" or "ahead". The only meaningful measure is the State's own airspace design plan against its own milestones, expressed within the regional plan.

Primary ICAO SARPs and PANS#

• Annex 11 (Air Traffic Services), Chapter 1, §1.1 — Definitions of ATS route ("a specified route designed for channelling the flow of traffic as necessary for the provision of air traffic services"), control area, controlled airspace, control zone, and terminal control area (TMA at the confluence of ATS routes near major aerodromes).
• Annex 11 (Air Traffic Services), Chapter 2, §2.6 — Classification of airspaces (Classes A–G); services and separation per class; less restrictive class applies at common adjoining levels.
• Annex 11 (Air Traffic Services), Chapter 2, §2.7 — Performance- based navigation operations; States prescribe navigation specifications; reference to Doc 9613.
• Annex 11 (Air Traffic Services), Chapter 2, §2.10 — Establishment of control areas, terminal control areas, and control zones.
• Annex 11 (Air Traffic Services), Chapter 2, §2.13 — Establishment and identification of ATS routes (protected airspace, safe spacing, designators per Appendix 1; guidance in Doc 9426).
• Annex 11 (Air Traffic Services), Chapter 2, §2.14 — Establishment of change-over points on VOR-defined segments (segments of 110 km / 60 NM or more).
• Annex 11 (Air Traffic Services), Chapter 2, §2.15 — Significant points used to define ATS routes and to support position reporting.
• Annex 11 (Air Traffic Services), Chapter 2, §2.21 — Establishment of minimum flight altitudes.
• Annex 11 (Air Traffic Services), Chapter 2, §2.27 — Safety management of significant changes to the ATS system (read with Annex 19).
• Annex 11 (Air Traffic Services), Appendix 1 — Principles for the identification of navigation specifications and ATS routes other than SIDs and STARs.
• Annex 11 (Air Traffic Services), Attachment A — Material related to VOR-defined ATS routes.
• Annex 19 (Safety Management) — State Safety Programme and Safety Management System requirements that apply to airspace re-design.

ICAO PANS#

• Doc 4444 — PANS-ATM, Chapter 3 — ATS system capacity and air traffic flow management.
• Doc 4444 — PANS-ATM, Chapter 5 — Separation methods and minima (operational counterpart underpinning route spacing and sectorisation).
• Doc 4444 — PANS-ATM, Chapter 8 — ATS surveillance services.
• Doc 8168 — PANS-OPS, Volume I, Part I, §2 — Terminal area fixes and obstacle clearance for arrival / departure procedures feeding TMA design.
• Doc 8168 — PANS-OPS, Volume I, Part III — Departure procedure design (SIDs: straight, turning, omnidirectional; environmental and CCO considerations).
• Doc 8168 — PANS-OPS, Volume II — Construction of visual and instrument flight procedures (PBN approach and arrival procedure design feeding the airspace structure).
• Doc 7030 — Regional Supplementary Procedures — Region-specific procedures (EUR, MID, ASIA/PAC, AFI, NAT, SAM, CAR).

ICAO manuals and guidance#

• Doc 9426 — Air Traffic Services Planning Manual — Primary guidance on ATS route establishment, sectorisation, capacity assessment, and airspace organisation; explicitly referenced by Annex 11 §2.13.
• Doc 9613 — Performance-Based Navigation (PBN) Manual, 5th edition (2023) — Navigation specifications (RNAV 5 / 2 / 1, RNP 4 / 2 / 1, A-RNP, RNP APCH, RNP AR APCH) used for en-route, terminal, and approach route design including FRA.
• Doc 9689 — Manual on Airspace Planning Methodology for the Determination of Separation Minima — Collision-risk methodology used to justify reduced separation in RVSM and PBN airspace.
• Doc 9854 — Global Air Traffic Management Operational Concept — Source of the eleven Key Performance Areas (KPAs) used to justify airspace design changes.
• Doc 9883 — Manual on Global Performance of the Air Navigation System — Performance management methodology (KPAs, KPIs, performance objectives).
• Doc 9750 — Global Air Navigation Plan (GANP) — The strategic / conceptual / technical layering, with ASBU FRTO, APTA, CDO, CCO, and FUA modules driving airspace design content.
• Doc 9859 — Safety Management Manual — Implementation guidance for the safety assessment of airspace changes.
• Doc 9082 — ICAO's Policies on Charges for Airports and Air Navigation Services — Cost-recovery framework for ATM modernisation including airspace redesign.

Authoritative external sources#

• EUROCONTROL Free Route Airspace concept and FRA Design Guidelines — https://www.eurocontrol.int/concept/free-route-airspace
• EUROCONTROL ERNIP Part 1 — European Route Network Improvement Plan (Airspace Design Methodology) — https://www.eurocontrol.int/publication/european-route-network-improvement-plan-ernip-part-1
• EUROCONTROL Network Manager (NM) — https://www.eurocontrol.int/network-manager
• EUROCONTROL Performance Review Body — https://www.eurocontrol.int/prc
• SESAR Joint Undertaking — European ATM Master Plan — https://www.atmmasterplan.eu/
• FAA Order JO 7400 series — Airspace Designations and Reporting Points; Procedures for Handling Airspace Matters — primary FAA airspace handbook reference (authoritative source — not in local library).
• FAA Aeronautical Information Manual (AIM) — https://www.faa.gov/air_traffic/publications/
• ICAO PBN Portal (industry mirror) — https://www.pbnportal.eu/
• SKYbrary — Free Route Airspace — https://skybrary.aero/articles/free-route-airspace-fra
• SKYbrary — Performance-Based Navigation (PBN) — https://skybrary.aero/articles/performance-based-navigation-pbn
• SKYbrary — Flexible Use of Airspace — https://skybrary.aero/articles/flexible-use-airspace-fua
• ICAO GANP Portal — https://ganpportal.icao.int/
• APAC Seamless ATM Plan (ICAO Asia/Pacific Regional Office) — https://www.icao.int/APAC/Pages/edocs.aspx
• MID Air Navigation Strategy (ICAO MID Regional Office) — https://www.icao.int/MID/Pages/default.aspx

Notes on coverage#

The Annex 11, Doc 4444, Doc 8168, Doc 9426, and Doc 9613 references above are the primary authoritative basis. Doc 9689 is essential for any design that proposes reduced separation. EUROCONTROL FRA / ERNIP and FAA Order JO 7400 are pulled in as regional realisations and are flagged where the source is not in the local ICAO library mirror.