Detailed working notes on the ICAO Air Navigation Plan (ANP) framework — the Global Air Navigation Plan (GANP, Doc 9750) plus the family of electronic Regional Air Navigation Plans (eANPs) maintained by the Planning and Implementation Regional Groups. This folder expands the summary in topics/air_navigation_plan.md into per-aspect files so each can be read on its own.

Files in this folder#

• overview.md — what an ANP is, the global vs. regional structure, and how the GANP and the eANPs fit together.
• components.md — Volume I (basic ANP / general planning aspects) vs. Volume II (FASID), Volume III (dynamic State parts), regional supplementary procedures (Doc 7030).
• blocks.md — adapted from the ASBU "blocks" file: the seven ICAO ANP regions (NAM, EUR, AFI, MID, APAC, CAR, SAM) and how each region's ANP is structured.
• threads.md — adapted from the ASBU "threads" file: the subject areas that recur as FASID parts in every eANP (ATS, MET, AIS/AIM, COM, NAV, SUR, SAR, AOP, ATFM, search-and-rescue regions, SSR code allocation).
• modules.md — anatomy of an ANP table or facility entry: what one row in a FASID table actually carries, and how it ties back to a State and to a SARP.
• enablers.md — the institutional machinery: ICAO Regional Offices, Planning and Implementation Regional Groups (PIRGs), Regional Aviation Safety Groups (RASGs), Regional Air Navigation (RAN) meetings, and the amendment process for Volumes I, II, and III.
• performance_objectives.md — KPAs in the ANP context, regional performance frameworks, and how regional priorities feed back into the GANP.
• timeline.md — ANP evolution from paper-era regional plans (Doc 7754, Doc 8733, etc.) through the transition to electronic ANPs (eANPs) and the Volume III dynamic-maintenance regime.
• references.md — Doc 9750 (GANP), Doc 7030 (regional Supplementary Procedures), and the seven regional ANP documents (Doc 7474, Doc 7754, Doc 8733, Doc 9634/9635, Doc 9673, Doc 9708, plus NAM ANP).

Reading order#

Start with overview.md, then components.md to understand Volume I / FASID / Volume III. Read blocks.md for the regional geography and threads.md for the subject-area structure that recurs in every region. Drill into modules.md for what a FASID row carries in practice, then enablers.md for the governance machinery and performance_objectives.md for how the GANP performance lens lands in regional priorities. Use timeline.md for date context and references.md for citations.

Source basis#

Content is grounded in:

• ICAO Doc 9750 — Global Air Navigation Plan (GANP), current edition.
• ICAO Doc 9161 — Manual on Air Navigation Services Economics (definitional anchor for "Regional ANP").
• ICAO Doc 7030 — Regional Supplementary Procedures.
• ICAO Doc 9854 — Global Air Traffic Management Operational Concept.
• ICAO Doc 8126 — Aeronautical Information Services Manual.
• The seven regional ANP documents:
  • Doc 7474 — AFI Basic ANP and FASID.
  • Doc 7754 — EUR ANP, Volumes I–III.
  • Doc 8733 — CAR/SAM ANP, Volume II (FASID).
  • Doc 9634 / Doc 9635 — NAT Basic ANP and FASID.
  • Doc 9673 — APAC Basic ANP and FASID.
  • Doc 9708 — MID ANP, Volumes I–III.
  • NAM regional planning material (NAM is administered jointly between ICAO NACC and the FAA / NAV CANADA national plans; treated as a fallback citation where no single Doc number applies).
• ICAO Regional Office eANP portals: APAC, EUR/NAT, MID, ESAF/WACAF (AFI), NACC (CAR/NAM), SAM.
• GANP Portal: https://ganpportal.icao.int/

What an ANP is#

An Air Navigation Plan (ANP) is the ICAO instrument that translates Standards and Recommended Practices (Annexes) and procedures (PANS) into specific facilities, services, and procedures required for international air navigation in a defined geography, on a defined timeline. It answers the question that SARPs alone cannot: "Where must which facility or service exist, who provides it, and by when?"

Doc 9161 (Manual on Air Navigation Services Economics) defines a Regional ANP as "Air navigation plans that set forth in detail the facilities, services and procedures required for international air navigation within a specified area." Doc 9161 further records that facilities or services provided for in an ICAO regional ANP — or recommended by a regional air navigation meeting and approved by the Council — are "considered to be necessary for safety and efficiency" and thus eligible for cost recovery through air navigation charges.

That last point matters: ANP listing is the bridge from "ICAO encourages this" to "this State may charge airspace users for it."

The global vs. regional structure#

ICAO maintains the ANP framework at two operational tiers, plus a national tier derived from them:

1. Global tier — the Global Air Navigation Plan (GANP, Doc 9750). The strategic plan for the global air navigation system on a 15-year rolling horizon. Establishes vision, KPAs, the Conceptual Roadmap, and the technical-layer frameworks (Basic Building Blocks and Aviation System Block Upgrades).
2. Regional tier — the seven regional eANPs. One electronic ANP per ICAO planning region: NAM, EUR, AFI, MID, APAC, CAR, SAM (with NAT and NACC as variants). Each eANP is a three-volume document set.
3. National tier — the National Air Navigation Plan (NANP). Each State derives its NANP from the GANP and the relevant eANP(s) and uses it to drive procurement, regulation, training, and budgeting.

PANS-IM (Doc 10199) frames the transition toward an automated, digitalised, interconnected system "as described in the GANP (Doc 9750)." National programmes such as US NextGen and European SESAR are aligned to the GANP and to Doc 9854 (the Global ATM Operational Concept).

Relationship to the GANP#

The GANP and the regional ANPs are not parallel documents — they are deliberately layered.

• The GANP provides the strategic layer (vision and KPAs), the technical layer (BBB + ASBU), and a regional layer that acknowledges and tasks the PIRGs.
• The eANPs are the regional realisation: they take BBB and ASBU regional priorities from the GANP and turn them into specific FASID tables — which aerodromes carry which navaids; which ATS routes exist; which FIR is responsible for each block of airspace; which States operate which SSR code blocks; which ATFM arrangements apply.
• Doc 7030 (Regional Supplementary Procedures) sits alongside the eANPs as the procedural counterpart: where the FASID specifies a facility or organisational arrangement, Doc 7030 specifies the procedure to use. Doc 7030 repeatedly cites the FASIDs by name (e.g. Doc 7754 Part IV Attachment H for EUR SSR codes, Doc 8733 Part V Appendix B for CAR/SAM SSR codes).

What planners use the ANP set for#

For a State or ANSP, the ANP set answers four practical questions:

1. What baseline must I provide? The eANP and the BBB layer of the GANP together define the floor of facilities and services.
2. What upgrades am I expected to plan for next? The ASBU layer of the GANP and the regional priorities recorded in eANP Volume I give the upgrade ladder.
3. Where, exactly? FASID tables (eANP Volume II) and Volume III State parts identify the specific aerodromes, FIRs, routes, and facilities.
4. Cost-recoverable vs. discretionary? Doc 9161's rule — listing in the regional ANP is the test for cost-recovery eligibility — turns the ANP from advisory text into a financial instrument.

Why "Air Navigation Plan"#

The word "plan" is doing real work. An ANP is not a snapshot inventory and not a wishlist. It is:

• Forward-looking — Volume I sets multi-year regional priorities; the GANP runs on a 15-year rolling horizon.
• Binding for facilities listed — once a facility or service is in FASID, the State has a documented obligation to provide it (subject to the amendment process for changes).
• Coordinated — every entry has been reviewed by the PIRG and approved by the ICAO Council, so neighbours know what to expect.
• Maintained — Volume III is updated dynamically; Volumes I and II are amended on the PIRG cycle.

Relationship to other initiatives in this repo#

The ANP framework is the regional/national execution layer for most of the global initiatives covered elsewhere in this workspace:

• GANP, BBB, ASBU — global strategy and technical framework that the eANPs realise regionally.
• APAC Seamless ATM Plan — APAC-specific regional realisation, endorsed by APANPIRG and reflected in Doc 9673.
• PBN, ADS-B, CPDLC — listed in FASID NAV/COM/SUR tables as required facilities per FIR or route.
• SWIM, FF-ICE, Digital AIM, AMET — increasingly listed in FASID AIS/COM tables as regional information services.
• ATFM, A-CDM, NOPS — reflected in FASID ATFM and ATS sections, and in Doc 7030 supplementary procedures.

An ANP is not a single artefact. It is a structured set of interlocking components — one global plan, seven regional plans each in three volumes, plus a procedural counterpart — that together describe what facility or service must exist, where, who provides it, and how it will be procedurally used. The components are:

1. The Global Air Navigation Plan (Doc 9750)#

The umbrella strategic document. Current architecture (7th-edition family) is a multi-layer model:

• Global strategic layer. Vision, KPAs (safety, capacity, efficiency, environment, access and equity, cost-effectiveness), and a Conceptual Roadmap covering a 15-year rolling horizon.
• Global technical layer. The Basic Building Blocks (BBB) — the baseline floor — and the Aviation System Block Upgrades (ASBU) — the upgrade ladder. See topics_detailed/asbu/ for ASBU detail.
• Regional layer. Regional priorities and performance ambitions, managed by the PIRGs.
• National layer. Each State's National Air Navigation Plan (NANP), derived from the GANP and the relevant eANP.

The GANP module catalogue and performance objectives are maintained dynamically on the GANP Portal (https://ganpportal.icao.int/).

2. Volume I — Basic ANP / General Planning Aspects#

The regional strategic volume. Stable text, amended infrequently. Volume I typically contains:

• Region-wide planning principles and assumptions (traffic forecast, airspace organisation, performance ambitions).
• Regional implementation priorities for BBBs and ASBU threads.
• Region-wide policies on coordination, safety oversight, and States' cooperative arrangements.
• High-level descriptions of major airspace structures (e.g. ATS route network philosophy, FIR boundaries, oceanic airspace schemes).
• Performance objectives endorsed by the PIRG.

Volume I is the document that planners read first to understand a region's air-navigation philosophy.

3. Volume II — FASID (Facilities and Services Implementation Document)#

The operational core of the eANP. Tables and charts specify the required facilities and services per FIR, aerodrome, ATS route, or service area. FASID parts typically include:

• AOP — Aerodrome operations and capacity planning.
• ATS — ATS route network, FIR delineation, airspace classifications.
• MET — Meteorological watch offices, aerodrome MET stations, WAFC / volcanic-ash advisory arrangements.
• AIS / AIM — AIS units, AIP publication arrangements, NOTAM offices, regional AIS database arrangements.
• COM — Aeronautical telecommunication services (AFS, AMHS, AFTN routing diagrams, voice circuits, data link).
• NAV — Required navigation aids per route segment / FIR; PBN coverage; conventional aid retention.
• SUR — Required surveillance per FIR and airspace volume (radar, ADS-B, Mode S, ADS-C, MLAT, space-based ADS-B).
• SAR — Search and Rescue Regions (SRRs), Rescue Coordination Centre boundaries, cross-border SAR agreements.
• ATFM — Regional ATFM arrangements, flow management entities, exemption schemes (e.g. EUR FASID Part V.III on ASTER and CFMU slot-allocation exemptions).
• SSR code allocation — regional code distribution plans (e.g. Doc 7754 Part IV Attachment H for EUR; Doc 8733 Part V Appendix B for CAR/SAM).

FASID is the primary "binding" volume — entries here are the basis on which neighbouring States plan and on which Doc 9161 cost-recovery eligibility is judged.

4. Volume III — Dynamic State Parts#

Each State's specific entries: aerodrome inventory, ATS route descriptions, frequency assignments, navaid identifiers, surveillance service areas, AIS publication particulars. Volume III is maintained dynamically online by the Regional Office and amended through Regional Office procedures rather than via a Council amendment cycle. This is what makes the ANP "electronic" — Volume III changes weekly to monthly, without re-issuing the document.

5. Doc 7030 — Regional Supplementary Procedures#

The procedural counterpart to the eANPs. Where FASID specifies a facility or arrangement, Doc 7030 specifies the procedure that goes with it. Examples:

• SSR code assignment in CAR/SAM "in accordance with Doc 8733, Part V, Appendix B."
• EUR SSR codes per Doc 7754, Part IV, Attachment H.
• EUR ATFM exemption procedures referencing EUR FASID Part V.III.

Doc 7030 is divided by region (EUR, MID, ASIA/PAC, AFI, NAT, SAM, CAR) and is updated in lockstep with FASID amendments.

6. The seven Regional ANP documents#

7. Doc 9161 — Cost-recovery anchor#

Doc 9161 (Manual on Air Navigation Services Economics) is not part of the ANP set itself, but it is the policy bridge that turns ANP listing into financial obligation: facilities and services in the eANP are "considered to be necessary for safety and efficiency" and are thus recoverable through user charges.

8. Doc 9854 / Doc 9883 — performance lens#

Doc 9854 (Global ATM Operational Concept) and Doc 9883 (Global Performance Manual) supply the KPA / KPI vocabulary that the GANP and the regional Volume I performance sections use.

9. The matrix view#

Putting the components together produces the canonical ANP planning matrix:

                Strategic           Technical          Implementation
GANP            Vision, KPAs,       BBB + ASBU         (Conceptual)
                Conceptual Roadmap  threads
eANP Vol I      Regional priorities Regional BBB/ASBU  (region-wide
                                    priorities          principles)
eANP Vol II     -                   FASID tables       Per FIR / aerodrome
(FASID)                             (binding)
eANP Vol III    -                   -                  Per State (dynamic)
Doc 7030        -                   Regional SUPPs     Per region (procedural)
NANP            National strategy   National roadmap   National projects

A planner navigates this matrix from any axis: a single FASID NAV table row ties down to a SARP in Annex 10, up to an ASBU module in the GANP, sideways to a Doc 7030 procedure, and through Doc 9161 to a charging basis.

In the ASBU framework, "Blocks" are time windows. In the ANP framework, the analogous structural axis is geography: the seven ICAO planning regions, each with its own eANP, its own PIRG, and its own Regional Office. This file describes those regions and the structure of each region's ANP.

What an ICAO Region is#

An ICAO planning region is a contiguous block of FIRs (with oceanic extensions) coordinated by a single Planning and Implementation Regional Group under the oversight of one or more ICAO Regional Offices. The seven regions are:

Each region's ANP is a parallel three-volume structure (Volume I, FASID Volume II, dynamic Volume III), with regional flavour reflecting the traffic, geography, and political arrangements of the region.

NAM — North American Region#

Geography. Continental United States, Canada, parts of Mexico, adjacent oceanic interfaces with the NAT and CAR regions.

ANP document. NAM regional planning material is administered through the NACC office and aligned with the NAT plan; there is no single NAM-only Doc number on the model of Doc 7754. National plans dominate (US National Airspace System plans, NAV CANADA plans).

Distinctive features. Highest movement densities globally; mature PBN, ADS-B, and data link deployment; close coupling to NAT for North Atlantic Tracks (OTS) interface; FAA NextGen as the dominant national modernisation programme.

EUR — European Region#

Geography. ECAC States plus extensions; from Iceland to Türkiye, including the Baltic and the western Mediterranean.

ANP document. Doc 7754 — EUR ANP, Volumes I, II, III.

Distinctive features. The most densely contested airspace in the world; SES (Single European Sky) and SESAR Deployment as parallel European Union frameworks alongside the ICAO eANP; EUROCONTROL Network Manager as central flow entity; LSSIP cycle as annual reporting tool; EUR FASID Part V.III defines ASTER ATFM service States and CFMU slot exemptions; Part IV Attachment H is the EUR SSR Code Allocation Plan.

NAT — North Atlantic Region#

Geography. North Atlantic oceanic airspace between NAM and EUR/AFI; includes the Reykjavik, Bodø, Shanwick, Gander, New York, and Santa Maria oceanic FIRs.

ANP document. Doc 9634 (Basic ANP) and Doc 9635 (FASID).

Distinctive features. The NAT High Level Airspace (HLA) regime, PBCS (Performance-Based Communication and Surveillance) requirements, data link mandate (FANS-1/A or ATN B1), space-based ADS-B coverage, Organised Track System (OTS), reduced lateral and longitudinal minima.

AFI — African-Indian Ocean Region#

Geography. Continental Africa (less the Mediterranean rim), Indian Ocean island States, oceanic interfaces with APAC at the eastern edge.

ANP document. Doc 7474 — AFI Basic ANP and FASID.

Distinctive features. Wide variation in BBB completeness across States; major implementation focus on PBN, ADS-B (including space-based for oceanic and remote continental), AFI Plan for safety and capacity; AFISNET / NAFISAT regional VSAT networks for AFTN/AMHS.

MID — Middle East Region#

Geography. Arabian Peninsula, Levant, Iran, Iraq, the Mediterranean eastern rim where it interfaces with EUR.

ANP document. Doc 9708 — MID ANP, Volumes I, II, III.

Distinctive features. Very high transit-flow growth; MID Air Navigation Strategy as the regional implementation roadmap; MIDANPIRG priority on PBN, ATFM (MID RVSM completed earlier), and SWIM / Digital AIM transition; geopolitically sensitive FIR boundaries.

APAC — Asia/Pacific Region#

Geography. From Pakistan and Central Asia eastward through East, Southeast, and Australasian airspace, plus Pacific oceanic FIRs.

ANP document. Doc 9673 — APAC Basic ANP and FASID.

Distinctive features. Largest region by area and traffic growth; APAC Seamless ATM Plan as the regional ASBU realisation; APANPIRG as the senior PIRG with a heavy committee structure (ATM SG, AIM SG, CNS SG, MET SG, SAR TF, etc.); diverse maturity levels across States; extensive oceanic airspace under ADS-C / CPDLC / space-based ADS-B.

Pakistan sits in the western edge of APAC; PCAA's ANP work is coordinated through APANPIRG and the Bangkok Regional Office.

CAR — Caribbean Region#

Geography. Caribbean basin States and territories; oceanic interfaces with NAM, NAT, and SAM.

ANP document. Doc 8733 (shared with SAM) — CAR/SAM ANP, Volume II (FASID).

Distinctive features. Many small-State ANSPs; heavy tourist-traffic peak loads; close coordination with FAA Caribbean operations; GREPECAS as the joint CAR/SAM PIRG; Doc 8733 Part V Appendix B is the SSR Code Allocation Plan invoked by Doc 7030.

SAM — South American Region#

Geography. South America from Colombia and Venezuela southward, including the South Atlantic oceanic interface with AFI.

ANP document. Doc 8733 (shared with CAR) — CAR/SAM FASID; SAM-specific portions in Volume III State parts.

Distinctive features. Long oceanic and remote continental FIRs; focus on PBN coverage in the Andes, ADS-B and space-based ADS-B for oceanic; SAM Implementation Project (SAM-IP) as the regional implementation vehicle.

Region dependency principle#

ANP entries are regional but FIRs frequently sit on a region boundary (e.g. Karachi FIR straddles APAC / MID interface; Casablanca FIR sits on AFI / EUR / NAT interface). For these boundary FIRs, the FASID entries in two adjacent eANPs must agree on:

• The boundary itself (ATS route handover points, FIR limits).
• The transfer-of-control procedure (Doc 4444 + Doc 7030).
• SSR code transitions (Doc 7754 Att H ↔ Doc 9673 ↔ Doc 8733 App B).
• Letter-of-Agreement obligations between the adjacent ANSPs.

This is why Volume I priorities are set per region, but Volume II FASID entries on boundaries are co-developed by the two PIRGs.

Pakistan / APAC application#

A typical national ANP exercise for the PCAA / Pakistan CAA proceeds:

1. Read GANP Doc 9750 Part I + II for global priorities (BBB + ASBU).
2. Read Doc 9673 Volume I for APAC regional priorities.
3. Audit Doc 9673 FASID Volume II entries for Pakistan FIRs (Karachi, Lahore where applicable) — AOP, ATS routes, COM, NAV, SUR, SAR.
4. Maintain Volume III State parts dynamically through the APAC Regional Office.
5. Cross-check Doc 7030 ASIA/PAC supplementary procedures for any regional rules that change Doc 4444 application in the region.
6. Coordinate with MID (MIDANPIRG / Doc 9708) for the western boundary handovers.

In the ASBU framework, "Threads" are feature areas (APTA, SWIM, FICE, TBO, etc.). In the ANP framework, the analogous structural axis is the set of subject areas that recur as parts of every regional FASID: ATS, MET, AIS/AIM, COM, NAV, SUR, SAR, AOP, ATFM, and the cross-cutting SSR code-allocation tables. This file walks through each.

The catalogue below reflects the FASID part structure used in the seven regional eANPs (Doc 7474, 7754, 8733, 9634/35, 9673, 9708, plus NAM/NACC material). Naming and numbering vary by region; the subject matter does not.

Operational subject areas#

ATS — Air Traffic Services#

The largest single FASID part in most regions. Carries:

• FIR boundaries and lateral / vertical limits.
• ATS route network: route designators, segments, vertical applicability, navigation specification (RNAV / RNP).
• Airspace classification per FIR / volume.
• Transfer-of-control points and coordination requirements with neighbouring FIRs.
• ATS unit identification (ACC, APP, TWR, FIC).
• Cross-references to Annex 11 (ATS) and Doc 4444 (PANS-ATM).

In Pakistan / APAC terms this is the part of Doc 9673 that lists Karachi FIR, Lahore FIR (where applicable), and the published ATS routes.

AOP — Aerodrome Operations#

Aerodrome inventory and capacity planning. Carries:

• International aerodromes (regular use, alternate, off-load).
• Required runway, taxiway, and apron capacity.
• A-SMGCS levels expected per aerodrome category.
• A-CDM applicability at major hubs.
• Cross-references to Annex 14 (Aerodromes).

ATFM — Air Traffic Flow Management#

Regional flow-management arrangements. Examples:

• EUR FASID Part V.III: ASTER ATFM service States, CFMU slot allocation exemptions.
• APAC Air Traffic Flow Management Steering Group (ATFM/SG) arrangements.
• MID regional ATFM cell and the cross-FIR coordination protocols.

Cross-references to Doc 4444 (PANS-ATM) Chapter 3 ATFM provisions and Doc 7030 regional supplements.

SAR — Search and Rescue#

Search and Rescue Region (SRR) delineation, Rescue Coordination Centre (RCC) responsibilities, cross-border SAR agreements, communication arrangements (Cospas-Sarsat, SARSAT MEOSAR), and the maritime / land / aeronautical SAR interface.

Cross-references to Annex 12 (Search and Rescue), Doc 9731 (IAMSAR Manual).

Information subject areas#

MET — Meteorological Service for Air Navigation#

Operational MET arrangements per FIR and per aerodrome:

• Meteorological Watch Office (MWO) responsibilities.
• Aerodrome MET stations and observation requirements.
• WAFC (World Area Forecast Centre) products and user States.
• VAAC (Volcanic Ash Advisory Centre) coverage.
• Tropical-cyclone advisory arrangements.
• IWXXM / OPMET data exchange arrangements.

Cross-references to Annex 3 (MET), Doc 10157 (PANS-MET).

AIS / AIM — Aeronautical Information Services / Management#

The information backbone for the eANP itself. Carries:

• AIS / AIM units and AIP publication arrangements per State.
• NOTAM offices and the regional NOTAM exchange (e.g. EAD in Europe).
• Regional AIS database and digital AIM products.
• AIRAC alignment.
• Transition to Digital AIM, AIXM 5 data sets, and SWIM-based exchange — increasingly listed as a regional priority in Volume I.

Cross-references to Annex 15 (AIS/AIM), Doc 8126 (AIS Manual), Doc 10066 (PANS-AIM). Doc 8126 explicitly ties Digital AIM and SWIM to GANP/ASBU objectives.

Technology / CNS subject areas#

COM — Aeronautical Telecommunications#

The communications layer: ground-ground (AFTN, AMHS, AFS routing diagrams, voice circuits) and air-ground (VHF, HF, satcom voice; CPDLC over VDL Mode 2 or FANS-1/A; future ATN B2 and IPS).

Carries:

• Regional AFTN / AMHS routing diagrams.
• VHF (and 8.33 kHz spacing in EUR) frequency allocations.
• HF family arrangements (CWP — common working procedures).
• Data link applicability (continental CPDLC, oceanic FANS-1/A, ATN B1 in EUR core).

Cross-references to Annex 10 (CNS), Doc 4444 data link procedures, Doc 7030 regional procedures.

NAV — Navigation Systems#

Navigation aid inventory and PBN deployment per FIR / route:

• Conventional aids retained (VOR, DME, NDB, ILS) — and their planned phase-down where redundancy allows.
• GNSS use as primary means, with augmentation arrangements (SBAS: WAAS, EGNOS, MSAS, GAGAN, SDCM; GBAS at airports).
• PBN navigation specifications per route / approach.
• Multi-constellation / multi-frequency rollout plans.

Cross-references to Annex 10 Vol I (radio navigation aids), Doc 9613 (PBN Manual).

SUR — Surveillance#

Surveillance coverage requirements per FIR / airspace volume:

• Primary / Secondary radar networks.
• Mode S Enhanced Surveillance.
• ADS-B Out coverage and equipage mandates.
• ADS-C contracts in oceanic and remote.
• Multilateration (WAM en route, MLAT at airports).
• Space-based ADS-B coverage in oceanic and remote regions.

Cross-references to Annex 10 Vol IV (surveillance), Doc 4444 surveillance procedures.

Cross-cutting subject area#

SSR Code Allocation#

A region-wide table that distributes SSR code blocks across States so that codes do not collide across FIR boundaries. Examples of FASID authority:

• EUR: Doc 7754 Part IV Attachment H — SSR code distribution principles for the EUR Region (invoked by Doc 7030 § 5.1.2.1).
• CAR/SAM: Doc 8733 Part V Appendix B — SSR Code Allocation Plan for the CAR/SAM Regions (invoked by Doc 7030 § 5.1.3.1).
• APAC, MID, AFI, NAT: equivalent code-allocation appendices in Doc 9673, Doc 9708, Doc 7474, and Doc 9634/9635 respectively.

These tables are formally part of FASID but are typically managed by a dedicated SSR Code Management Group under each PIRG.

Cross-thread dependencies (typical)#

• NAV / SUR drive ATS route-network design — RNP-capable routes cannot be published without the NAV environment to support them, and surveillance separation minima follow from SUR coverage.
• COM is a prerequisite for ATFM (network-manager messaging) and for AIS/AIM (AMHS, AIXM exchange).
• AOP and ATS must agree on aerodrome-FIR boundaries.
• MET feeds ATS (SIGMET dissemination) and ATFM (regulation triggers from convective activity, volcanic ash, tropical cyclones).
• SAR depends on COM for distress-alert distribution.

This is why FASID parts cannot be drafted independently — the PIRG working groups (ATM SG, AIM SG, CNS SG, MET SG, SAR TF) cross-coordinate amendment proposals before they reach the PIRG plenary.

What a FASID entry is#

In the ASBU framework the smallest planning unit is a Module. In the ANP framework the smallest planning unit is a FASID entry — one row of a Volume II Facilities and Services Implementation Document table, or one cell of one of its appendices. A FASID entry is operational — it defines a specific facility, service, or service area that a State or group of States is committed to provide.

A FASID entry sits at the intersection of:

• a Region (one of NAM, EUR, NAT, AFI, MID, APAC, CAR, SAM);
• a Subject area (ATS, MET, AIS/AIM, COM, NAV, SUR, SAR, AOP, ATFM, SSR code allocation);
• a Geographic scope (a FIR, a route segment, an aerodrome, an oceanic area, a service region).

Identifier convention is by document part / table / row rather than a single string code, e.g.:

Doc 7754 (EUR ANP), Vol II FASID, Part IV, Attachment H, Row 12
Doc 8733 (CAR/SAM FASID), Part V, Appendix B, CAP entry for FIR XXXX
Doc 9673 (APAC FASID), Vol II, ATS Routes Table, Route ID Lxxx

Anatomy of a FASID entry#

The structured information a FASID entry typically carries is:

1. Identifier and scope#

The unambiguous reference to the entry: document, volume, part, table, row number, and the geographic scope (FIR, route, aerodrome, service area).

2. Facility or service description#

A plain-language statement of what the entry obliges. For an ATS route row this is the route designator, route geometry (waypoints), vertical applicability, navigation specification (RNAV 5, RNP 2, RNP 1, etc.), and direction. For a NAV row it is the navaid identifier, type, service volume, and operational status.

3. Responsible State and provider#

The entry names the State (and, where relevant, the ANSP or operator) responsible for providing the facility or service. Boundary entries identify both States.

4. Performance / specification element#

The operational performance the entry implies. For a SUR row: required coverage altitude floor, surveillance type (PSR, SSR Mode S, ADS-B, WAM, ADS-C, space-based ADS-B), update rate. For a COM row: voice or data link service, frequency, channel spacing.

5. Procedural element#

The procedural rules that govern use of the facility — usually by cross-reference to PANS:

• Doc 4444 (PANS-ATM) for ATS / ATFM.
• Doc 8168 (PANS-OPS) for procedure design (PBN approaches, CDOs, CCOs).
• Doc 10066 (PANS-AIM) for AIS/AIM data quality and lifecycle.
• Doc 10157 (PANS-MET) for MET service procedures.
• Doc 7030 (Regional Supplementary Procedures) for the regional delta on top of PANS — Doc 7030 explicitly cites FASID parts (e.g. Doc 7754 Part IV Attachment H, Doc 8733 Part V Appendix B).

6. Standards basis (SARPs)#

The Annex provisions the entry depends on:

• Annex 2 (Rules of the Air), Annex 3 (MET), Annex 10 (CNS, Vols I–V), Annex 11 (ATS), Annex 12 (SAR), Annex 14 (Aerodromes), Annex 15 (AIS/AIM), Annex 19 (SMS).

7. ASBU / BBB linkage#

The GANP technical layer the entry maps to. A FASID NAV row for a new RNP 1 SID maps up to the APTA ASBU thread and to BBB navigation baseline. A FASID COM row for a new CPDLC service maps to the COMI ASBU thread.

8. Effective date and amendment history#

Entries carry an effective date, and, in Volume III, are revised through Regional Office procedures. Volume II amendments are formal ICAO Council actions following PIRG endorsement.

9. Cost-recovery basis#

By Doc 9161, listing in the eANP is the test for whether a facility or service is "considered to be necessary for safety and efficiency" and thus chargeable through user charges per Doc 9082.

10. Coordination requirements#

Where the entry affects two or more States (boundary FIRs, cross-FIR ATS routes, regional AMHS routing, SAR cooperation), the FASID entry identifies the required Letter of Agreement, MoU, or coordination protocol.

11. Volume III dynamic flag#

Whether the entry lives in stable Volume II (Council amendment cycle) or dynamic Volume III (Regional Office amendment cycle).

12. Implementation guidance#

Where applicable, the entry references regional implementation roadmaps (APAC Seamless ATM Plan, MID Air Navigation Strategy, EUR ATM Master Plan) and PIRG conclusions that motivated it.

Worked examples#

Example 1 — EUR SSR Code Allocation row#

• Identifier. Doc 7754 (EUR), Vol II FASID, Part IV, Attachment H, one row of the EUR Originating Code Block table.
• Description. A specific Originating Code Block (e.g. 0001–0077) allocated to a specific State's ACC for SSR Mode A code assignment.
• Responsible State. Named in the row.
• Procedural element. Doc 7030 § 5.1.2.1 invokes this attachment for SSR code assignment in the EUR Region.
• Standards basis. Annex 10 Vol IV (SSR / Mode S), Doc 4444 Chapter 8 (radar service / surveillance).
• ASBU linkage. ASUR (surveillance) thread.
• Coordination. Boundary handover entries in adjacent FIRs use the agreed code-conflict-avoidance rules.

Example 2 — APAC ATS route row#

• Identifier. Doc 9673 (APAC), Vol II FASID, ATS Routes Table, Route Lxxx.
• Description. Route designator, sequence of waypoints, navigation specification (e.g. RNAV 5 or RNP 2), vertical applicability, direction, traffic category.
• Responsible States. Each FIR through which the route passes.
• Performance element. Required onboard PBN capability per Doc 9613.
• Procedural element. Doc 4444 ATS-route operating procedures plus Doc 7030 ASIA/PAC supplements.
• Standards basis. Annex 11 §2.6 (designation of ATS routes), Annex 11 Appendix 1 (ATS route principles), Doc 9613 (PBN).
• ASBU linkage. FRTO (en-route trajectory) and NAVS (PBN) threads.
• Volume III flag. Route description in Vol II; specific frequency / waypoint coordinates in Vol III.

Example 3 — CAR/SAM SAR Region row#

• Identifier. Doc 8733 (CAR/SAM), Vol II FASID, SAR part, SRR row for a specific Search and Rescue Region.
• Description. SRR boundary, RCC identification, contact details, cross-border SAR responsibilities.
• Responsible State. SRR-owning State.
• Procedural element. Doc 4444 distress procedures, IAMSAR Manual (Doc 9731).
• Standards basis. Annex 12 (Search and Rescue).
• ASBU linkage. Cross-cutting (no single thread).

How FASID entries become a national plan#

A National Air Navigation Plan (NANP) is produced by:

1. Extracting from the regional FASID every row that obliges or concerns the State.
2. Cross-referencing each row to the responsible national agency (CAA, ANSP, MET service, AIS/AIM provider, SAR authority).
3. Mapping each row to the project, funding source, regulatory action, and milestone date.
4. Aligning the package with GANP BBB completeness and ASBU module priorities.
5. Submitting amendment proposals (PfA — Proposal for Amendment) into the relevant PIRG cycle for FASID changes.
6. Maintaining Volume III State entries dynamically with the Regional Office.
7. Reporting implementation status via the PIRG annual report and the regional implementation programme (e.g. APAC Seamless ATM Plan monitoring; EUR LSSIP cycle).

What an Enabler is in the ANP context#

An Enabler is a supporting element without which an ANP entry cannot deliver its intended benefit. In ASBU, enablers are weighted toward technology and avionics. In the ANP framework, enablers are weighted toward institutional machinery — the bodies that draft, amend, endorse, and monitor the plan; the meeting cycle; and the amendment process itself. ANP planning makes these enablers explicit because without them no FASID row gets written, amended, or retired.

Enablers fall into seven categories.

1. ICAO Regional Offices#

Seven Regional Offices hold the operational pen on the regional ANPs:

• EUR/NAT (Paris) — EUR and NAT regions.
• APAC (Bangkok) — Asia/Pacific region.
• MID (Cairo) — Middle East region.
• ESAF (Nairobi) and WACAF (Dakar) — AFI region (eastern and western halves).
• NACC (Mexico City) — Caribbean region; supports NAM coordination.
• SAM (Lima) — South American region.

Each Regional Office:

• Hosts the PIRG secretariat and convenes its meetings.
• Maintains the eANP electronically (especially Volume III dynamic parts).
• Coordinates with adjacent regions on boundary FIRs, ATS routes, SSR codes, AMHS routing, and SAR.
• Liaises with the ICAO Air Navigation Bureau in Montréal on Volume II amendment proposals.

2. Planning and Implementation Regional Groups (PIRGs)#

PIRGs are the senior ICAO regional planning bodies, established by the Council, that endorse Volume I priorities and Volume II FASID amendments. The seven PIRGs:

• APANPIRG — Asia/Pacific Air Navigation Planning and Implementation Regional Group.
• EANPG — European Air Navigation Planning Group.
• APIRG — AFI Planning and Implementation Regional Group.
• MIDANPIRG — MID Air Navigation Planning and Implementation Regional Group.
• GREPECAS — CAR/SAM Regional Planning and Implementation Group.
• NAT SPG — North Atlantic Systems Planning Group.
• NACC — coordinates NAM with NAT/CAR via the NACC office.

PIRGs meet annually (typically), with sub-groups operating between plenaries. Typical sub-groups: ATM SG, AIM SG, CNS SG, MET SG, SAR TF, ATFM SG, AAITF (autonomous arrival initiatives), Aviation Information Systems Working Group, etc.

3. Regional Aviation Safety Groups (RASGs)#

RASGs are the safety counterpart to PIRGs. The Council-established RASGs operate in the same regions and coordinate Regional Aviation Safety Plans (RASPs):

• RASG-AFI — AFI region.
• RASG-APAC — Asia/Pacific.
• RASG-EUR — Europe.
• RASG-MID — Middle East.
• RASG-PA — Pan America (CAR/SAM/NAM).

RASGs do not own the eANP, but they own the safety performance lens that informs Volume I priorities and feeds Annex 19 SMS at State and service-provider level. ANP and RASG outputs are explicitly cross-linked under the GANP and the Global Aviation Safety Plan (GASP, Doc 10004).

4. Regional Air Navigation (RAN) meetings#

Triennial-or-greater Regional Air Navigation Meetings are the formal high-level forum for major eANP changes that exceed PIRG authority. Recommendations from a RAN meeting are submitted to the ICAO Council; upon approval, they amend the regional ANP at Volume II level and feed into GANP revisions. The regularity of RAN meetings has reduced as the electronic ANP regime has matured — many changes that once required a RAN now go through PIRGs and Regional Office procedures.

5. The amendment process#

The eANP amendment regime distinguishes three procedures:

• Volume I amendments. Strategic / general planning material. Endorsed by the PIRG, submitted to ICAO Council, approved as a Council action. Slow cadence (years).
• Volume II / FASID amendments. Operational core. Submitted as a Proposal for Amendment (PfA) by a State or Regional Office, reviewed by the relevant PIRG sub-group, endorsed by the PIRG plenary, formally approved by the Council. Annual to multi-year cadence.
• Volume III amendments. Dynamic State parts. Submitted directly to the Regional Office; reviewed against agreed procedures; published online. Continuous cadence (effectively as needed).

Doc 7030 (Regional Supplementary Procedures) is amended in lockstep with FASID changes, since FASID and Doc 7030 cross-reference each other.

6. National counterpart bodies#

For an ANP entry to deliver, the State must have:

• A CAA / regulator authorised under the Convention to discharge Annex obligations and approve operational arrangements.
• An ANSP (or designated service provider) able to deliver the ATS, AIS/AIM, COM, NAV, SUR, MET, SAR services listed.
• An AIS/AIM organisation capable of publishing and maintaining the AIP, AIRAC, and digital AIM products that reflect FASID entries.
• A SAR authority with RCC capability for the State's SRR.
• A safety oversight function (Annex 19 SMS, State Safety Programme) able to authorise the operational changes that FASID entries imply.
• Mechanisms for user-charge collection under Doc 9082 / Doc 9161 if the State recovers ANS costs through charges.

The ANP framework assumes — and where State capability gaps appear, ICAO supports through the No Country Left Behind (NCLB) initiative, regional implementation programmes (AFI Plan, APAC Seamless ATM Plan, MID Air Navigation Strategy), and ICAO Technical Cooperation Bureau projects.

7. Industry and inter-State coordination#

• EUROCONTROL (in EUR) — Network Manager, Performance Review Body, LSSIP cycle, supports EUR FASID maintenance.
• CANSO — air navigation service provider association, contributing technical input to PIRG sub-groups.
• IATA — airspace user input to PIRGs and RAN meetings.
• Bilateral and multilateral letters of agreement between adjacent ANSPs implementing FASID boundary entries.
• Cross-FIR ATFM and arrival management agreements (XMAN) where FASID entries imply such cooperation.

How enablers are managed in practice#

PIRG sub-groups maintain a rolling list of Conclusions and Decisions assigned to specific States or to the Regional Office. Each Conclusion is tracked to closure in the next plenary report. The ICAO Air Navigation Commission and the Council oversee the cumulative output, and the GANP Implementation Monitoring exercises consolidate progress globally.

This is why ANP planning is not merely a documentation exercise. A State that does not engage in its PIRG, does not submit PfAs, and does not participate in sub-group work will see FASID entries drift out of date — with downstream consequences for Doc 9161 cost recovery, for neighbours' operations, and for the State's standing in the ICAO USOAP audit.

The performance lens of the ANP#

The ANP framework is the regional and national execution layer of a performance-based global plan. The GANP sets KPAs, performance ambitions, and a Conceptual Roadmap; the eANPs translate these into regional priorities and FASID entries; the National Air Navigation Plans turn those into projects with measurable benefits.

The performance vocabulary comes from Doc 9854 (Global ATM Operational Concept) and Doc 9883 (Manual on Global Performance of the Air Navigation System). The chain is:

KPA  --(measured by)-->  KPI  <--(targeted by)--  Performance Objective
                                                       |
                                                       v
                                              GANP / eANP / NANP entry

Key Performance Areas (KPAs) in the ANP context#

The eleven Doc 9854 / Doc 9883 KPAs apply, but the GANP simplifies the ANP-level narrative around six headline KPAs that consistently appear in eANP Volume I performance frameworks:

1. Safety — accident, serious-incident, and loss-of-separation rates.
2. Capacity — runway, sector, network throughput.
3. Efficiency — flight efficiency (track-mile, vertical), fuel/CO2 per flight.
4. Environment — noise, emissions, fuel burn.
5. Access and equity — fair access to airspace and airports across user classes (commercial, GA, State aircraft, RPAS).
6. Cost-effectiveness — unit cost of ANS per service unit, with Doc 9082 charging and Doc 9161 cost-recovery anchors.

The remaining Doc 9883 KPAs (Security, Flight efficiency as a distinct dimension, Flexibility, Predictability, Participation, Interoperability, Global interoperability) are still tracked, but typically rolled into the six headlines for eANP Volume I narrative.

Performance Objectives in the eANPs#

Each regional eANP Volume I carries a regional performance framework: a list of Performance Objectives (POs) endorsed by the PIRG, each linked to:

• the KPAs it improves;
• the KPIs that measure it;
• the FASID parts and ASBU modules that deliver it;
• a target or trajectory.

Examples of recurring regional POs (illustrative naming, consistent with eANP Volume I style):

• PO — Reduce en-route flight inefficiency. Measured by KEP/KEA vs. great-circle. Delivered by FASID ATS route changes (free route airspace, direct routings) and ASBU FRTO / NOPS / OPFL / TBO modules.
• PO — Improve arrival predictability at major hubs. Measured by variance between planned and actual landing time. Delivered by FASID ATS / ATFM entries supporting AMAN/XMAN, A-CDM, network collaboration, and ASBU ACDM / RSEQ / NOPS / SWIM modules.
• PO — Achieve full PBN coverage. Measured by % of approach procedures with vertical guidance; % of ATS routes RNAV/RNP. Delivered by FASID NAV entries and ASBU APTA / NAVS modules.
• PO — Provide cooperative surveillance over [region]. Measured by % FIR area covered by ADS-B / Mode S / space-based ADS-B. Delivered by FASID SUR entries and ASBU ASUR modules.
• PO — Transition from product-centric AIS to data-centric AIM. Measured by AIXM 5 conformance, digital data quality. Delivered by FASID AIS/AIM entries and ASBU DAIM modules. Doc 8126 ties this directly to GANP/ASBU.
• PO — Reduce CO2 per flight. Measured by fuel/CO2 per movement and excess fuel per arrival. Delivered by FASID ATS / NAV entries enabling CDO/CCO and ASBU CDO / CCO / OPFL modules.

Regional performance frameworks#

Each region operates a tailored performance framework on top of the GANP KPAs:

APAC#

• APAC Seamless ATM Plan — the regional ASBU realisation, monitored by APANPIRG. Performance reporting feeds the annual APANPIRG report.
• KPIs: route extension vs. great-circle; ATFM delay; PBN approach coverage; ADS-B coverage in oceanic; AIXM 5 readiness.

MID#

• MID Air Navigation Strategy — the regional roadmap monitored by MIDANPIRG. Performance reporting through the MID Region Performance Framework.
• KPIs: airspace efficiency; ATFM delay; PBN approach coverage; AIM digital readiness.

EUR#

• European ATM Master Plan (SESAR Joint Undertaking) — the SES modernisation roadmap, aligned with ICAO eANP.
• EUROCONTROL Performance Review Body — independent performance assessment.
• LSSIP cycle — annual Local Single Sky Implementation reporting, which doubles as the EUR ASBU implementation report.

NAT#

• NAT Implementation Management Group (NAT IMG) — track performance against PBCS (Performance-Based Communication and Surveillance) requirements, RNP/RCP achievement, OTS efficiency.

AFI#

• AFI Plan — safety- and capacity-focused implementation programme; performance reporting via APIRG.
• KPIs heavily weighted toward Safety KPA and BBB completeness.

CAR / SAM#

• GREPECAS Performance Framework; SAM Implementation Project (SAM-IP) for SAM-specific projects.

NAM#

• US National Airspace System performance framework (FAA), NAV CANADA performance reports; coordinated with NAT and CAR through the NACC office.

Key Performance Indicators (KPIs)#

Common KPI families used in eANP Volume I and PIRG performance reports:

Safety KPIs#

• Accident and serious-incident rates.
• Runway-incursion severity-weighted rate.
• Loss-of-separation events per flight hour.

Capacity KPIs#

• Declared runway capacity at major aerodromes.
• Sustained sector throughput.
• ATFM delay per flight.

Efficiency / environment KPIs#

• KEP (filed plan vs. great-circle), KEA (actual vs. great-circle).
• Vertical efficiency, fuel/CO2 per flight, CDO conformance.

Information / interoperability KPIs#

• AIXM 5 / IWXXM data product coverage.
• SWIM service availability and conformance.
• AMHS / FF-ICE Release 1 readiness.

Cost-effectiveness KPIs#

• Unit cost of ANS per service unit (Doc 9082 framework).
• Productivity (composite flight-hours per controller).

How performance is reported#

• Globally — through the GANP Implementation Monitoring exercise, consolidated under the GANP review cycle (3-yearly, aligned with the ICAO Assembly).
• Regionally — through the PIRG annual report and the regional implementation programme (APAC Seamless ATM Plan, MID Strategy, EUR LSSIP, AFI Plan, GREPECAS, NAT IMG).
• Nationally — through the NANP, the State Safety Programme, and any State-specific environmental action plan (CORSIA / State Action Plans for emissions).

Why this matters for ANP planning#

The ANP framework would otherwise look like a static inventory of facilities. Tying every FASID entry to a Performance Objective and a KPI keeps the regional plan honest. It forces the question — "what measurable problem does this row fix?" — during the PfA cycle, and it gives the PIRG and the Council the language to ask whether deployed capability is actually delivering the promised regional benefit.

It is also what justifies, under Doc 9161, the inclusion of new facilities in the eANP for cost-recovery purposes: a State proposing a new SUR entry has to be able to show the safety, capacity, or efficiency benefit it brings to international air navigation in the region.

Three timelines to keep distinct#

When discussing ANP "dates", separate three things:

1. GANP edition timeline — when ICAO published / amended the global plan.
2. Regional ANP evolution — how the seven regional plans emerged, converged on a three-volume model, and transitioned to electronic form (eANPs).
3. National implementation timeline — each State's NANP cadence, expressed against the regional FASID and the GANP performance ambitions.

A facility entry's "effective date" in FASID is a fourth, even more specific date that planners should not confuse with any of the above.

GANP edition timeline#

The key inflection points are 2013 (ASBU born), 2016 (ASBU re-baselined), 2019 (catalogue moved to portal), and 2022 (BBB layer formalised).

Regional ANP evolution#

Paper-era regional plans (pre-2000s)#

For decades the regional ANPs were paper documents in two volumes (Basic ANP + FASID), amended through Regional Air Navigation (RAN) meetings every several years. Document numbers stabilised early:

• Doc 7474 — AFI ANP.
• Doc 7754 — EUR ANP.
• Doc 8733 — CAR/SAM FASID.
• Doc 9634 / Doc 9635 — NAT Basic ANP and FASID.
• Doc 9673 — APAC Basic ANP and FASID.
• Doc 9708 — MID ANP.

RAN meetings were the primary forum for major change. PIRGs (where they existed) handled implementation tracking but had limited amendment authority.

Three-volume model and PIRG empowerment (2000s–2010s)#

ICAO progressively moved to a three-volume eANP model: Volume I (General Planning Aspects), Volume II (FASID), Volume III (dynamic State parts). The PIRGs (APANPIRG, EANPG, APIRG, MIDANPIRG, GREPECAS, NAT SPG) gained authority to endorse Volume II amendments and to maintain Volume III through Regional Office procedures, reducing the need for full RAN cycles.

Transition to electronic ANPs (eANPs)#

The defining transition was from paper or PDF "snapshots" to electronic ANPs: web-published, dynamically maintained Volume III content for each State, with Volume I/II amendments still going through PIRG plenary endorsement and Council approval but published online. The eANP regime is now the standard:

• Volume III for each region is maintained on Regional Office portals.
• AIRAC-aligned Volume III amendments are continuous.
• Volume II amendments are batched annually or as needed.
• Volume I amendments are batched on multi-year cycles.

GANP 6th / 7th edition portal alignment#

With GANP 6th edition (2019) and 7th edition (2022), the BBB and ASBU catalogues moved onto the GANP Portal. This means an eANP Volume I priority statement (e.g. "PBN to be deployed across all FIRs") now links electronically to the relevant ASBU thread on the portal rather than reproducing module text in the regional plan.

Block / BBB availability timeline (for ANP context)#

The notional ASBU block dates that the eANPs use as their planning horizon (set in GANP 5th and carried forward):

Block 0 ........ from 2013   (BBB completion expected for all States)
Block 1 ........ from 2019
Block 2 ........ from 2025
Block 3 ........ from 2031

Visualised against GANP editions:

1998     2007     2013     2019     2025     2031     2037
 |        |        |        |        |        |        |
GANP1    GANP3    GANP4    GANP6    BlockEra BlockEra
                  (ASBU)   (Portal)  Block 2  Block 3
                                     start    start
         RAN-era   eANP transition   eANP mature

National implementation timelines#

For Pakistan / APAC, the practical cadence is:

1. Annual — APANPIRG plenary; LSSIP-style national status update into APAC Seamless ATM Plan monitoring.
2. Annual — Volume III update with the APAC Regional Office (Bangkok) for Pakistan-specific entries.
3. Multi-annual — Volume II amendments via PfA into APANPIRG ATM / AIM / CNS / MET sub-groups, supporting Doc 9673 changes.
4. Triennial — alignment with ICAO Assembly cycle and GANP review.
5. 5–10 year — major procurement cycles (CNS infrastructure refresh, ATM system modernisation) framed against ASBU block availability dates.

Implementation monitoring cadence#

• Global — GANP Implementation Monitoring, consolidated for the Council and the Assembly every three years.
• APAC — APAC Seamless ATM Plan annual monitoring through APANPIRG; APAC Regional Performance Framework.
• MID — MIDANPIRG annual monitoring against the MID Air Navigation Strategy.
• EUR — annual LSSIP cycle, which doubles as ICAO ASBU implementation reporting in Europe; EUROCONTROL Performance Review Body annual report.
• AFI — APIRG annual monitoring of the AFI Plan.
• CAR/SAM — GREPECAS annual monitoring; SAM-IP for SAM-specific projects.
• NAT — NAT IMG monitoring of NAT HLA, PBCS, and OTS performance.
• National — typically a 3–5 year NANP, reviewed annually, expressed in BBB / ASBU module terms.

How to read a date in an ANP document#

When an ANP document quotes a date, check which kind of date it is:

• "Effective date 2025-04-17" — FASID Volume III publication date for the entry, AIRAC-aligned.
• "Volume II Amendment 9 (2024)" — Council-approved Volume II amendment.
• "Block 1 from 2019" — ASBU notional global availability date.
• "Regional priority by 2027" — eANP Volume I or PIRG performance ambition.
• "GANP 7th edition (2022)" — ICAO publication date.

Mixing these up leads to false claims that a State is "behind" or "ahead" of the ANP, when in fact the only meaningful measure is the State's own NANP against the FASID effective dates and the regional performance framework targets.

Primary ICAO documents — global#

• Doc 9750-AN/963 — Global Air Navigation Plan (GANP), current edition (7th-edition family). The strategic / technical / regional / national framework. ICAO page: https://www.icao.int/global-air-navigation-plan-ganp
• Doc 9854 — Global Air Traffic Management Operational Concept. Source of the eleven KPAs used in performance frameworks.
• Doc 9883 — Manual on Global Performance of the Air Navigation System. Performance management methodology (KPAs, KPIs, POs).
• Doc 9161 — Manual on Air Navigation Services Economics. Definitional anchor — Regional ANP definition and the cost-recovery principle (§3.2 GANP linkage; §3.3 Assembly Resolution A41-10 Appendix G). Citations in this workspace anchor at: Doc 9161, Chapter 3, §3.2 — GANP linkage.
• Doc 9082 — ICAO's Policies on Charges for Airports and Air Navigation Services. Charging policy that operationalises Doc 9161.
• Doc 9587 — Policy and Guidance Material on the Economic Regulation of International Air Transport.
• Doc 4444 — PANS-ATM. Air traffic services procedures referenced by every FASID ATS / ATFM entry.
• Doc 8168 — PANS-OPS. Procedure design rules underpinning FASID NAV / approach entries.
• Doc 10066 — PANS-AIM. AIM procedures and the Aeronautical Data Catalogue underpinning FASID AIS/AIM entries.
• Doc 10157 — PANS-MET. MET procedures underpinning FASID MET entries.
• Doc 10199 — PANS-IM (Information Management). Frames the digital/automated transition "as described in the GANP (Doc 9750)".
• Doc 7030 — Regional Supplementary Procedures. Region-specific procedures (EUR, MID, ASIA/PAC, AFI, NAT, SAM, CAR). Repeatedly cross-references FASID parts.
• Doc 9613 — Performance-Based Navigation (PBN) Manual. Foundation for FASID NAV entries.
• Doc 9731 — IAMSAR Manual. Underpins FASID SAR entries.
• Doc 8126 — Aeronautical Information Services Manual. Ties Digital AIM and SWIM to GANP/ASBU objectives.
• Doc 10004 — Global Aviation Safety Plan (GASP). Safety counterpart to the GANP; informs RASGs and Volume I safety priorities.

Regional ANP documents (the seven)#

• Doc 7474 — AFI Basic ANP and FASID. Maintained by APIRG.
• Doc 7754 — EUR ANP, Volumes I, II (FASID), III. Maintained by EANPG. Notable parts:
  • Part IV, Attachment H — SSR code distribution principles for the EUR Region (invoked by Doc 7030 §5.1.2.1).
  • Part V.III, Attachments B and C — ASTER ATFM service States and CFMU slot allocation exemptions.
• Doc 8733 — CAR/SAM ANP, Volume II (FASID). Maintained by GREPECAS. Notable parts:
  • Part V, Appendix B — SSR Code Allocation Plan for the CAR/SAM Regions (invoked by Doc 7030 §5.1.3.1).
• Doc 9634 — NAT Basic ANP and Doc 9635 — NAT FASID. Maintained by NAT SPG. Covers NAT HLA, PBCS, and data link requirements.
• Doc 9673 — APAC Basic ANP and FASID. Maintained by APANPIRG. APAC BBB/ASBU regional priorities and FASID tables for AOP, ATS, COM, NAV, SUR.
• Doc 9708 — MID ANP, Volumes I, II, III. Maintained by MIDANPIRG.
• NAM regional planning material — administered by the NACC office in conjunction with the FAA NAS plan and NAV CANADA national planning. (Authoritative source — NAM does not have a single published Doc number on the model of Doc 7754.)

ICAO Annexes most touched by the ANP framework#

• Annex 2 (Rules of the Air), Annex 3 (MET), Annex 4 (Charts), Annex 6 (Operations), Annex 10 (CNS, Vols I–V), Annex 11 (ATS), Annex 12 (Search and Rescue), Annex 14 (Aerodromes), Annex 15 (AIS/AIM), Annex 17 (Security), Annex 19 (SMS).
• Annex 11, Chapter 2 (notably §2.6 and §2.32) — designation of ATS routes and air traffic services airspaces, anchoring FASID ATS entries.

Convention and Assembly Resolutions#

• Convention on International Civil Aviation, Article 37. Obligation of Contracting States to collaborate in securing the highest practicable degree of uniformity in air navigation facilities, services, and procedures — the legal basis for SARPs, PANS, and the ANP framework.
• Assembly Resolution A41-10, Appendix G. Cross-border ATS airspace delineation, cost-effective CNS/ATM implementation, joint ATS authorities (cited in Doc 9161 §3.3).
• Assembly Resolution A22-19. Assistance and advice in the implementation of Regional Plans; consolidated direction to States and PIRGs on eANP execution.

Live / authoritative ICAO sources#

• ICAO GANP page — https://www.icao.int/global-air-navigation-plan-ganp
• ICAO GANP Portal — https://ganpportal.icao.int/ — live home of the ASBU framework and the BBB layer.
• ICAO ASBU Threads catalogue — https://ganpportal.icao.int/asbu/thread
• ICAO ASBU Performance Objectives catalogue — https://www4.icao.int/ganpportal/asbu/performanceobjective
• ICAO GANP / ASBU tutorial — https://www4.icao.int/ganpportal/tutorial
• ICAO GANP Resources — https://www.icao.int/airnavigation/pages/ganp-resources.aspx

ICAO Regional Office eANP portals#

• APAC (Bangkok) — https://www.icao.int/APAC/Pages/eDocuments.aspx (APAC eANP and Doc 9673 family). Authoritative web portal for APAC Volume III maintenance.
• EUR/NAT (Paris) — https://www.icao.int/EURNAT/Pages/welcome.aspx (EUR Doc 7754 and NAT Doc 9634/9635 portals).
• MID (Cairo) — https://www.icao.int/MID/Pages/default.aspx (Doc 9708 portal).
• ESAF / WACAF (Nairobi / Dakar) — AFI eANP portals; Doc 7474 Volume III maintenance.
• NACC (Mexico City) — https://www.icao.int/NACC/Pages/welcome.aspx (CAR/NAM regional planning, GREPECAS support).
• SAM (Lima) — https://www.icao.int/SAM/Pages/welcome.aspx (Doc 8733 SAM Volume III maintenance, SAM-IP).

(Authoritative source — Regional Office portals; URL paths can shift as ICAO reorganises its web presence.)

Regional implementation programmes#

• APAC Seamless ATM Plan (APANPIRG-monitored).
• MID Air Navigation Strategy (MIDANPIRG-monitored).
• AFI Plan (APIRG-monitored).
• European ATM Master Plan (SESAR JU) and EUROCONTROL LSSIP cycle (EANPG-coordinated).
• NAT Implementation Management Group (NAT IMG).
• GREPECAS programme of work; SAM Implementation Project (SAM-IP).

Industry and supporting material#

• EUROCONTROL Network Manager — https://www.eurocontrol.int/ (Network Manager and LSSIP).
• CANSO — https://www.canso.org/
• IATA — https://www.iata.org/
• EUROCONTROL ASBU monitoring briefing (LSSIP context): https://www.eurocontrol.int/sites/default/files/2021-10/lssip2021-11-icao-asbu-monitoring.pdf

Cross-reference to other detailed folders in this workspace#

• topics_detailed/asbu/ — ASBU framework: Blocks, Threads, Modules.
• topics/air_navigation_plan.md — public summary used by the web app.
• topic/air_navigation_plan.md — working file with internal anchors and search recipes.