Detailed working notes on the body of regional aviation documents issued by the ICAO Asia and Pacific (APAC) Regional Office in Bangkok and its planning groups. This folder expands the summary in topics/apac_files.md into per-aspect files so each can be read on its own.

Files in this folder#

• overview.md — what the APAC files corpus is, the role of the APAC Regional Office, and the working bodies (APANPIRG, RASG-APAC, sub-groups).
• components.md — the categories of APAC files (Regional ANP/FASID, Seamless ANS Plan, ATFM Roadmap and Framework, AIDC ICDs, PBN, MET, AIM, SAR documents, WP/IP archives).
• blocks.md — editions and major revisions of the key APAC reference documents: where each one stands today.
• threads.md — subject areas covered by APAC files: ATM, CNS, AIM, MET, SAR, AGA.
• modules.md — anatomy of a single APAC reference file: purpose, governance, applicability, update cycle, and how it is used.
• enablers.md — APANPIRG, contributory groups, decision-making process, and the APAC Regional Office machinery that produces the files.
• performance_objectives.md — Seamless ATM / Seamless ANS performance framework KPAs and KPIs.
• timeline.md — major APAC plan editions and amendment dates.
• references.md — ICAO APAC Office URLs and direct links to the key APAC plan documents.

Reading order#

Start with overview.md, then components.md, then threads.md and blocks.md. Drill into modules.md for the anatomy of a single file and enablers.md for the governance machinery. Use performance_objectives.md to understand how the Seamless ANS Plan measures success, timeline.md for date context, and references.md for citations.

Source basis#

Content is grounded in:

• ICAO Doc 9750, Global Air Navigation Plan (GANP), 8th Edition — the global frame against which all APAC files align.
• ICAO Doc 9854, Global ATM Operational Concept — KPAs underpinning the Seamless ANS performance framework.
• ICAO Doc 9673, Asia/Pacific eANP, Volumes I, II, and III — the Regional Air Navigation Plan that hosts FASID and the performance volume.
• Asia/Pacific Seamless ANS Plan, Version 4.0 (Nov 2024).
• Asia/Pacific Regional Framework for Collaborative ATFM, Version 4.0 (Oct 2022).
• Asia/Pacific Regional AIDC ICD, Version 3, with AIDC-IGD Edition 2.0 (June 2025).
• Asia/Pacific Regional FF-ICE/R1 Implementation Plan, Version 1.0 (draft, 2026).
• ICAO APAC Office portal: https://www.icao.int/APAC

Note on local library coverage#

The local ICAO Markdown library does not mirror the APAC eDocument set. APAC content surfaces only indirectly inside global ICAO documents (regional references in Annex 10 Vol I, Doc 9804, Doc 7030). For any operational APAC question, the live APAC Office portal and the relevant APANPIRG sub-group meeting page are the authoritative sources.

What "APAC files" means#

"APAC files" is shorthand for the body of regional aviation planning and implementation documents issued and maintained by the ICAO Asia and Pacific (APAC) Regional Office in Bangkok, together with its planning and implementation groups. They are the regional layer that sits between global ICAO instruments (Annexes, PANS, Doc-series) and individual State AIPs, regulations, and operational procedures.

Most APAC files are published as eDocuments rather than priced ICAO Doc-series volumes. They are guidance- and planning-grade in form but operationally binding through the Regional Air Navigation Plan (RANP) and through their incorporation into State implementation programmes endorsed at APANPIRG.

Why a regional layer exists#

ICAO Annexes and PANS deliberately leave many implementation details to "regional air navigation agreement". Common examples:

• Communications, navigation, and surveillance (CNS) infrastructure inventories per FIR (Annex 11; Annex 10).
• Required navigation specifications and PBN approach implementation (Annex 6; Doc 9613).
• Cross-FIR ATS coordination and data exchange (Doc 4444 PANS-ATM).
• Regional supplementary procedures (Doc 7030).
• Aeronautical information services data sets, NOTAM patterns, AIRAC cycle compliance (Annex 15; Doc 10066 PANS-AIM).
• Regional MET, SAR, and AGA arrangements.

The APAC Regional Office, working through APANPIRG and its sub-groups, produces the agreed regional plans, ConOps, ICDs, and roadmaps that fill these gaps for the Asia/Pacific region.

The APAC Regional Office#

The Regional Office is based in Bangkok and is the operational arm of ICAO for the Asia and Pacific region. Its core duties are:

• Servicing APANPIRG, RASG-APAC, and their contributory bodies as Secretariat — agendas, working papers, decisions, conclusions.
• Maintaining the Asia/Pacific eANP (Doc 9673) and the regional plan ecosystem.
• Monitoring deficiencies in air navigation services through the Air Navigation Deficiencies (AND) database for the region.
• Coordinating with adjacent regions (MID, NAT, AFI) at the boundary FIRs.
• Liaising with industry bodies, the Network Manager-equivalent initiatives, and IATA's regional offices.

The working bodies#

Three bodies and their sub-groups produce most of the APAC files.

APANPIRG#

The Asia/Pacific Air Navigation Planning and Implementation Regional Group. The principal regional planning body for air navigation. Reports annually to the ICAO Air Navigation Commission through the APAC Regional Office. It approves the regional plans, endorses sub-group conclusions, and tracks deficiencies.

RASG-APAC#

The Regional Aviation Safety Group — Asia and Pacific. Owns the regional safety strategy, monitors USOAP audit findings, and produces the Annual Safety Report. Coordinates with APANPIRG on safety-relevant air navigation deficiencies.

Sub-groups under APANPIRG#

The standing contributory groups. Names and exact mandates vary by APANPIRG cycle; the typical roster includes:

• ATM/SG — Air Traffic Management Sub-Group. Owns ATM planning, PBN, FF-ICE, AIDC, ATFM/A-CDM, airspace.
• CNS SG — Communications, Navigation, and Surveillance Sub-Group. Owns CNS infrastructure, ADS-B, AMHS, voice, GNSS, spectrum.
• AOP/SG — Aerodromes Operations and Planning Sub-Group. Owns aerodrome certification, runway safety, AGA matters.
• MET/SG — Meteorology Sub-Group. Owns regional MET service provision, IWXXM, SIGMET coordination.
• AIM/SG — Aeronautical Information Management Sub-Group. Owns AIM transition, AIXM 5, digital NOTAM, eTOD, IFP.
• ATFM/A-CDM SG — ATFM and Airport Collaborative Decision Making Sub-Group. Owns the regional collaborative ATFM framework.
• RASMAG — Regional Airspace Safety Monitoring Advisory Group. Owns airspace safety monitoring, RVSM, PBN safety oversight.
• SAR/SG — Search and Rescue Sub-Group, where active.

Each sub-group typically meets once or twice a year, reports to APANPIRG, and produces the working papers (WP), information papers (IP), and decisions that become inputs to the published APAC files.

How APAC files relate to the global frame#

• ICAO Doc 9750 (GANP, 8th Edition) sets the global ASBU framework; the APAC Seamless ANS Plan operationalises it for the region.
• ICAO Doc 9673 (Asia/Pacific eANP, Vols I, II, III) is the formal Regional Air Navigation Plan; FASID lives in Volume II.
• Doc 7030 carries the regional supplementary procedures recognised by the global PANS framework.

The mental model: GANP is the global menu, the APAC eANP and Seamless ANS Plan are the regional commitments, and State implementation plans are the bottom-of-the-stack delivery vehicles.

The APAC files corpus is not a single artefact. It is a structured set of document categories, each with its own role, governance, and update cadence. The categories below are the principal building blocks.

1. Regional Air Navigation Plan (RANP / eANP)#

The formal Regional Air Navigation Plan for the Asia/Pacific region, published as ICAO Doc 9673, Asia/Pacific eANP. It has three volumes:

• Volume I — General. Stable. Strategy, regional context, ATM framework, and methodology.
• Volume II — FASID (Facilities and Services Implementation Document). Living. Per-FIR and per-State inventory of CNS, ATM, AGA, AIM, MET, and SAR facilities and services agreed by regional air navigation agreement. Amended through APANPIRG conclusions.
• Volume III — Performance-Based Volume. The principal carrier of the regional performance framework from 2026 onwards, taking on much of the role previously held by the standalone Seamless ANS Plan.

2. Asia/Pacific Seamless ANS Plan#

The flagship regional document for performance and ASBU alignment. Current edition is Version 4.0 (Nov 2024). It defines:

• The regional performance framework: KPAs, KPIs, targets per FIR.
• The agreed ASBU B0 / B1 elements per FIR.
• Cross-FIR seamless service expectations (PBN, AIDC, ATFM, AIM, MET).
• The transition path for ASBU B2 elements (initial TBO, FF-ICE).

The Seamless ANS Plan supersedes the legacy Seamless ATM Plan Version 1.0, which is retained for historical traceability.

3. Concepts of Operations (ConOps)#

Regional operational concept documents. These describe how a capability will be provided across the region before procedures and systems are finalised. Examples:

• Asia/Pacific Regional Framework for Collaborative ATFM (V4.0, October 2022) — regional ATFM ConOps with governance, CDM, and the data exchange model.
• TBO and FF-ICE/R1 ConOps elements embedded in implementation plans.

4. Implementation roadmaps and plans#

Time-phased delivery documents anchored to the Seamless ANS Plan.

• Asia/Pacific Regional FF-ICE/R1 Implementation Plan (V1.0 draft, 2026) — phased introduction of FF-ICE Release 1 with cross-border technical trials targeted from around 2030 and ICAO 2012 FPL cessation aligned to the 2032-2034 window.
• APAC ADS-B Implementation and Operations Guidance Document (AIGD) — regional rollout of ADS-B Out, separation standards, fitment guidance.
• CPDLC and AIDC implementation plans for cross-FIR data exchange.
• Regional PBN Implementation Plan consistent with Doc 9613.
• GBAS / SBAS regional roadmaps where applicable.

5. Interface Control Documents (ICDs) and Implementation Guidance Documents (IGDs)#

The technical interoperability baseline.

• Asia/Pacific Regional AIDC ICD, Version 3 with AIDC-IGD Edition 2.0 (June 2025) — the cross-FIR ATS Interfacility Data Communications interface. The ICD specifies messages and bindings; the IGD captures known issues, configuration profiles, and implementation recommendations.
• AFTN/AMHS-based ICD for ATFM, Version 2 — data exchange specification used where AIDC is not yet available, to support regional ATFM message flows.

6. Regional Plan for Collaborative AIM#

The APAC roadmap for the AIS-to-AIM transition, AIXM 5 adoption, digital NOTAM, eTOD, instrument flight procedure data, and the Aeronautical Data Catalogue per PANS-AIM (Doc 10066). Current edition: Version 4.0.

7. CNS performance and supporting documents#

Regional documents on:

• AMHS / ATN connectivity and X.400 / IPS migration.
• VHF and HF voice planning, allotment plans.
• GNSS performance monitoring and ionospheric threat work (relevant to APAC GBAS/SBAS).
• Spectrum coordination, including 5G C-band coexistence with radio altimeters.

8. MET, SAR, and AGA documents#

• MET — regional SIGMET coordination, IWXXM transition, volcanic ash and tropical cyclone advisory arrangements.
• SAR — regional SAR plan, contingency arrangements, exercises.
• AGA — regional aerodrome certification status, runway safety programme, GRF (Global Reporting Format) implementation guidance.

9. APANPIRG and sub-group meeting record#

The working trail from which most files originate.

• Working Papers (WP) — proposals for action by the meeting.
• Information Papers (IP) — background, status updates, surveys.
• Sub-group reports — formal record of conclusions, decisions, and proposed amendments going to APANPIRG.
• APANPIRG annual reports — for example APANPIRG/35.
• Regional Performance Report — annual KPI snapshot.

10. Air navigation deficiencies database#

Not a document in the conventional sense, but a maintained register of identified air navigation deficiencies (AND) for the region — referenced from APAC files when describing implementation status, and updated through sub-group reporting cycles.

How the components fit together#

GANP / Annexes / PANS / Docs (global)
          |
          v
Doc 9673 eANP Vol I/II/III  <-- Seamless ANS Plan V4.0
          |                          |
          v                          v
ConOps + Implementation Plans + ICDs/IGDs (AIDC, AMHS-ATFM, ...)
          |
          v
WP/IP through sub-groups -> APANPIRG conclusions -> AND register
          |
          v
State AIPs, regulations, operational procedures

Each layer feeds the next; APAC files are the middle band between the global frame and the State level.

This file is the APAC analogue of the ASBU "Blocks" page. Where ASBU talks about Block 0 / 1 / 2 / 3 availability windows, the APAC files corpus is structured around editions and major revisions of the key reference documents. Each major edition is a coherent baseline that States, ANSPs, and operators align to until the next baseline is endorsed by APANPIRG.

How an APAC edition works#

A typical major-edition cycle:

1. APANPIRG sub-group identifies that the existing edition is no longer fit for purpose (gaps versus a new GANP edition, new ASBU modules, fielded capability that is not yet captured, or technology inflection such as IPv6, AIXM 5.1, IWXXM 3, or FF-ICE).
2. A drafting task force is formed (e.g. ATMAS-TF for ATM automation/seamless work; ATFM/A-CDM TF; AIM/AIXM TF).
3. Successive drafts circulate as Working Papers across one or two sub-group meeting cycles.
4. APANPIRG endorses the new edition; the previous edition becomes superseded but remains in the historical archive.
5. States are expected to align AIPs, regulations, and procedures over a transition period (typically 12-24 months).

Minor amendments are issued between major editions through Decisions or Conclusions of the relevant body, with the document text itself re-published when the change is substantive.

Asia/Pacific Seamless ATM Plan / Seamless ANS Plan#

Doc 9673 — Asia/Pacific eANP#

Asia/Pacific Regional Framework for Collaborative ATFM#

AIDC ICD and AIDC-IGD#

AFTN/AMHS-based ICD for ATFM#

Asia/Pacific Regional FF-ICE/R1 Implementation Plan#

Regional Plan for Collaborative AIM#

APANPIRG and sub-group reports#

Reading an APAC edition tag#

When a document is cited as "AIDC ICD V3" or "Seamless ANS Plan V4.0", two facts are being asserted:

1. The endorsing body has accepted that text as the regional baseline.
2. Earlier editions are superseded for new implementations, although running systems may still be operating against an earlier edition under a transition arrangement.

National and bilateral implementation work always cites the specific edition and date — generic references such as "the AIDC ICD" without a version number are a frequent source of confusion in cross-FIR coordination.

This file is the APAC analogue of the ASBU "Threads" page. APAC files are organised first and foremost by subject area: ATM, CNS, AIM, MET, SAR, and AGA. Each subject area has its own sub-group, its own documents, and its own contributory task forces. This page gives the working catalogue.

The subject areas line up with the ICAO eDocuments index categories and with the APANPIRG sub-group structure.

ATM — Air Traffic Management#

The largest single body of APAC files. Owned principally by ATM/SG, with task forces for specific topics.

Headline documents:

• Asia/Pacific Seamless ANS Plan, Version 4.0 (Nov 2024).
• Asia/Pacific Regional Framework for Collaborative ATFM, Version 4.0 (October 2022).
• AIDC ICD Version 3 and AIDC-IGD Edition 2.0 (June 2025).
• AFTN/AMHS-based ICD for ATFM, Version 2.
• Asia/Pacific Regional FF-ICE/R1 Implementation Plan, Version 1.0 (draft, 2026).
• Regional PBN Implementation Plan and supporting guidance.
• A-CDM regional guidance.
• Airspace concept documents (free route airspace trials, dynamic sectorisation work).
• Contingency planning documents (volcanic ash, conflict zones).

Topics: cross-FIR coordination; ATFM and CDM; PBN; FF-ICE; airspace design; oceanic operations; UAS / RPAS integration planning.

CNS — Communications, Navigation, and Surveillance#

Owned by CNS SG with contributory task forces (e.g. CNS/SG/IPS, ADS-B/TF, GNSS/TF).

Headline documents:

• APAC ADS-B Implementation and Operations Guidance Document (AIGD) with associated separation standards.
• CPDLC and AIDC implementation plans (link with ATM).
• AMHS regional implementation guidance and IPv6 / ATN/IPS migration documents.
• VHF voice and HF voice planning documents.
• GNSS regional performance reports and ionospheric threat work relevant to APAC GBAS.
• GBAS / SBAS regional roadmaps where applicable.
• Spectrum coordination guidance, including 5G C-band coexistence with radio altimeters.

Topics: surveillance coverage and gap analysis; data link rollout; voice infrastructure; PNT (positioning, navigation, timing) resilience; spectrum.

AIM — Aeronautical Information Management#

Owned by AIM/SG, with AIXM and digital NOTAM task forces.

Headline documents:

• APAC Regional Plan for Collaborative AIM, Version 4.0.
• AIXM 5 / 5.1 transition guidance.
• Digital NOTAM implementation guidance.
• eTOD (electronic Terrain and Obstacle Data) regional guidance.
• Instrument flight procedure (IFP) data exchange guidance.
• Aeronautical Data Catalogue alignment per Doc 10066 PANS-AIM.

Topics: AIS-to-AIM transition; data quality; AIRAC discipline; digital products; IFP design data flow.

MET — Meteorology#

Owned by MET/SG, supported by the regional WMO/ICAO Meteorological Authority arrangements.

Headline documents:

• APAC IWXXM transition and implementation guidance.
• Regional SIGMET coordination procedures and message-quality monitoring reports.
• Volcanic ash and tropical cyclone advisory arrangements (link to the relevant Volcanic Ash Advisory Centres and Tropical Cyclone Advisory Centres in the region).
• World Area Forecast System (WAFS) transition guidance.

Topics: regulated MET service provision per Annex 3; transition to IWXXM and to digital MET integrated with SWIM; coordination of regional advisory products.

SAR — Search and Rescue#

Owned by the SAR Sub-Group where active, otherwise carried as a standing item under another group.

Headline documents:

• Asia/Pacific Regional SAR Plan and contingency arrangements.
• Regional SAR exercise reports.
• Coordination with adjacent regions for boundary FIRs.

Topics: SAR Region (SRR) boundaries; rescue coordination centre arrangements; exercises; lessons-learned from real events.

AGA — Aerodromes#

Owned by AOP/SG.

Headline documents:

• Regional aerodrome certification status reports.
• Runway safety programme guidance.
• Global Reporting Format (GRF) implementation guidance.
• Aerodrome contingency planning guidance (e.g. NOTAM cessation, pandemic response).
• A-CDM at the airport level (link with ATM).

Topics: aerodrome certification under Annex 14; runway safety; surface movement; aerodrome data flows into AIM.

GEN and AIG — General and Investigation#

• GEN files cover region-wide cross-cutting items: USOAP CMA coordination, training, the Air Navigation Deficiencies database, cooperative arrangements with industry.
• AIG files relate to accident and incident investigation under Annex 13, where APAC plays a regional coordination role rather than an investigative one.

Cross-subject dependencies#

APAC files routinely cross subject boundaries. Examples:

• The Seamless ANS Plan touches ATM, CNS, AIM, and MET.
• AIDC sits at the interface of ATM (procedure) and CNS (transport).
• IWXXM sits at the interface of MET and AIM (data products on SWIM).
• A-CDM crosses ATM and AGA.
• FF-ICE/R1 crosses ATM, AIM (data quality on SWIM), and CNS (ATN/IPS).

The sub-groups manage these interfaces through joint working papers and shared task forces.

A single APAC reference file (a Seamless ANS Plan edition, an AIDC ICD, an AIM Implementation Plan, etc.) follows a consistent internal structure. This page is the APAC analogue of the ASBU "Modules" file: it describes what a single document carries, how it is governed, and how it is used.

What an APAC reference file is#

An APAC reference file is a regionally agreed, named, versioned document maintained by the ICAO APAC Regional Office in conjunction with the relevant APANPIRG sub-group. It is deliverable — a State, ANSP, or operator can use it to plan, fund, procure, deploy, certify, train for, and operate a capability across the region.

Anatomy of a file#

The headline sections most APAC files share, even when worded differently:

1. Title, edition, and date#

For example: "Asia/Pacific Regional AIDC ICD, Version 3" or "Asia/Pacific Seamless ANS Plan, Version 4.0 (November 2024)". The edition and date are load-bearing — citing without them is a frequent source of error.

2. Endorsing body#

The APANPIRG body that endorsed the document, with the conclusion or decision number. Example: endorsed by APANPIRG/35 by Conclusion 35/x.

3. Purpose and scope#

A plain-language statement of the operational problem the file addresses and the geographic / operational scope it covers (region- wide, oceanic only, specific FIRs, specific user classes).

4. Governance and applicability#

• Who maintains the document (sub-group, task force).
• Who it applies to (States, ANSPs, operators, MET providers).
• The regulatory weight: regional air navigation agreement, regional supplementary procedure, or guidance-only.
• Relationship to ICAO Annexes, PANS, and Doc-series.

5. Definitions and acronyms#

Local definitions consistent with global ICAO usage.

6. Operational concept or technical specification#

The body of the document. Depending on the file type:

• Plan / ConOps — performance framework, target architecture, staged transition, RACI for actions.
• ICD — message catalogue, data dictionary, sequence diagrams, bindings, conformance levels.
• IGD — known issues, configuration profiles, recommended practices, illustrative examples.
• Roadmap — milestones, dependencies, decision gates.

7. Performance framework (where applicable)#

KPAs, KPIs, baseline values, regional targets. Most prominent in the Seamless ANS Plan and Doc 9673 Volume III.

8. Implementation guidance and timeline#

How States and ANSPs implement the file. Typically:

• Recommended implementation steps.
• Indicative timeline aligned with ASBU Block 0 / 1 / 2 windows.
• Trigger events (e.g. FANS-1/A retirement, 2012 FPL cessation).

9. Update process#

How the document will be updated and where amendments will be published.

10. References#

Citations to ICAO Annexes, PANS, Doc-series, related APAC files, and external standards (RTCA DO, EUROCAE ED, WMO).

11. Annexes / appendices#

• Per-FIR or per-State data tables (notably in FASID material).
• Conformance checklists.
• Worked examples.

Worked examples#

Example 1 — Asia/Pacific Seamless ANS Plan, Version 4.0#

• Purpose. Define the regional performance framework and the agreed ASBU B0 / B1 / initial B2 elements per FIR.
• Governance. Endorsed by APANPIRG, maintained by ATM/SG with inputs from CNS SG, AIM/SG, MET/SG.
• Applicability. All APAC States and ANSPs; operators read it for fleet planning context.
• Body. KPAs, KPIs, FIR-level targets, ASBU module status, gap analysis, action items.
• Update process. Refreshed against new GANP editions; from 2026 much of the content migrates into Doc 9673 Vol III.

Example 2 — Asia/Pacific Regional AIDC ICD, Version 3 with AIDC-IGD Edition 2.0#

• Purpose. Specify the cross-FIR ATS Interfacility Data Communications interface used between APAC ANSPs.
• Governance. Maintained by ATM/SG via the ATMAS-TF6 task force.
• Applicability. ANSPs implementing AIDC-based cross-FIR coordination.
• Body of ICD. Message set (ABI, EST, CPL, ACP, TOC, etc.), data fields, timing, error handling, transport bindings.
• Body of IGD. Conformance profiles, known issues, vendor configuration notes, lessons learned from operational deployments.
• Update process. New ICD versions when message set or transport changes; IGD editions issued more frequently to capture experience.

Example 3 — Asia/Pacific Regional Framework for Collaborative ATFM, V4.0#

• Purpose. ConOps for regional ATFM with collaborative decision-making.
• Governance. Maintained by ATFM/A-CDM SG.
• Applicability. ANSPs operating ATFM units in APAC; airspace users participating in CDM.
• Body. ATFM lifecycle, roles, daily plan, measure types, performance reporting, data exchange (linked to the AFTN/AMHS-based ICD for ATFM where AIDC is unavailable).
• Update process. Major refresh as fielded experience and new capabilities (e.g. cross-border AMAN) require it.

How files become State action#

A typical chain from an APAC file to State action:

1. State or ANSP reviews the new edition against its existing capability and AIP.
2. Gaps are identified and a national implementation plan item is created (often referenced into the State Action Plan or the national air navigation plan).
3. Funding, regulation, and procurement are aligned.
4. Implementation status is reported into APANPIRG through the relevant sub-group, feeding the regional performance report and the Air Navigation Deficiencies (AND) database.
5. Where applicable, the AIP is amended via AIRAC and the change is notified to neighbouring FIRs.

This file is the APAC analogue of the ASBU "Enablers" page. ASBU enablers describe the supporting elements (CNS infrastructure, procedures, regulation, training) that must be in place for a module to deliver its benefit. For the APAC files corpus, the enablers are the governance machinery that produces and maintains the files in the first place: APANPIRG, RASG-APAC, sub-groups, task forces, the Regional Office, and the decision-making process that ties them together.

1. The APAC Regional Office#

Based in Bangkok, the office is the operational arm of ICAO for the Asia/Pacific region. Its enabling functions for the APAC files corpus are:

• Secretariat. Administers APANPIRG, RASG-APAC, and the contributory sub-groups: agendas, papers, minutes, conclusions, follow-up.
• Editorial. Maintains the eDocuments index, publishes endorsed versions, retires superseded editions.
• Coordination. Liaises with adjacent regions (MID, NAT, AFI), with ICAO HQ, with industry (IATA, CANSO), and with WMO, IMO, and other treaty bodies on cross-cutting items.
• Monitoring. Owns the Air Navigation Deficiencies (AND) database for the region and the Regional Performance Report cycle.
• Capacity-building. Coordinates regional workshops, training, and assistance to States needing implementation support.

2. APANPIRG — the principal planning body#

The Asia/Pacific Air Navigation Planning and Implementation Regional Group.

• Mandate. Endorses the regional air navigation plans and the associated APAC files; oversees implementation; identifies deficiencies; reports to the ICAO Air Navigation Commission.
• Membership. APAC States, observed by international organisations (IATA, IFALPA, IFATCA, CANSO).
• Cadence. Annual plenary; numbered sequentially (e.g. APANPIRG/35).
• Output. Conclusions (calls for action by States or ICAO) and Decisions (internal to the group). These are the formal hooks by which a sub-group output becomes a regional commitment.

3. RASG-APAC — the safety counterpart#

The Regional Aviation Safety Group — Asia and Pacific is the safety-side counterpart to APANPIRG. Where an APAC file has a safety dimension (e.g. runway safety, GRF, occurrence reporting, USOAP-related items), RASG-APAC owns the safety strategy and coordinates with APANPIRG to ensure the air navigation plan reflects safety priorities.

4. The standing sub-groups#

The sub-groups under APANPIRG are the working layer where most APAC files originate. Typical roster (names and exact mandates evolve):

• ATM/SG — Air Traffic Management Sub-Group.
• CNS SG — Communications, Navigation, Surveillance Sub-Group.
• AOP/SG — Aerodromes Operations and Planning Sub-Group.
• MET/SG — Meteorology Sub-Group.
• AIM/SG — Aeronautical Information Management Sub-Group.
• ATFM/A-CDM SG — ATFM and A-CDM Sub-Group.
• RASMAG — Regional Airspace Safety Monitoring Advisory Group.
• SAR/SG — where active.

Each sub-group maintains its own working catalogue, publishes its meeting reports, and tables conclusions to APANPIRG.

5. Task forces and ad-hoc groups#

Sub-groups spin up task forces for specific deliverables. Examples:

• ATMAS-TF — ATM automation / Seamless work; produced AIDC ICD V3 and AIDC-IGD Edition 2.0 in the ATMAS-TF6 cycle.
• FF-ICE/TF — drafting of the regional FF-ICE/R1 Implementation Plan.
• AIXM/TF — AIXM 5 / 5.1 transition.
• GBAS/TF, ADS-B/TF, IPS/TF under CNS SG.
• VAAC and TCAC working arrangements under MET/SG.

Task forces operate on a defined scope and deadline, then dissolve or re-charter.

6. The decision-making process#

Member State / industry input
        |
        v
Working Paper (WP) / Information Paper (IP)
        |
        v
Sub-group meeting -> draft conclusion
        |
        v
APANPIRG plenary -> Conclusion adopted
        |
        v
APAC Office publishes the new / amended file
        |
        v
States align AIPs, regulations, and procedures
        |
        v
Status reported back through the AND database
        and the Regional Performance Report

The cycle is genuinely consensus-based: APANPIRG conclusions are agreed by member States rather than imposed.

7. Industry and treaty-body coordination#

APAC files do not exist in isolation. They are coordinated with:

• IATA APAC and CANSO APAC for airline and ANSP perspectives.
• IFATCA / IFALPA for controller and pilot input.
• WMO for MET service provision (joint ICAO/WMO arrangements).
• IMO for SAR coordination at the maritime / aeronautical boundary.
• National regulators through their representatives at APANPIRG and sub-groups.

8. Cross-region coordination#

Boundary FIR coordination with:

• MIDANPIRG (ICAO MID Office) for the western boundary.
• EANPG / NAT for North Pacific traffic flows.
• AFI Planning and Implementation Regional Group for the western Indian Ocean boundary.

9. Why governance is the enabler#

For the ASBU corpus, hardware (radar, data link, GNSS) and procedures are the enablers. For the APAC files corpus, the binding constraint is agreement among 40+ States on how to operate together. The APANPIRG / sub-group / task force machinery exists because there is no other way to produce regionally binding planning material at the required cadence.

A State that wants to influence the APAC files corpus does so by participating actively in the sub-groups and tabling well-evidenced working papers. A State that ignores the machinery finds itself with neighbouring FIRs operating to a baseline it has not signed up to.

The Asia/Pacific Seamless ANS Plan (Version 4.0, November 2024) and the performance volume of the eANP (Doc 9673 Volume III) carry the regional performance framework. This file describes the KPAs and KPIs as they are applied in the APAC corpus.

The chain#

KPA  --(measured by)-->  KPI  <--(targeted by)-->  Performance Objective
  --(achieved by)-->  ASBU module / APAC file commitment per FIR

The structure is the same as for global ASBU, but the targets are regional and the KPI baselines are FIR-specific.

KPAs used in the APAC framework#

The Seamless ANS Plan applies the eleven KPAs from ICAO Doc 9854, Global ATM Operational Concept, with the regional emphasis on the KPAs that drive cross-FIR seamless service:

1. Safety — accident, incident, and loss-of-separation rates.
2. Capacity — runway, sector, and oceanic track-system throughput.
3. Flight efficiency — track-mile and vertical-profile efficiency.
4. Predictability — variance between planned and actual times.
5. Environmental impact — fuel burn, CO2, noise.
6. Cost-effectiveness — unit cost of ANS service.
7. Flexibility — ability of users to reroute / re-level tactically.
8. Access and equity — fair access to airspace and procedures.
9. Interoperability — common procedures and data formats across FIRs.
10. Participation — stakeholder involvement in regional planning.
11. Security — protection of ATM information assets.

The APAC headline targets concentrate on safety, capacity, flight efficiency, predictability, environment, and interoperability, because those are the KPAs that move when the seamless concept is properly implemented across FIR boundaries.

Performance objectives most prominent in APAC#

The Seamless ANS Plan organises commitments around objectives such as the following (illustrative; the document text varies by edition):

• Seamless cross-FIR coordination. Every shared FIR boundary uses AIDC where technically possible, and a documented coordination procedure where it is not.
• Region-wide PBN. Full PBN approach coverage with vertical guidance at all instrument runway ends; PBN en-route routes consistent with Doc 9613.
• Cooperative surveillance everywhere it is feasible. ADS-B Out coverage with appropriate separation standards; space-based ADS-B for oceanic.
• Regional ATFM / A-CDM. Operational ATFM units in every State of significance; regional CDM via the Asia/Pacific Regional Framework for Collaborative ATFM, V4.0.
• Digital AIM. AIXM 5 data products, digital NOTAM, eTOD, Aeronautical Data Catalogue alignment per Doc 10066.
• IWXXM-based MET. All operational MET messages exchanged in IWXXM at the regional boundary.
• FF-ICE/R1 readiness. Phased introduction of FF-ICE Release 1, with cross-border technical trials targeted from around 2030 and 2012 FPL cessation aligned to 2032-2034.
• Free Route Airspace expansion. Where traffic patterns and surveillance support it.

Each objective is tied to one or more measurable KPIs and to specific APAC files (Seamless ANS Plan tables, eANP FASID amendments, AIDC ICD, Collaborative ATFM Framework, etc.).

KPIs reported in the APAC framework#

Common KPIs surfaced in regional reporting (subset):

Safety KPIs#

• Reportable safety occurrences per 100,000 movements at the regional level.
• Loss-of-separation events per flight hour, by FIR.
• Runway incursion severity-weighted rate.

Capacity KPIs#

• Declared sector capacities for high-density APAC FIRs.
• Oceanic track system throughput (NOPAC, ATS routes in the South China Sea, Bay of Bengal).
• ATFM-regulated minutes of delay per flight in the worst-day-of-year and busy-day-average measures.

Flight efficiency KPIs#

• KEP / KEA equivalents for APAC: filed and actual flight efficiency versus great-circle distance.
• Vertical efficiency: cruise altitude versus optimum.
• Free-route airspace utilisation where deployed.

Predictability KPIs#

• Standard deviation of arrival time at hub airports.
• ATFM slot adherence in regulated periods.

Environmental KPIs#

• Fuel burn per flight at the regional level.
• Excess fuel per arrival as a CDO conformance proxy.

Interoperability KPIs#

• Percentage of FIR-to-FIR boundaries using AIDC vs. voice-coordination only.
• IWXXM message conformance percentage at regional MET centres.
• AIXM 5 data product coverage percentage at AIS/AIM offices.

Cost-effectiveness KPIs#

• Unit cost of ANS per service unit at the State level (Doc 9082 charging principles).
• Productivity at the regional level.

How performance is reported#

• Annually through the APAC Regional Performance Report at APANPIRG plenary.
• Through sub-group reports against their respective specialty KPIs.
• Through the Air Navigation Deficiencies (AND) database for identified gaps.
• Through State Action Plans where these are produced (notably for environment and safety).

Why the performance lens matters for APAC files#

Tying every Seamless ANS Plan commitment to a KPI keeps the regional files corpus honest. It forces the question "what measurable problem does this fix?" during the drafting cycle, and it gives APANPIRG the language to ask whether deployed capability is delivering the promised regional benefit. The migration of much of the Seamless ANS Plan content into Doc 9673 Volume III from 2026 is an explicit move to make the performance framework the spine of the regional plan, rather than a parallel document.

Three timelines to keep distinct#

When discussing APAC dates, separate three things:

1. Global GANP / ASBU edition timeline — when ICAO published or amended the global frame.
2. APAC plan edition timeline — when each major regional document was endorsed by APANPIRG.
3. APANPIRG meeting cadence — when the plenary met and the conclusions adopted at that meeting.

A State implementation roadmap is a fourth timeline, derived from these.

Global frame anchors#

Asia/Pacific Seamless ATM / Seamless ANS Plan editions#

Doc 9673 — Asia/Pacific eANP#

• Volume I — General. Stable; refreshed alongside major GANP revisions.
• Volume II — FASID. Living. Amended through APANPIRG conclusions multiple times per year. Amendments published by the APAC Office after each plenary.
• Volume III — Performance-Based Volume. Maturing through the APANPIRG/35 cycle to absorb Seamless ANS Plan content from 2026.

Asia/Pacific Regional Framework for Collaborative ATFM#

AIDC ICD and AIDC-IGD#

AFTN/AMHS-based ICD for ATFM#

Asia/Pacific Regional FF-ICE/R1 Implementation Plan#

Regional Plan for Collaborative AIM#

APANPIRG plenary cadence#

APANPIRG meets annually and is numbered sequentially.

APANPIRG/30  --  APANPIRG/31  --  ...  --  APANPIRG/35  --  ...
   |                                          |
   each plenary endorses sub-group reports,   most-recent-
   adopts conclusions, and triggers the       referenced
   amendment of the relevant APAC files       annual cycle

The most recent referenced cycle in current APAC files is APANPIRG/35. The conclusions adopted at each plenary are the formal hooks by which sub-group output becomes a regional commitment and an amendment to the eANP, the Seamless ANS Plan, or the relevant ICD.

Visualised timeline (illustrative)#

2013        2016        2019        2022        2024        2026 ->
 |           |           |           |           |           |
 GANP-4     GANP-5      GANP-6      GANP-7      GANP-8      eANP III
 Seamless   Seamless    Seamless    Seamless    Seamless    consolidates
 ATM V1     ATM V2      ATM V3      ATFM V4.0   ANS V4.0    perf content
                                                            FF-ICE/R1
                                                            draft V1.0

How to read a date in an APAC file#

When an APAC document uses a date, check which kind of date it is:

• "Seamless ANS Plan V4.0 (November 2024)" — APAC plan endorsement date.
• "AIDC-IGD Edition 2.0 (June 2025)" — APAC technical document publication date.
• "ASBU Block 1 from 2019" — global notional availability date.
• "FPL 2012 cessation 2032-2034" — global ICAO target with regional alignment.
• "APANPIRG/35" — the plenary number; the actual meeting year is derived from the sequence.

Mixing these up leads to false claims that APAC is "behind" or "ahead" of ASBU. The only meaningful measure is what the current APAC plan edition actually commits to and what the latest APANPIRG conclusions say.

Primary regional documents#

• Asia/Pacific Seamless ANS Plan, Version 4.0 (November 2024) — flagship regional performance and ASBU alignment document.
• Asia/Pacific Seamless ATM Plan, Version 1.0 — legacy predecessor of the Seamless ANS Plan, retained for historical traceability.
• ICAO Doc 9673, Asia/Pacific eANP, Volumes I, II, and III — Regional Air Navigation Plan covering general/strategy (Vol I), facilities and services / FASID (Vol II), and performance objectives (Vol III).
• Asia/Pacific Regional Framework for Collaborative ATFM, Version 4.0 (October 2022) — regional ATFM ConOps with governance and CDM elements.
• Asia/Pacific Regional Interface Control Document for ATS Interfacility Data Communications (AIDC ICD), Version 3, with AIDC-IGD Edition 2.0 (June 2025) — interoperability baseline for cross-FIR coordination, produced through ATMAS-TF6.
• AFTN/AMHS-based ICD for ATFM, Version 2 — ATFM message exchange specification used where AIDC is unavailable.
• Asia/Pacific Regional FF-ICE/R1 Implementation Plan, Version 1.0 (draft, 2026) — phased FF-ICE Release 1 path; cross-border technical trials targeted from around 2030; ICAO 2012 FPL cessation aligned to 2032-2034.
• APAC Regional Plan for Collaborative AIM, Version 4.0 — regional AIM transition, AIXM 5 / 5.1 path, digital NOTAM, eTOD, Aeronautical Data Catalogue alignment.
• APAC ADS-B Implementation and Operations Guidance Document (AIGD) — regional ADS-B Out rollout, separation standards, fitment guidance.
• APANPIRG annual reports (most recently APANPIRG/35) — formal record of conclusions, decisions, and deficiencies adopted at the Regional Group plenary.
• APAC Regional Performance Report — annual KPI snapshot.

Global frame anchors#

• ICAO Doc 9750, Global Air Navigation Plan (GANP), 8th Edition — global frame to which the Seamless ANS Plan V4.0 aligns.
• ICAO Doc 9854, Global Air Traffic Management Operational Concept — source of the eleven Key Performance Areas used in the APAC performance framework.
• ICAO Doc 9883, Manual on Global Performance of the Air Navigation System — performance management methodology used in regional reporting.
• ICAO Doc 4444 (PANS-ATM), Doc 8168 (PANS-OPS), Doc 10066 (PANS-AIM), Doc 10157 (PANS-MET) — procedural anchors for APAC files.
• ICAO Doc 7030, Regional Supplementary Procedures — including the ASIA/PAC region supplements.
• ICAO Doc 9613, Performance-Based Navigation (PBN) Manual — basis for the regional PBN Implementation Plan.

ICAO Annexes most touched by APAC files#

• Annex 1 (Personnel Licensing); Annex 3 (Meteorological Service); Annex 4 (Aeronautical Charts); Annex 6 (Operation of Aircraft); Annex 10 (Aeronautical Telecommunications, Volumes I-V); Annex 11 (Air Traffic Services); Annex 12 (Search and Rescue); Annex 13 (Accident Investigation); Annex 14 (Aerodromes); Annex 15 (Aeronautical Information Services); Annex 17 (Security); Annex 19 (Safety Management).

Live ICAO APAC sources#

• APAC Office landing page — https://www.icao.int/APAC
• APAC eDocuments index — https://www.icao.int/APAC/apac-electronic-documents (categories: GEN, AGA, ATM, CNS, MET, AIM, SAR, AIG)
• Asia/Pacific Seamless ANS Plan page — https://www.icao.int/APAC/asia-pacific-seamless-ans-plan
• APAC Air Navigation Plan (RANP) page — https://www.icao.int/APAC/apac-air-navigation-plan-anp
• APANPIRG meetings, reports, decisions — https://www.icao.int/apac/apanpirg
• APAC meetings archive (WP/IP by year and sub-group) — https://www.icao.int/APAC/meetings

Direct document links#

• Seamless ANS Plan V4.0 PDF — https://www.icao.int/sites/default/files/APAC/Documents/Asia-Pacific-Seamless-ANS-Plan-Version-4.0.pdf
• Asia/Pacific Regional Framework for Collaborative ATFM V4.0 (October 2022) PDF — https://www.icao.int/sites/default/files/APAC/Documents/edocs/ATM/Asia-Pacific-Regional-Framework-for-Collaborative-ATFM-version-4.0-October-2022.pdf
• AIDC ICD V3 PDF — https://www.icao.int/sites/default/files/APAC/Documents/edocs/icd_aidc_ver3.pdf
• AIDC-IGD Edition 2.0 (June 2025) PDF — https://www.icao.int/sites/default/files/APAC/Documents/AIDC-IGD-Edition-2.0-June-2025-ATMAS-TF6.pdf
• AFTN/AMHS-based ICD for ATFM V2 PDF — https://www.icao.int/sites/default/files/APAC/Documents/edocs/APX-E-AFTNAMHS-based-ICD-for-ATFM-Ver.2.pdf

Cross-region context#

• MIDANPIRG (ICAO MID Office) — boundary coordination on the western side. (authoritative source — not in local library)
• EANPG / NAT — North Pacific traffic flows.
• AFI Planning and Implementation Regional Group — boundary coordination across the western Indian Ocean.

Industry / treaty-body coordination#

• WMO — joint ICAO/WMO arrangements for MET service provision.
• IMO — SAR coordination at the maritime-aeronautical boundary.
• IATA APAC and CANSO APAC — operator and ANSP perspectives fed into APANPIRG via observer status.
• IFATCA / IFALPA — controller and pilot perspectives.

Local library coverage note#

The local ICAO Markdown library does not mirror the APAC eDocument set. APAC content surfaces only indirectly inside global ICAO documents — for example regional references to Asia/Pacific in Doc 9804 (Aeronautical Surveillance Manual), ionospheric threat-model material relevant to APAC GBAS in Annex 10 Volume I, and regional supplementary procedures in Doc 7030. For any operational APAC question (Seamless ANS targets, AIDC configuration, ATFM ConOps, FF-ICE phasing, RANP deficiencies), the live APAC Office portal and the relevant APANPIRG sub-group meeting page are the authoritative sources.