Procedures & airways procedures-conus · 2611

federal · procedures · effective 2026-10-29 to 2026-11-26 · in the live catalog · history

Experimental / Amateur-Built use only. Not certified. This data is provided as-is with no warranty and any use of the data is at your own risk.

Checks

pass 13 warn 1 fail 4 not run 3

not run PACK-004 Upstream sources are recorded: Retro record: this edition was published before pack-report/1 existed, and the upstream inputs it was built from were not recorded then and cannot be recovered from the pack.
warn ROW-002 Row counts against the previous edition: largest change: airways -17.3% (1,504 -> 1,244) — no build note recorded
fail PROC-MSA-001 Every PS record in the source file is in the msa table: no msa table
fail PROC-MSA-002 Each MSA's sectors cover 360 degrees with no gap or overlap: no msa table
fail PROC-MSA-003 MSA altitudes, radii and bearing references are plausible: no msa table
fail PROC-MSA-004 MSA centre fixes the build could not place: no msa table
not run PROC-GLD-001 FAACIFP18 golden fixture: The golden fixture runs in the unit tests against the parser (tests/test_build_procedures.py), not against a built pack. Catalogue v2 (TV7) moves it here.
not run PROC-DIFF-001 Independent differential against a commercial database: Not yet run (AER-1702). Until it is, nothing independent of the FAA source has been compared against this pack's procedures.

record is retro, not build: only a build record can clear the gate
ROW-002 warns with no build note: largest change: airways -17.3% (1,504 -> 1,244)

Show: pass warn fail not run

	Check	What it checks	Measured	Expected	Cannot catch
fail	PROC-MSA-001	Every PS record in the source file is in the msa table	no msa table	as many MSA records (and continuation records) in the pack as PS records in the source FAACIFP18	A record that is present but decoded wrong; PROC-MSA-002 and -003 look for that.	since AER-4446
fail	PROC-MSA-002	Each MSA's sectors cover 360 degrees with no gap or overlap	no msa table	0 records: every sector ends where the next begins, the last closes on the first, and together they span 360 degrees (one sector: start equals end)	A consistent set of sectors with the wrong altitude in one of them, and a column shift that keeps the bearings contiguous.	since AER-4446
fail	PROC-MSA-003	MSA altitudes, radii and bearing references are plausible	no msa table	altitudes 1,000-20,000 ft, radii 10-50 nm, bearings referenced M or T	A wrong value inside the bounds, such as 5200 coded where the plate says 5900.	since AER-4446
fail	PROC-MSA-004 non-blocking	MSA centre fixes the build could not place	no msa table	at most 0.1% of MSA records, every one listed: a regression bound that carries forward the 1 of 6,058 observed in 2611 (KHRJ HQT, an NDB the file does not define). It does not accept those records as correct; they are stored with no position, never a guessed one	A centre placed at the wrong coordinates.	since AER-4446
warn	ROW-002 non-blocking	Row counts against the previous edition	largest change: airways -17.3% (1,504 -> 1,244)	Provisional threshold: no table moves more than 10%; a larger move needs a build note	A change that keeps counts steady (rows replaced by wrong rows), any defect already present in the previous edition, and a loss under the threshold (for obstacles at 10%, about 65,000 rows).	No build note recorded.
not run	PACK-004 non-blocking	Upstream sources are recorded	—	at least one source, each with a non-empty edition and a 64-hex sha256	A recorded source that is not the one the build actually used, and an edition or sha256 that is well formed but wrong.	Note: Retro record: this edition was published before pack-report/1 existed, and the upstream inputs it was built from were not recorded then and cannot be recovered from the pack.
not run	PROC-GLD-001 non-blocking	FAACIFP18 golden fixture	—	the fixture's procedures decode to their published legs	Everything outside the fixture's handful of procedures.	Note: The golden fixture runs in the unit tests against the parser (tests/test_build_procedures.py), not against a built pack. Catalogue v2 (TV7) moves it here.
not run	PROC-DIFF-001 non-blocking	Independent differential against a commercial database	—	no unexplained differences	Errors that both databases share.	Note: Not yet run (AER-1702). Until it is, nothing independent of the FAA source has been compared against this pack's procedures.
pass	PACK-001	pack_meta is readable and names a known kind	id=procedures-conus kind=procedures cycle=2611 schema_version=1	pack_meta present; kind is one the device knows	A pack_meta that is well formed but names the wrong id or cycle for the bytes inside.
pass	PACK-002	Attribution and license are recorded in pack_meta	attribution and license present	both non-empty	A license tag or attribution that is present but wrong for the data.
pass	PACK-003	Origin label is federal, community or user-supplied	federal (defaulted by kind procedures, not read from the pack)	one of federal / community / user-supplied	Whether the label matches where the data really came from. For a kind with a default label (ORIGIN_BY_KIND in packtools/report.py) the label comes from that table, not from the builder or the pack, so the check is tautological and always passes; measured says which. With --origin it shows only that the label given is one of the three.	since AER-699
pass	ACC-001	Device acceptance: pyEfis's own reader opens the pack and answers a fixed query set	opened; 3/3 queries returned data	the reader opens the pack and every query returns data	Wrong values the reader accepts. It shows the device can open and query these bytes, not that what it returns is right. The queries cover fixed points only: US kinds, 5 CONUS metros (Denver, Seattle, Atlanta, Los Angeles and Chicago); airports (Canada), Toronto and Vancouver; water, Puget Sound, Lake Michigan and Lake Ontario; navaids, idents DEN, SEA, LAX; procedures, airways V23, J80, V1; terrain, one native tile or the coarsest mosaic level. So it cannot catch a missing Alaska, Hawaii or Puerto Rico, or any state or province that holds none of those points.
pass	SQL-001	SQLite structure is sound (PRAGMA quick_check)	ok	ok	Wrong data in a structurally sound file, and an index whose contents do not match its table: quick_check does not verify index contents, which is SQLite's documented difference from integrity_check. IDX-001 covers the R-trees.
pass	ROW-001	No data table is empty	0	0 empty tables, apart from those declared empty by design for the kind (water: waterway_lines)	A table that has rows but is missing most of them.
pass	ROW-003	No table of the previous edition has disappeared	0 of 5 tables gone	every table in the previous edition is still present, unless schema_version changed	A table dropped together with a schema_version bump that should not have been; the bump is taken as the declaration that the drop is intended.	since AER-4102
pass	GEO-001	Coordinates are present, valid and not at 0,0	0	0 bad coordinates. On point tables a NULL latitude or longitude is bad; on procedure and airway legs a leg with no fix position is left to PROC-FIX-001	A plausible coordinate in the wrong place, such as a transposed digit that still lands on land. On airway_legs, a leg with a NULL fix position (no check counts those).
pass	UNQ-001	Identifiers that must be unique are unique	procedures(airport, kind, ident) 0	0 duplicates	Two different things given the same correct-looking identifier in different tables, and a wrong identifier that happens to be unique.
pass	GEO-002 non-blocking	Points outside the US coverage envelope, against the previous edition	641 (previous 1,007)	Provisional threshold: no growth beyond 25 points or 10%, whichever is larger. FAA files carry real oceanic and foreign points, so the count is tracked, not forbidden	A point moved to the wrong place inside the envelope; the envelope is a handful of boxes, not a coastline.
pass	PROC-FIX-001 non-blocking	Procedure legs that name a fix the build could not place	941 of 200,853 legs (0.47%)	at most 0.5% of legs: a regression bound that carries forward the 0.47% observed in 2610 (950 of 201,030) and 2611 (941 of 200,853). It does not accept those legs as correct; it stops the share growing	A fix placed at the wrong coordinates. Legs with no fix by design (for example heading legs) are not counted.
pass	PROC-AWY-001	Airway idents are unique	0 duplicate idents; unique index present	0 duplicate idents	Two areas' airways merged under one ident row; PROC-AWY-002 looks for that.	since AER-1979
pass	PROC-AWY-002	No airway mixes legs from two areas (repeated sequence numbers)	0	0 airways	Two areas' legs merged with sequence numbers that do not collide, and an airway whose legs are all present but in the wrong order.	since AER-1979

Check

What it checks

Measured

Expected

Cannot catch

fail

PROC-MSA-001

Every PS record in the source file is in the msa table

no msa table

as many MSA records (and continuation records) in the pack as PS records in the source FAACIFP18

A record that is present but decoded wrong; PROC-MSA-002 and -003 look for that.

since AER-4446

fail

PROC-MSA-002

Each MSA's sectors cover 360 degrees with no gap or overlap

no msa table

0 records: every sector ends where the next begins, the last closes on the first, and together they span 360 degrees (one sector: start equals end)

A consistent set of sectors with the wrong altitude in one of them, and a column shift that keeps the bearings contiguous.

since AER-4446

fail

PROC-MSA-003

MSA altitudes, radii and bearing references are plausible

no msa table

altitudes 1,000-20,000 ft, radii 10-50 nm, bearings referenced M or T

A wrong value inside the bounds, such as 5200 coded where the plate says 5900.

since AER-4446

fail

PROC-MSA-004
non-blocking

MSA centre fixes the build could not place

no msa table

at most 0.1% of MSA records, every one listed: a regression bound that carries forward the 1 of 6,058 observed in 2611 (KHRJ HQT, an NDB the file does not define). It does not accept those records as correct; they are stored with no position, never a guessed one

A centre placed at the wrong coordinates.

since AER-4446

warn

ROW-002
non-blocking

Row counts against the previous edition

largest change: airways -17.3% (1,504 -> 1,244)

Provisional threshold: no table moves more than 10%; a larger move needs a build note

A change that keeps counts steady (rows replaced by wrong rows), any defect already present in the previous edition, and a loss under the threshold (for obstacles at 10%, about 65,000 rows).

No build note recorded.

not run

PACK-004
non-blocking

Upstream sources are recorded

—

at least one source, each with a non-empty edition and a 64-hex sha256

A recorded source that is not the one the build actually used, and an edition or sha256 that is well formed but wrong.

Note: Retro record: this edition was published before pack-report/1 existed, and the upstream inputs it was built from were not recorded then and cannot be recovered from the pack.

not run

PROC-GLD-001
non-blocking

FAACIFP18 golden fixture

—

the fixture's procedures decode to their published legs

Everything outside the fixture's handful of procedures.

Note: The golden fixture runs in the unit tests against the parser (tests/test_build_procedures.py), not against a built pack. Catalogue v2 (TV7) moves it here.

not run

PROC-DIFF-001
non-blocking

Independent differential against a commercial database

—

no unexplained differences

Errors that both databases share.

Note: Not yet run (AER-1702). Until it is, nothing independent of the FAA source has been compared against this pack's procedures.

pass

PACK-001

pack_meta is readable and names a known kind

id=procedures-conus kind=procedures cycle=2611 schema_version=1

pack_meta present; kind is one the device knows

A pack_meta that is well formed but names the wrong id or cycle for the bytes inside.

pass

PACK-002

Attribution and license are recorded in pack_meta

attribution and license present

both non-empty

A license tag or attribution that is present but wrong for the data.

pass

PACK-003

Origin label is federal, community or user-supplied

federal (defaulted by kind procedures, not read from the pack)

one of federal / community / user-supplied

Whether the label matches where the data really came from. For a kind with a default label (ORIGIN_BY_KIND in packtools/report.py) the label comes from that table, not from the builder or the pack, so the check is tautological and always passes; measured says which. With --origin it shows only that the label given is one of the three.

since AER-699

pass

ACC-001

Device acceptance: pyEfis's own reader opens the pack and answers a fixed query set

opened; 3/3 queries returned data

the reader opens the pack and every query returns data

Wrong values the reader accepts. It shows the device can open and query these bytes, not that what it returns is right. The queries cover fixed points only: US kinds, 5 CONUS metros (Denver, Seattle, Atlanta, Los Angeles and Chicago); airports (Canada), Toronto and Vancouver; water, Puget Sound, Lake Michigan and Lake Ontario; navaids, idents DEN, SEA, LAX; procedures, airways V23, J80, V1; terrain, one native tile or the coarsest mosaic level. So it cannot catch a missing Alaska, Hawaii or Puerto Rico, or any state or province that holds none of those points.

pass

SQL-001

SQLite structure is sound (PRAGMA quick_check)

Wrong data in a structurally sound file, and an index whose contents do not match its table: quick_check does not verify index contents, which is SQLite's documented difference from integrity_check. IDX-001 covers the R-trees.

pass

ROW-001

No data table is empty

0 empty tables, apart from those declared empty by design for the kind (water: waterway_lines)

A table that has rows but is missing most of them.

pass

ROW-003

No table of the previous edition has disappeared

0 of 5 tables gone

every table in the previous edition is still present, unless schema_version changed

A table dropped together with a schema_version bump that should not have been; the bump is taken as the declaration that the drop is intended.

since AER-4102

pass

GEO-001

Coordinates are present, valid and not at 0,0

0 bad coordinates. On point tables a NULL latitude or longitude is bad; on procedure and airway legs a leg with no fix position is left to PROC-FIX-001

A plausible coordinate in the wrong place, such as a transposed digit that still lands on land. On airway_legs, a leg with a NULL fix position (no check counts those).

pass

UNQ-001

Identifiers that must be unique are unique

procedures(airport, kind, ident) 0

0 duplicates

Two different things given the same correct-looking identifier in different tables, and a wrong identifier that happens to be unique.

pass

GEO-002
non-blocking

Points outside the US coverage envelope, against the previous edition

641 (previous 1,007)

Provisional threshold: no growth beyond 25 points or 10%, whichever is larger. FAA files carry real oceanic and foreign points, so the count is tracked, not forbidden

A point moved to the wrong place inside the envelope; the envelope is a handful of boxes, not a coastline.

pass

PROC-FIX-001
non-blocking

Procedure legs that name a fix the build could not place

941 of 200,853 legs (0.47%)

at most 0.5% of legs: a regression bound that carries forward the 0.47% observed in 2610 (950 of 201,030) and 2611 (941 of 200,853). It does not accept those legs as correct; it stops the share growing

A fix placed at the wrong coordinates. Legs with no fix by design (for example heading legs) are not counted.

pass

PROC-AWY-001

Airway idents are unique

0 duplicate idents; unique index present

0 duplicate idents

Two areas' airways merged under one ident row; PROC-AWY-002 looks for that.

since AER-1979

pass

PROC-AWY-002

No airway mixes legs from two areas (repeated sequence numbers)

0 airways

Two areas' legs merged with sequence numbers that do not collide, and an airway whose legs are all present but in the wrong order.

since AER-1979

Black-box check (Auspex)

Not run for this edition.

Row counts

Rows per table, against 2610.

Table	Rows	Previous	Change
airway_legs	16,960	19,391	-2,431 (-12.5 %)
airways	1,244	1,504	-260 (-17.3 %)
legs	200,853	201,030	-177 (-0.1 %)
procedures	14,303	14,338	-35 (-0.2 %)
transitions	52,317	52,352	-35 (-0.1 %)

Identity

Pack sha256	2ac5c748f9406817aacff0e84855afa6460efc7bf1d823b3a73635184dfe1099
Size	21,798,912 bytes
Content schema	1
Record	retro · raw JSON sha256 72127f6af9800e31 — matches the report_sha256 in the signed catalog
Built	· · no CI run recorded
From	makerplane-data —
Compared against	2610

Sources

No upstream sources are recorded for this edition (see PACK-004).

Known issues

Issues found after this edition was built are not listed here yet. Until they are, see the makerplane-data issues.

What this report is and is not

These are the checks we ran on this pack, what each one measured, and what each one cannot catch. It is evidence, not a warranty and not a certification. No authority has reviewed or approved this data or these checks. Passing them does not mean the data is correct, complete or current. Results marked as coming from Auspex come from a proprietary AI test engine whose method is not published; each of its findings is stated so you can check it yourself. This data is for Experimental / Amateur-Built use. This data is provided as-is with no warranty and any use of the data is at your own risk. Verify against official publications.

Check it yourself

packtool report --check procedures-conus-2611.pack

Re-runs every open check on the pack you downloaded and compares the result with this record. How to do it.