Detailed working notes on the local ICAO file set used by this workspace as its reference corpus. This folder expands the summary in topics/icao_files.md into per-aspect files so each can be read on its own.

Files in this folder#

• overview.md — what the local ICAO file set is, its scope, and how it relates to the authoritative ICAO publications.
• components.md — file categories (Annexes, PANS, Documents) and the consolidation / volume / part / language naming conventions.
• blocks.md — the three top-level blocks (Annex, PANS, Doc) and the role each block plays in the ICAO publication architecture.
• threads.md — subject-coverage threads (CNS, ATM, AIM, MET, AGA, SAR, ENV, SEC) cutting across the three blocks.
• modules.md — anatomy of a single consolidation file: purpose, expected headings, amendment markers, signposts inside the text.
• enablers.md — the conversion pipeline (PDF to Markdown), the search workflow used in this workspace, and integration with the per-topic source map.
• performance_objectives.md — quality and coverage objectives for the local set: completeness, freshness, accuracy, searchability.
• timeline.md — the April 2026 snapshot used here, ICAO amendment cadence, and envisaged refresh policy.
• references.md — pointers to the authoritative ICAO publications portal and stores; reminder that local files are working copies.

Reading order#

Start with overview.md, then components.md, then blocks.md and threads.md, then drill into modules.md, enablers.md, and performance_objectives.md. Use timeline.md for snapshot context and references.md for the authoritative external sources.

Source basis#

Content is grounded in:

• The ICAO publications catalogue (Annexes 1 to 19, the PANS series, and the Doc series).
• ICAO Doc 7300 — Convention on International Civil Aviation, Articles 37 and 54(l), which define why Annexes and PANS exist.
• ICAO Doc 8143 — Directives to Divisional-type Air Navigation Meetings (drafting and amendment process for SARPs and PANS).
• ICAO Doc 10184 — Assembly Resolutions in Force.
• The ICAO publications portal: https://store.icao.int/
• The ICAO public site: https://www.icao.int/

Scope reminder#

This folder describes the local file set as a curated index into the ICAO body of work. It does not replace the authoritative ICAO editions and amendments — those remain at ICAO. The local set exists so that topic notes elsewhere in this workspace can resolve to a stable, fully searchable Markdown surface during day-to-day work.

Conventions used inside this folder#

• ASCII text only. No emojis. Plain URLs.
• Citations to ICAO publications use the formal style: Annex / PANS / Doc identifier, chapter, section number with the paragraph mark (§). Example: "Annex 11 (Air Traffic Services), Chapter 2, §2.6".
• No local filesystem paths and no shell commands appear in any file in this folder. Anchors and search recipes belong in the working notes under topic/, not here.
• Where a publication is named that does not sit in the local file set, its citation is suffixed "(authoritative source — not in local library)" so that the reader knows to consult ICAO directly.

How this folder is used#

Open overview.md for the framing, components.md for what the set contains, blocks.md and threads.md for navigation, and the remaining files for pipeline, quality, timeline, and external references. Read in that order on a first pass; thereafter use any file as a standalone reference.

What the local ICAO file set is#

In this workspace, "ICAO files" means the curated April 2026 snapshot of ICAO publications held alongside this repository as a reference corpus. The set comprises original ICAO PDFs together with paired Markdown conversions. The Markdown layer is the primary search surface; the PDFs are opened only when layout, tables, figures, or exact wording must be confirmed for a citation.

This repository (NextGenDiscuss) holds topic notes, source maps, and discussion material. It does not duplicate the ICAO text. Treat the local file set as the reference corpus that topic notes resolve into.

Why it exists#

ICAO publications are issued primarily as PDFs. PDFs do not lend themselves to grep-style searching across hundreds of chapters. Working on 24 cross-cutting aviation topics requires a search surface that:

• Covers Annexes, PANS, and the Doc series in one place.
• Returns line numbers so a hit can be turned into a stable anchor.
• Preserves enough structure (headings, paragraphs, lists, tables) that a hit is recognisable as a SARP, a recommended practice, a procedure, or guidance text.
• Is read-only and never edited, so the corpus stays faithful to the ICAO source.

The Markdown layer satisfies these needs. The PDF layer is retained as the authority of last resort for exact wording and figure layout.

Scope of coverage#

The set covers the three publication families that matter for air navigation work:

1. Annexes 1 to 19 to the Convention on International Civil Aviation (the Standards And Recommended Practices, or SARPs). All nineteen Annexes are present, with multi-volume Annexes (notably Annex 6, Annex 10, Annex 14, Annex 16) split into their published parts and volumes.
2. PANS — the Procedures for Air Navigation Services. The set includes the main PANS documents covering ATM, OPS, AIM, MET, Aerodromes, ABC abbreviations, Training, and the environmental procedures.
3. Doc series — manuals, guidance material, and consolidated technical documents identified by four-digit "Doc" numbers (for example Doc 9613 PBN Manual, Doc 9750 GANP, Doc 9859 SMS Manual, Doc 8126 AIS Manual).

Circulars and supporting material are folded into the Doc series where present. The set does not aim to be every ICAO publication ever issued; it aims to be the working subset relevant to ATM, CNS, AIM, MET, aerodromes, safety, and related policy work.

Relation to the authoritative ICAO versions#

The local file set is a working copy, not a substitute:

• The authoritative editions live in the ICAO Online Store (https://store.icao.int/) and on ICAO-NET (https://portal.icao.int/), the subscription portal for States and approved users.
• Free guidance pages live on https://www.icao.int/ (GANP, CORSIA, safety, SMS, and similar topical hubs).
• For any citation that will be used outside this workspace, the authoritative edition and current amendment number must be checked against the ICAO source.

Within this workspace, citations follow the formal ICAO style: Annex / PANS / Doc identifier, chapter, section number with the paragraph mark (for example "Annex 11, Chapter 2, §2.6").

What the set is not#

• It is not an authoritative source of SARPs. Use the ICAO original.
• It is not a parallel publication. It is not redistributed.
• It is not a substitute for amendments. Between snapshots, ICAO publishes amendments that this set will not yet reflect.
• It is not a substitute for translations. Where a publication exists in multiple ICAO languages, the local set keeps only the English working copy unless otherwise noted in the file name.

How topic notes use it#

Each topic in this workspace points into the ICAO file set through:

• An internal anchor (file plus line number) in the topic working notes.
• A formal citation (Annex / Doc, chapter, paragraph) in the published topic file rendered by the web app.
• A search recipe in sources_internal.md that re-derives the anchors if the file set is refreshed.

This is the mental model: published topic cites the formal ICAO reference, working topic keeps the line-number anchor for the present snapshot, the file set is what those anchors resolve into.

The local ICAO file set is organised as three parallel components: a PDF layer, a Markdown layer, and a download manifest. Each plays a defined role and has its own naming conventions.

1. PDF layer#

The PDF layer holds the original ICAO publications as issued. Within the set the PDFs are partitioned into the same three families used by ICAO:

• Annexes — Annex 1 through Annex 19, with separately published volumes and parts kept as separate files.
• PANS — the principal Procedures for Air Navigation Services documents.
• Documents — the four-digit Doc series (manuals and guidance).

PDFs are opened when wording must be quoted exactly, when a figure or chart is needed, or when a complex table must be read with its original column structure intact. They are otherwise left closed; reading PDF across 150-plus files for daily lookups is impractical.

2. Markdown layer#

The Markdown layer is the working search surface. Its directory layout mirrors the PDF layer one-for-one: every PDF has a same-named Markdown sibling. The Markdown is generated from the PDF by an automated pipeline (see enablers.md).

Three subfolders, matching the publication families:

• Annexes/ — the SARPs (Standards And Recommended Practices) attached to the Convention on International Civil Aviation. Approximately thirty files, covering Annex 1 to Annex 19 with multi-volume splits.
• PANS/ — the principal PANS documents. Around ten files. PANS publications give the operational procedures that complement the Annexes.
• Documents/ — the Doc series manuals and guidance. Around 110 files.

Markdown is the primary read for this workspace because it is fully searchable, returns line numbers that can be turned into stable anchors, and preserves enough document structure (headings, lists, paragraphs) for a hit to be recognised in context.

3. Download manifest#

A simple comma-separated manifest accompanies the file set, recording what was fetched, on which date, in which language, and under which ICAO identifier. The manifest is the authoritative cross-reference between bare four-digit Doc filenames and human-readable titles. It is the place to consult when a search returns a Doc number whose subject is not already known.

Naming conventions#

ICAO publication identifiers are short. The local file set adds suffixes to keep volumes, parts, language, and consolidation status visible at a glance.

Suffix vocabulary#

• _cons — consolidated edition (the Annex / PANS / Doc as currently amended at the snapshot date), as opposed to a base edition plus a separate stack of amendments.
• _en — English language version. Used where an ICAO publication is routinely issued in multiple languages and the language must be visible in the filename.
• _v1, _v2, _v3, _v4, _v5 — volume number, used by Annexes and PANS that publish in multiple volumes (Annex 10, Annex 14, Annex 16, Doc 8168).
• _p1, _p2, _p3 — part number, used by Annexes that split into parts (Annex 6).
• _note — supplementary editorial note attached to a numbered volume.

Annex filenames#

Annex filenames begin with AN or an followed by the two-digit Annex number, then the volume or part suffix where applicable, then _cons, then the file extension. Examples:

• an11_cons.md — Annex 11, Air Traffic Services, consolidated.
• AN10_V1_cons.md — Annex 10, Aeronautical Telecommunications, Volume I (Radio Navigation Aids), consolidated.
• an14_v1_cons.md — Annex 14, Aerodromes, Volume I (Aerodrome Design and Operations), consolidated.
• AN06_P1_cons.md — Annex 6, Operation of Aircraft, Part I (International Commercial Air Transport — Aeroplanes), consolidated.

Case (AN vs an) is not semantically significant; it reflects the state of the source pipeline at the time each file was generated.

PANS filenames#

PANS filenames begin with the four- or five-digit Doc number, then the volume suffix where applicable, then _cons_en, then the file extension. Examples:

• 4444_cons_en.md — Doc 4444, PANS-ATM.
• 8168_v1_cons_en.md — Doc 8168, PANS-OPS, Volume I.
• 10066_cons_en.md — Doc 10066, PANS-AIM.

Document filenames#

Documents follow the same <docnum>_cons_en pattern, possibly with a volume suffix. Some documents carry only the four-digit number with no volume suffix.

When the same publication appears twice#

Doc 4444 (PANS-ATM) may be reachable through two paths in the set: as part of the PANS subfolder and again under the Doc series. This is by design — Doc 4444 is both a PANS document and a numbered Doc — and either path resolves to the same content. Treat the PANS folder as the canonical search location for ATS procedures.

Why three components rather than one#

Keeping PDFs and Markdown separate, with a manifest cross-reference, gives three properties at once: searchable text, citable original, and a deterministic mapping between bare numbers and human titles. Fold any of these together and one of the three properties is lost.

What a block is, in this context#

In the asbu folder of this workspace, "Block" means an ASBU time-phased availability window. In this folder it means a different thing: the top-level publication block — the family that an ICAO publication belongs to and the legal or procedural weight that family carries.

There are three publication blocks in the local file set, each with a distinct role.

Block A — Annexes (the SARPs block)#

What it is. The nineteen Annexes to the Convention on International Civil Aviation. Each Annex contains Standards (binding on Contracting States, with mandatory notification of differences under Article 38) and Recommended Practices (advisory but expected to be followed unless impracticable).

Legal basis. Convention on International Civil Aviation, Article 37 (adoption of international standards and procedures) and Article 54(l) (Council adoption of Annexes by two-thirds vote).

Coverage in the local set. All nineteen Annexes are present, with multi-volume Annexes split into their published volumes:

• Annex 1 — Personnel Licensing.
• Annex 2 — Rules of the Air.
• Annex 3 — Meteorological Service for International Air Navigation.
• Annex 4 — Aeronautical Charts.
• Annex 5 — Units of Measurement.
• Annex 6 — Operation of Aircraft (Part I commercial aeroplanes, Part II general aviation, Part III helicopters).
• Annex 7 — Aircraft Nationality and Registration Marks.
• Annex 8 — Airworthiness of Aircraft.
• Annex 9 — Facilitation.
• Annex 10 — Aeronautical Telecommunications (Volume I radio nav aids, Volume II communication procedures, Volume III communication systems, Volume IV surveillance and ACAS, Volume V aeronautical radio frequency spectrum).
• Annex 11 — Air Traffic Services.
• Annex 12 — Search and Rescue.
• Annex 13 — Aircraft Accident and Incident Investigation.
• Annex 14 — Aerodromes (Volume I design and operations, Volume II heliports).
• Annex 15 — Aeronautical Information Services.
• Annex 16 — Environmental Protection (Volume I noise, Volume II engine emissions, Volume III aeroplane CO2, Volume IV CORSIA).
• Annex 17 — Security.
• Annex 18 — Safe Transport of Dangerous Goods by Air.
• Annex 19 — Safety Management.

How it is read in this workspace. Annexes are the first stop when a topic question is "what does ICAO require?" — they carry the mandatory text. Citations must use the chapter and paragraph mark (for example "Annex 11, Chapter 2, §2.6").

Block B — PANS (the procedures block)#

What it is. Procedures for Air Navigation Services. PANS publications give the operational procedures that complement the Annexes — they fill in the "how" once the Annex has set the "what".

Legal basis. PANS are approved by the ICAO Council and recommended to Contracting States for worldwide application. They are not Annexes, but in operational practice they are treated as binding for routine provision of services.

Coverage in the local set. The principal PANS documents are present:

• Doc 4444 — PANS-ATM (Air Traffic Management procedures).
• Doc 8168 — PANS-OPS (Aircraft Operations) Volumes I, II, and III, plus the Volume II editorial note.
• Doc 8400 — PANS-ABC (ICAO Abbreviations and Codes).
• Doc 9868 — PANS-Training.
• Doc 10066 — PANS-AIM (Aeronautical Information Management).
• Doc 10157 — PANS-Aerodromes.
• Doc 10199 — PANS Environmental Technical Manual / environmental procedures.

How it is read in this workspace. PANS are the second stop after the Annex. A topic answer that ends with the Annex citation is usually incomplete; the matching PANS gives the procedure detail ("how do we actually do separation, route a flight, build an approach, publish AIP data, run holding"). Citations follow the same chapter plus §paragraph style as the Annexes.

Block C — Doc series (the manuals block)#

What it is. Approximately one hundred and ten Doc-series publications spanning manuals, guidance material, performance methodology, planning frameworks, and consolidated technical references. Doc-series titles are not legally binding in the Annex sense; they are the authoritative explanatory layer that interprets, applies, and extends the Annexes and PANS.

Coverage highlights, grouped by theme.

• ATM, ATS, SAR. Doc 4444 (mirrored from the PANS block), Doc 7030 Regional Supplementary Procedures, Doc 9426 ATS Planning Manual, Doc 9433 SAR Manual, Doc 9574 RVSM, Doc 9613 PBN Manual, Doc 9689 Manual on Airspace Planning Methodology for the Determination of Separation Minima.
• Aerodromes. Doc 9157 Aerodrome Design Manual, Doc 9261 Heliport Manual, Doc 9476 SMGCS Manual, Doc 9830 A-SMGCS Manual.
• CNS. Doc 9694 Manual of ATS Data Link Applications, Doc 9750 GANP, Doc 9760 Airworthiness Manual, Doc 9871 Mode S Specific Services.
• Safety and SMS. Doc 9756 Manual of Aircraft Accident and Incident Investigation, Doc 9859 SMS Manual.
• Licensing and training. Doc 9379 Manual of Procedures for Establishment and Management of a State's Personnel Licensing System, Doc 9683 Human Factors Training Manual, Doc 8984 Manual of Civil Aviation Medicine.
• Security and facilitation. Doc 9303 Machine Readable Travel Documents.
• Charts, AIS, AIM. Doc 8126 AIS Manual, Doc 8697 Aeronautical Chart Manual.
• Performance, economics, planning. Doc 9082 Charges Policy, Doc 9587 Economic Regulation Policy, Doc 9626 Regulation of International Air Transport, Doc 9854 Global ATM Operational Concept, Doc 9883 Manual on Global Performance.

How it is read in this workspace. The Doc series is the third stop: after a topic has its Annex anchor and its PANS anchor, the Doc series provides the explanatory or planning context — the "why" and the "how to plan it".

How the three blocks fit together#

A complete answer to a typical topic question reaches into all three:

• Annex — the requirement.
• PANS — the procedure.
• Doc — the explanation, manual, or planning framework.

The three are not interchangeable. A topic note that cites only a Doc without resolving back to the Annex or PANS is operating on guidance alone and should be marked as such.

Cross-block dependencies#

Several documents bridge blocks. Examples:

• Doc 4444 is both a PANS publication (Block B) and a Doc-series publication (Block C); the local set keeps it primarily under PANS.
• Doc 8126 (AIS Manual, Block C) is the explanatory companion to Annex 15 (Block A) and Doc 10066 PANS-AIM (Block B).
• Doc 9613 (PBN Manual, Block C) is the explanatory companion to Annex 6 / Annex 10 / Annex 11 PBN provisions and Doc 8168 PANS-OPS procedure design.
• Doc 9750 (GANP, Block C) sits over the Annex / PANS pair and defines the planning framework (ASBU) by which States sequence Annex / PANS implementation.

Why this taxonomy matters#

When a topic note says "ICAO requires", the reader should be able to tell at a glance which block the citation is in. A citation into the Annex block is an obligation. A citation into PANS is an operational procedure. A citation into the Doc series is guidance. The three publication blocks are the simplest reliable carrier of that distinction.

What a thread is, here#

A thread is a subject area cutting across the Annex, PANS, and Doc publication blocks. Real topics rarely fall inside a single Annex; they draw on several Annexes plus their PANS plus the manuals that interpret them. The threads below are the practical groupings used when picking which files in the local set to search for a given topic.

CNS — Communications, Navigation, Surveillance#

Annex coverage. Annex 10 Volumes I to V (radio nav aids, communication procedures, communication systems, surveillance and ACAS, aeronautical radio frequency spectrum).

PANS coverage. Doc 4444 (PANS-ATM) data link operations chapters; Doc 8168 (PANS-OPS) for procedure design that depends on PBN.

Doc coverage. Doc 9613 PBN Manual; Doc 9694 ATS Data Link Applications Manual; Doc 9871 Mode S Specific Services; Doc 9849 GNSS Manual; Doc 9750 GANP for the technology threads.

Typical questions. PBN specifications, ADS-B carriage, CPDLC implementation, frequency planning, GNSS augmentation policy.

ATM — Air Traffic Management#

Annex coverage. Annex 11 (ATS) for service provision, airspace classification, ATFM, A-CDM-related coordination; Annex 2 (Rules of the Air) for the operating rules; Annex 13 where new occurrence categories arise from new ATM concepts.

PANS coverage. Doc 4444 (PANS-ATM) is the central reference; Doc 8168 (PANS-OPS) for procedure design touched by ATM concepts; Doc 7030 for regional supplementary procedures.

Doc coverage. Doc 9426 ATS Planning Manual; Doc 9574 RVSM Manual; Doc 9689 Airspace Planning Methodology for Separation Minima; Doc 9854 Global ATM Operational Concept; Doc 9883 Manual on Global Performance; Doc 9750 GANP.

Typical questions. Separation minima, free route airspace, ATFM, A-CDM, AMAN/DMAN, sector capacity, trajectory-based operations.

AIM — Aeronautical Information Management#

Annex coverage. Annex 15 (Aeronautical Information Services), and Annex 4 (Aeronautical Charts) for chart provisions.

PANS coverage. Doc 10066 (PANS-AIM) is the central reference for aeronautical data management procedures and the Aeronautical Data Catalogue.

Doc coverage. Doc 8126 (AIS Manual); Doc 8697 (Aeronautical Chart Manual); Doc 9750 GANP for the DAIM and SWIM linkage.

Typical questions. AIS-to-AIM transition, AIXM 5 data products, electronic AIP, terrain and obstacle data sets, charting requirements.

MET — Meteorology#

Annex coverage. Annex 3 (Meteorological Service for International Air Navigation).

PANS coverage. Doc 10157 (PANS-MET) for meteorological procedures; Doc 4444 for MET integration into ATS.

Doc coverage. WMO and ICAO joint guidance referenced under the GANP MET roadmap.

Typical questions. OPMET messages, IWXXM exchange model, SIGMET issuance, volcanic ash advisory, space weather, integration with TBO trajectory planning.

AGA — Aerodromes and Ground Aids#

Annex coverage. Annex 14 Volume I (aerodrome design and operations) and Volume II (heliports).

PANS coverage. Doc 10157 (PANS-Aerodromes) is the central PANS reference for aerodrome operational procedures.

Doc coverage. Doc 9157 Aerodrome Design Manual; Doc 9261 Heliport Manual; Doc 9476 SMGCS Manual; Doc 9830 A-SMGCS Manual.

Typical questions. Runway design, A-SMGCS levels, runway-incursion prevention, aerodrome certification, obstacle limitation surfaces, OLS and PANS-OPS surface interaction.

SAR — Search and Rescue#

Annex coverage. Annex 12 (Search and Rescue).

PANS coverage. SAR procedures cross-referenced from Doc 4444.

Doc coverage. Doc 9433 IAMSAR Manual.

Typical questions. SAR region definition, alerting service, SAR coordination centres, distress phases, cross-border SAR agreements.

ENV — Environment#

Annex coverage. Annex 16 Volume I (noise), Volume II (engine emissions), Volume III (aeroplane CO2), Volume IV (CORSIA).

PANS coverage. Doc 10199 PANS-Environmental Technical Manual / environmental procedures.

Doc coverage. ICAO environmental guidance material referenced from the GANP and from Annex 16 itself; Doc 9587 for the economic regulation interface.

Typical questions. CO2 standard application, CORSIA monitoring and reporting, noise certification, balanced approach to noise management.

SEC — Security and Facilitation#

Annex coverage. Annex 17 (Security) and Annex 9 (Facilitation).

PANS coverage. Security-relevant procedures embedded in Doc 4444 and Doc 10066 (data integrity and access control for AIM).

Doc coverage. Doc 9303 Machine Readable Travel Documents.

Typical questions. Aviation cybersecurity, screening, traveller identification, supply-chain security, cross-border data exchange governance.

How threads cross publication blocks#

A topic answer typically reaches into one Annex (Block A), one or two PANS (Block B), and two or three Doc-series titles (Block C) on the same thread. For example, a CDO design question pulls Annex 11, Doc 4444, Doc 8168, Doc 9613, and Doc 9854 — five files spanning three publication blocks but a single thread.

Why threads are useful for searching#

When sources_internal.md produces a search recipe for a topic, the thread is what tells the searcher which subset of the file set to search first. Searching for "free route airspace" should hit Annex 11, Doc 4444, and Doc 9750 first; not Annex 16 or Doc 9303. Threads keep the search scoped and the noise low.

What a "module" is, here#

In this folder, a module is a single consolidation file in the local set — for example one Annex volume, one PANS volume, or one Doc-series manual. Each module is the smallest publication unit a reader interacts with in day-to-day work. Knowing the anatomy of a module makes it easier to search efficiently, cite correctly, and recognise when a Markdown rendering has drifted from the source.

Purpose of a module#

A consolidation file presents an ICAO publication as currently amended at a defined date. The aim is that a reader can open one file and have a complete, contemporary view of the document without having to overlay successive amendment documents. The trade-off is that a consolidation is a snapshot — it is correct as of its consolidation date, not necessarily today.

Expected structure#

ICAO publications follow a recognisable structure. A consolidated Markdown rendering preserves that structure. Expected elements, in the order they normally appear:

Front matter#

• Foreword and amendment record.
• Table of contents.
• List of tables, figures, and appendices.
• List of acronyms and abbreviations.
• Editorial conventions used in the document.

The amendment record is important: it lists the amendment number, the date the amendment became applicable, and the parts of the document affected. When citing into a consolidation, recording the amendment state captured by the file is good practice.

Body chapters#

Numbered chapters at the document's first level (Chapter 1, Chapter 2, ...). Each chapter is divided into numbered paragraphs using ICAO's dotted decimal scheme: 2.1, 2.6, 2.6.1, 2.6.1.1. The dotted decimal is what citations key on (e.g. "Annex 11, Chapter 2, §2.6").

Within paragraphs, an ICAO publication uses recognisable typographical conventions:

• Standards — written in light type in Annexes; mandatory.
• Recommended Practices — written in italic type and prefixed "Recommendation"; advisory.
• Notes — explanatory; not part of the Standard or Recommendation.

Markdown conversion does not preserve italic-vs-roman cleanly in every case. When the standard / recommendation distinction matters for a citation, the PDF must be opened to confirm.

Appendices and attachments#

Appendices form part of the publication and carry the same legal weight as the body where the body explicitly so states. Attachments contain guidance material and do not have the same legal weight as the body text.

Tables and figures#

Tables are flattened into Markdown tables where possible, but multi-row header tables, merged cells, or rotated layouts may not survive intact. Figures are not preserved as images; placeholders or captions remain. For any table or figure that drives a decision, the PDF is the authority.

Amendment markers#

Consolidated ICAO publications mark amended text. The marker convention in the local Markdown depends on the source ICAO style. The two common ones are:

• A vertical bar | in the left margin of the printed page, which the Markdown conversion may render as a leading character, a separate line, or simply lose, depending on the conversion settings.
• An "Amendment " label at the bottom of a page, retained as a line in Markdown.

Treat marker survival as best-effort. To establish whether a paragraph was amended, check the amendment record in the front matter and, if needed, the PDF. The Markdown is for finding text, not for forensic amendment analysis.

Signposts inside the text#

Several signposts make a consolidation file easier to navigate even at length:

• Definitions — a numbered Definitions section near the start, in which technical terms are introduced in italics. Searching a definition is the fastest way to confirm whether an ICAO publication uses a term in a specific way.
• Cross-references — a paragraph often references another paragraph in the same document (see 4.2.3.1) or another publication (see Doc 4444, Chapter 5). Cross-references are preserved as text but not as live links.
• Notes — explicitly labelled "Note" or "Note.—". Notes are authoritative explanation but are not Standards.
• Recommendations — labelled "Recommendation" in some publications and italicised in Annexes.

How to search a module efficiently#

1. Search for definitions first when a term is at issue. The definitions section pins the meaning the publication assumes.
2. When looking for an obligation, search for the technical term plus "shall" — Standards in Annexes use "shall"; Recommendations use "should".
3. When looking for a procedure, search the PANS document on the same thread, not the Annex.
4. When looking for explanation, search the Doc-series manual on the same thread.

When the Markdown disagrees with the PDF#

Always trust the PDF. The Markdown is a search index over the PDF. Conversion artefacts to watch for:

• Headers and footers leaking into body text.
• Page numbers appearing mid-paragraph.
• Soft line breaks fragmenting a sentence across two lines.
• Multi-column pages flattened with column boundaries lost.
• Footnotes attached to the wrong paragraph.

For citations and quotations, copy from the PDF. For navigation, search the Markdown.

Why modules are kept whole#

It would be possible to split each consolidation into per-chapter files. This is deliberately not done. A whole-document module:

• Preserves cross-reference resolution within one file.
• Lets a single search hit return its full surrounding context.
• Matches the unit ICAO actually publishes and amends.
• Keeps line numbers stable across the document until the next consolidation.

Stable line numbers are what allow internal anchors elsewhere in this workspace to point reliably at a specific paragraph.

What an enabler is, here#

An enabler is a supporting process or convention that makes the local ICAO file set usable for day-to-day reference work. The set is not just a pile of PDFs; it is a small ecosystem of pipeline, conventions, and integration points. Three enablers matter most: the PDF-to-Markdown conversion pipeline, the search workflow, and the integration with the per-topic source map.

1. Conversion pipeline (PDF to Markdown)#

Inputs#

• Original ICAO PDFs as published, kept read-only.
• A consolidated edition for each Annex, PANS, or Doc, where ICAO publishes one. Where ICAO publishes only base plus amendment documents, the local snapshot keeps the published edition as is.

Stages#

1. Acquisition. Each PDF is fetched from an authorised channel (ICAO Online Store or ICAO-NET) and recorded in the download manifest with date, language, and identifier.
2. Text extraction. The PDF is parsed for its text layer where one exists. Scanned-only pages, where present, fall back to OCR.
3. Structural reconstruction. Heading hierarchy is recovered from font size and weight cues; paragraphs are reflowed; lists are detected; tables are emitted as Markdown tables where the layout allows; figures are kept as captions only.
4. Normalisation. Page headers, page numbers, and footers are removed where they would otherwise litter the body. Soft line breaks within paragraphs are joined.
5. Emission. The Markdown file is written to the matching subfolder under the Markdown layer, with a filename that mirrors the PDF and adds the suffixes documented in components.md.

Outputs and side products#

• The Markdown file itself.
• An entry in the download manifest indicating provenance.
• (Optionally) a conversion log capturing pages with low confidence, used during quality review.

Known limitations#

• Tables with merged cells, rotated layouts, or multi-row headers may not render usefully.
• Figures are not preserved as images.
• The standard / recommendation typographic distinction is partially lost.
• Footnotes may attach to the wrong anchor paragraph.
• Multi-column pages are flattened to a single column and a column break may slice a sentence in half.

These limitations are why the PDF remains the authority for citation and the Markdown is treated strictly as a search index.

2. Search workflow#

The intended workflow has four steps:

1. Scope. Use the topic's thread (CNS, ATM, AIM, MET, AGA, SAR, ENV, SEC) to decide which Annex, PANS, and Doc files are likely relevant. The threads documented in threads.md give the default scoping.
2. Search Markdown. Run a case-insensitive text search across the relevant subfolder of the Markdown layer and capture line numbers for the strongest hits.
3. Open the PDF. For each hit that looks promising, open the matching PDF at the corresponding chapter and confirm the wording.
4. Cite from the PDF. When committing a citation to a topic note, quote from the PDF and cite the chapter and paragraph (§paragraph), not the Markdown line number. Line numbers are internal anchors only.

Search returns are most useful when narrowed by thread first. A broad search across the whole Markdown layer is fast but produces noise; a targeted search inside Annex 11 plus Doc 4444 plus Doc 9750 for an ATM question is short and precise.

3. Integration with the per-topic source map#

The workspace keeps a per-topic source map — sources_internal.md at the top of this repository — that lists, for each topic, the search queries which produce its anchors against the local file set. The source map is the bridge between this folder (which describes the file set abstractly) and the per-topic working notes (which carry the actual anchors).

How the integration works:

• Every topic in this workspace has an entry in sources_internal.md.
• That entry lists the terms to search for, scoped to the publication blocks that the topic's thread points at.
• Running the searches re-derives the line-number anchors against the current snapshot.
• When the snapshot is refreshed, line numbers may shift; the search recipe is what makes refresh deterministic.

The published topic files in topics/ do not depend on line numbers; they cite Annex / PANS / Doc, chapter, and §paragraph only. The working topic files in topic/ carry the line-number anchors that are re-derivable from the search recipes.

4. Read-only discipline#

The local set is treated as read-only. Edits to Markdown content would silently desynchronise it from the PDF. Two consequences follow:

• No fixes are made to conversion artefacts in the Markdown layer itself; if a paragraph reads badly, the answer is to open the PDF.
• The set is replaced wholesale at refresh, not patched.

5. Cross-reference manifest#

The download manifest is the cross-reference for opaque four-digit Doc filenames. Looking up a number in the manifest returns:

• The publication's full title.
• The edition or amendment level captured.
• The language of the file.
• The fetch date.

This is the only enabler that lets the bare-number Doc filenames in the Doc series be navigated without prior knowledge of every Doc number ICAO has ever issued.

6. Refresh process (planned)#

Refresh of the local set is event-driven, not on a fixed cadence. A refresh cycle is triggered when:

• A major amendment is announced for a publication that drives several topics in the workspace.
• A new ICAO publication enters the working set of topics covered.
• Pipeline improvements (better table extraction, for example) justify a re-run of the conversion stage.

A refresh produces a new snapshot folder with its own date suffix. Topic working notes that depend on line numbers are refreshed against the new snapshot using the search recipes in sources_internal.md.

The performance lens for a reference corpus#

The ASBU framework applies a performance lens to operational capabilities. The same lens is useful for the local ICAO file set: a reference corpus is fit for purpose only if its quality, coverage, freshness, and searchability meet defined objectives.

The chain, adapted for a corpus:

Quality Area --(measured by)--> Indicator <--(targeted by)-- Objective --(achieved by)--> Pipeline / convention

Quality areas#

The four quality areas tracked for the local set are:

1. Completeness — does the set cover the publications a topic actually needs?
2. Freshness — how close is each file to the current ICAO edition and amendment level?
3. Accuracy — does the Markdown rendering correctly reflect the PDF source?
4. Searchability — can a topic question be answered from the set in reasonable time, with a citable result?

Each area has its own objectives and indicators.

Objective 1 — Coverage of the working topics#

Statement. Every topic listed in topics.md must have at least one Annex, one PANS, and one Doc-series anchor available in the local set.

Indicators.

• Number of topics with at least one anchor in each publication block.
• Number of topics whose working notes rely solely on the Doc series (an under-anchored topic).
• Number of topics whose sources_internal.md recipe returns zero hits against the current snapshot.

Achieved by. Curation of the file set when a new topic is added, checking the topic's thread (threads.md) and confirming the relevant Annex, PANS, and Doc are present. Where a needed publication is missing, an entry in the missing-publications list flags it for the next refresh cycle.

Objective 2 — Coverage breadth#

Statement. Across the 24 topics, the set covers the ICAO publication families that any aviation reference workspace would expect: all 19 Annexes; the principal PANS; the GANP and the manuals that interpret operational improvements.

Indicators.

• Number of Annex volumes / parts present (target: every published volume of Annexes 1 to 19).
• Number of principal PANS publications present (target: every PANS document currently in force).
• Number of Doc-series titles present (the working subset; growth is acceptable).

Achieved by. Maintaining the snapshot against the ICAO catalogue on each refresh cycle, with the download manifest as the audit trail.

Objective 3 — Freshness#

Statement. The Markdown layer must reflect the consolidated state of each publication at the snapshot's declared date.

Indicators.

• Snapshot date recorded in the snapshot folder name.
• Date of the most recent ICAO amendment captured in each file's amendment record.
• Time since the last refresh.

Achieved by. Consolidated editions are sourced where ICAO publishes them; non-consolidated publications are sourced as base plus applicable amendments and consolidated locally.

Trade-offs. A reference corpus is always slightly behind the authoritative ICAO source. The acceptable lag is bounded by:

• The pace at which ICAO publishes the consolidations themselves.
• The cadence of the local refresh cycle.

For any citation that will be used outside the workspace, the current ICAO edition must be checked.

Objective 4 — Accuracy of conversion#

Statement. The Markdown rendering preserves heading hierarchy, paragraph structure, list structure, and as much table structure as the source layout allows.

Indicators.

• Sampled paragraph match rate against the PDF (manual spot-check on refresh).
• Number of files flagged with low-confidence conversion regions in the conversion log.
• Number of corrections made on quality review (target: zero — the Markdown is regenerated, not edited).

Achieved by. A read-only discipline on the Markdown layer; the PDF is the authority for citation; conversion improvements are folded into the next pipeline run, not into the Markdown files.

Objective 5 — Searchability#

Statement. Any topic covered in the workspace must be answerable from the local set in a few minutes by a reader who knows the topic's thread.

Indicators.

• Median time from topic question to first usable anchor.
• Proportion of sources_internal.md recipes that return a usable hit on first run.
• Number of topics whose anchors point at the wrong paragraph (to be driven to zero on refresh).

Achieved by. Stable filenames, line-numbered Markdown, scoped search recipes per topic, and the thread taxonomy in threads.md.

Objective 6 — Citability#

Statement. Every citation produced from the workspace can be re-resolved, by a reader without access to the local set, against the authoritative ICAO publication.

Indicators.

• Proportion of citations using the formal "Annex / PANS / Doc, chapter, §paragraph" style.
• Proportion of citations that survive a refresh of the local set (target: 100%, because chapter and paragraph numbers do not move between editions except on amendment).

Achieved by. A documented convention (see modules.md) that chapter and paragraph numbers are the citable unit, not line numbers.

How these objectives interact#

Coverage and freshness pull in opposite directions: every additional publication brought into the set increases the maintenance burden at each refresh. The trade-off is managed by keeping the Doc-series scope tied to the working topics rather than to ICAO's full Doc catalogue. A Doc that no current topic cites does not need to be in the set, and adding it would dilute freshness without adding value.

Why this matters#

A reference corpus that is incomplete, stale, or unsearchable will be worked around — by guessing, by quoting from memory, or by reaching straight for the open web. Each of those failure modes leads to topic notes that are harder to verify and harder to maintain. The objectives above exist to keep the local set on the path of least resistance, so that working from the corpus is always easier than working around it.

Three timelines to keep distinct#

When discussing dates around the local ICAO file set, three different timelines are at play and must not be confused:

1. ICAO publication timeline — when ICAO published an edition or amendment of a given Annex, PANS, or Doc.
2. Local snapshot timeline — when this workspace fetched and consolidated its working copy.
3. Topic working timeline — when a particular topic note in this repository was last reconciled against the local set.

A snapshot date is not an ICAO publication date. A topic note's "last reviewed" date is not a snapshot date. Mixing these leads to false claims that a topic is "out of date".

ICAO publication timeline (in outline)#

ICAO does not publish all titles on a single cadence. The cadences relevant to this set are:

• Annexes. Amendments are issued as the Air Navigation Commission proposes them and the Council approves them. A new amendment becomes applicable on a notified date, after an objection window. Major Annexes (10, 11, 14, 15) typically see one amendment every one to three years.
• PANS. Amended on a similar cadence to the related Annexes. Doc 4444 (PANS-ATM) and Doc 8168 (PANS-OPS) see frequent amendments driven by operational evolution.
• Doc series. Manuals are revised on a per-document basis, often with multi-year gaps. The GANP (Doc 9750) is on a roughly three-year edition cadence aligned with the ICAO Assembly. Some manuals (for example Doc 9303) have multi-volume parts on independent cadences.

The authoritative publication state at any given date is held at ICAO, not in this workspace.

Local snapshot — April 2026#

The current local set is the April 2026 snapshot. This is the date captured in the snapshot folder name and recorded in the download manifest. It identifies:

• Which ICAO consolidated editions were available at fetch time.
• Which amendment level each publication had reached.
• The state of the Markdown conversion pipeline used to render the PDFs.

The April 2026 snapshot is a single coherent set: every file in it reflects the state of its source publication on or before the snapshot date. A user who wants to know "what did ICAO say in April 2026" can read this set and get a consistent answer.

Visualised#

ICAO ----> Annex amendments and Doc revisions arrive continuously
             |
             |        snapshot cycle
             v
Local set ---*------------------*------------------*--->
             ^                  ^                  ^
             |                  |                  |
             Apr 2026           next snapshot      future snapshot
             (current)
             |
             |        topic note reviews
             v
Topic notes -*--*--*---*-*--*-----*-*------*----->

Refresh policy#

Refresh is event-driven rather than fixed-cadence:

• A refresh is triggered when a major amendment is announced for a publication that drives several topics in the workspace, when a new publication enters the working scope, or when the conversion pipeline gets a meaningful improvement.
• A refresh produces a new snapshot in its own folder named for the fetch date.
• The previous snapshot is retained until the new one has been used to re-derive every topic anchor; only then is the previous snapshot archived.
• Topic working notes are reconciled against the new snapshot using the search recipes in sources_internal.md. Citations in the published topic files do not need to change unless the underlying ICAO chapter or paragraph numbering moved.

Indicative refresh checkpoints#

The expected refresh checkpoints, expressed as the events that would trigger a new snapshot rather than as fixed dates:

• Publication of a new GANP edition (Doc 9750), because the planning framework above ASBU is itself a working topic.
• A major Annex 10, 11, 14, or 15 amendment relevant to current topics.
• Publication of a new PANS-ATM (Doc 4444) or PANS-AIM (Doc 10066) edition.
• Pipeline upgrades that materially improve table extraction or amendment-marker preservation.

What the snapshot date does not tell you#

The snapshot date does not tell you:

• The applicable amendment number of any single publication. That is recorded inside each file's amendment register.
• Which topics have been reviewed since the snapshot. That is held in the topic working notes themselves.
• Whether any newer amendment has been issued by ICAO since the snapshot. That must be checked against the ICAO publications portal.

How to read a date in this workspace#

When a date appears in topic notes or in this folder, identify which of the three timelines it belongs to:

• "ICAO-Apr-26" or "April 2026 snapshot" — local snapshot timeline.
• "Amendment 53 (applicable 2025-11-26)" — ICAO publication timeline.
• "Topic note last reviewed 2026-05" — topic working timeline.

Mixing these will produce statements that look meaningful and are not. The discipline is to name the timeline whenever a date is quoted.

Why the corpus is always slightly behind ICAO#

The authoritative source moves continuously. A reference corpus is necessarily a snapshot. The gap is bounded by the refresh policy above, and any citation that needs to be currency-correct must be checked against the ICAO publications portal at the time of use, not only against the local set.

Authoritative publications (the things the local set is a working copy of)#

• Convention on International Civil Aviation (Doc 7300) — Articles 37 and 54(l). Article 37 obliges Contracting States to collaborate in securing the highest practicable degree of uniformity in regulations, standards, procedures, and organisation; Article 54(l) empowers the ICAO Council to adopt international Standards and Recommended Practices (Annexes).
• ICAO Annexes 1 to 19. Standards And Recommended Practices, attached to the Convention. The local set covers every Annex, with multi-volume Annexes (Annex 6, Annex 10, Annex 14, Annex 16) split into their published volumes and parts.
• PANS publications. Doc 4444 (PANS-ATM), Doc 8168 (PANS-OPS), Doc 8400 (PANS-ABC), Doc 9868 (PANS-Training), Doc 10066 (PANS-AIM), Doc 10157 (PANS-Aerodromes), Doc 10199 (PANS-Environmental Technical Manual / environmental procedures).
• Selected Doc-series titles referenced repeatedly across the workspace topics: Doc 7030 (Regional Supplementary Procedures), Doc 8126 (AIS Manual), Doc 8697 (Aeronautical Chart Manual), Doc 9082 (Charges Policy), Doc 9157 (Aerodrome Design Manual), Doc 9303 (Machine Readable Travel Documents), Doc 9426 (ATS Planning Manual), Doc 9433 (IAMSAR Manual), Doc 9476 (SMGCS Manual), Doc 9587 (Economic Regulation Policy), Doc 9613 (PBN Manual), Doc 9626 (Regulation of International Air Transport), Doc 9683 (Human Factors Training Manual), Doc 9694 (ATS Data Link Applications Manual), Doc 9750 (Global Air Navigation Plan), Doc 9756 (Manual of Aircraft Accident and Incident Investigation), Doc 9830 (A-SMGCS Manual), Doc 9854 (Global ATM Operational Concept), Doc 9859 (Safety Management Manual), Doc 9871 (Mode S Specific Services), Doc 9883 (Manual on Global Performance of the Air Navigation System).

Governance of ICAO publications#

• ICAO Doc 8143 — Directives to Divisional-type Air Navigation Meetings. Describes the formal route by which SARPs and PANS are drafted, reviewed, and amended.
• ICAO Doc 10184 — Assembly Resolutions in Force. Consolidated policy framework agreed by Contracting States; sets the strategic direction the publications implement.
• ICAO Doc 7984 — Working Arrangements between ICAO and other international bodies (relevant where ICAO publications are developed jointly with WMO, IMO, ITU, and others).

Live / authoritative sources#

• ICAO Online Store — https://store.icao.int/ Authoritative editions and amendments for purchase. Use this for anything that will be cited outside the workspace.
• ICAO-NET (subscription portal) — https://portal.icao.int/ For Contracting States and approved users; full electronic library.
• ICAO public site — https://www.icao.int/ Free guidance and topical hubs (GANP, CORSIA, safety / SMS pages).
• ICAO Air Navigation Commission and Council pages — https://www.icao.int/about-icao/AirNavigationCommission/Pages/default.aspx Source of amendment proposals and adoption records.
• ICAO publications catalogue — https://www.icao.int/publications/Pages/catalogue.aspx Mapping of Doc numbers to titles; useful when a Doc number is encountered without context.

Regional and bridging references#

• APAC region. ICAO Asia/Pacific Office documentation portal — https://www.icao.int/APAC — for the APAC Seamless ATM Plan and APANPIRG documentation; the regional realisation of ICAO publications for the Asia and Pacific States.
• MID region. ICAO Middle East Office — https://www.icao.int/MID — for the MID Air Navigation Strategy and MIDANPIRG documentation.
• EUR/NAT. ICAO European and North Atlantic Office — https://www.icao.int/EURNAT — and the EUROCONTROL specifications cross-referenced from the European ATM Master Plan, where they bridge into ICAO publications.

Standards bridging into ICAO#

Where ICAO publications point at industry standards, the bridges are:

• RTCA — https://www.rtca.org/ — Minimum Operational Performance Standards (MOPS) referenced from Annex 10.
• EUROCAE — https://www.eurocae.net/ — European MOPS counterparts.
• WMO — https://public.wmo.int/ — joint ICAO/WMO publications on meteorology (Annex 3 / Doc 10157).
• ITU — https://www.itu.int/ — radio frequency spectrum standards referenced from Annex 10 Volume V.

Reminder on the status of the local set#

The local file set is a working copy, not an authoritative publication. Three consequences follow:

• For citation outside this workspace, the authoritative ICAO edition must be checked. The local set is the search index, not the source.
• The local set may lag the latest ICAO amendments by the period between the most recent snapshot and today.
• The local set is not redistributed. It exists for in-workspace reference work only.

When in doubt, the resolution path is: search the local Markdown, confirm against the local PDF, then re-confirm against the ICAO publications portal entry for the cited edition and amendment level.

How citations are written in this workspace#

The published topic files in topics/ use the formal ICAO citation style:

• Annex. "Annex 11 (Air Traffic Services), Chapter 2, §2.6 — short note."
• PANS. "Doc 4444 (PANS-ATM), Chapter 5, §5.4.1 — short note."
• Doc. "Doc 9750 (Global Air Navigation Plan), Part II — short note."

Where a referenced source is not in the local working set, the citation is appended with "(authoritative source — not in local library)" so that the reader knows to reach for the ICAO portal directly.