Exhaustiveness ledger
Coverage
Per cycle: exactly what we decode from the free FAA CIFP, and exactly what we do not — enumerated, gated, and on the decode backlog.
“Advisory” means exactly one thing: this is not a legal / certified navigation source. It means nothing else.
It is not a license for missing, wrong, or unrendered data. A silent gap is a defect of the same severity as a wrong value. Every known gap below is enumerated, gated so it cannot grow or appear silently, and on a prioritized decode backlog.
Total records
396,430
Claimed (decoded)
100.0%
396,425 records
Unclaimed (backlog)
0
0.0% of cycle
Unclaimed record classes
| Class | Description | Records | Backlog |
|---|
5 leading header records + 396,425 claimed + 0 unclaimed = 396,430 tiled records. This set is gated: a new record class in a future cycle refuses to publish until it is enumerated here.
Per-family span accounting (of 132 bytes)
| Family | Records | Decoded | Raw | Filler | Coverage |
|---|---|---|---|---|---|
| procedure_legs | 207,856 | 51 | 73 | 8 | |
| terminal_waypoints | 37,635 | 71 | 11 | 50 | |
| enroute_waypoints | 32,401 | 69 | 13 | 50 | |
| restrictive_airspace | 29,994 | 97 | 32 | 3 | |
| airway_legs | 19,099 | 27 | 65 | 40 | |
| runways | 16,805 | 76 | 10 | 46 | |
| airports | 13,321 | 94 | 10 | 28 | |
| controlled_airspace | 13,135 | 97 | 32 | 3 | |
| path_points | 9,810 | 56 | 76 | 0 | |
| heliports | 6,134 | 94 | 17 | 21 | |
| msas | 6,050 | 86 | 24 | 22 | |
| navaids | 2,475 | 97 | 30 | 5 | |
| localizers | 1,280 | 78 | 29 | 25 | |
| grid_moras | 241 | 106 | 6 | 20 | |
| terminal_ndbs | 189 | 79 | 16 | 37 |
“Decoded” bytes are parsed through a codec; “Raw” bytes are conserved verbatim but not yet interpreted (an in-family decode backlog); “Filler” bytes are spec-blank. Counts are derived mechanically from the committed span tables.
coverage config SHA-256 488f05d1c5278fefded8bd736cad1ece3af47a8a9bc5c9461a99629bb0bb9969
What we deliberately do not decode — and why
Every record in the FAA CIFP is now claimed by meaning, and the decode of each family has run to its principled frontier. The bytes that stay “raw” above are not a backlog — they are here by design, and there are exactly two kinds.
| Undecoded field | Why it stays raw |
|---|---|
| Navaid class flags (VOR/DME/TACAN) | A bit-packed class field. The free FAA CIFP coding legend does not publish the packing, so we conserve the bytes rather than invent a decode. |
| NDB navaid class flags | The NDB equivalent of the above — the same packed-flag byte block, unmapped by any free source. |
| Runway description code | A coded runway-description field whose value set is defined only in the licensed spec; conserved verbatim. |
| Localizer glideslope support block | The glideslope support/positioning sub-block sits behind the licensed spec. We DO decode the GS angle, position, and station declination (see any ILS airport); this residual block we do not. |
| FAS (final-approach segment) data block tail | The LPV/FAS tail interleaves TCH / HAL / VAL with a CRC and cannot be honestly sub-divided without the licensed FAS spec. We DO decode the path-point GPA and threshold ellipsoid height; this CRC-bearing tail we conserve as-is. |
The other raw bytes are structural: record-type, section/subsection, and identifier bytes that locate a record rather than carry a navigation value — conserved verbatim so every datum traces to its exact source bytes, but nothing to “decode.” These five data residues are principled: honestly decoding them needs licensed specifications that our free-only sourcing rule (D-001) forbids us to use, so we conserve the bytes rather than guess.
Advisory / planning only · AIRAC cycle 2607 · not a certified navigation source.