Provenance and source use
Source Library
This page shows the source families the current codebase actually uses, how those values enter the application, and where a planned source remains outside the current encoded scope.
Source record
FAA Part 77
Directly encoded
- Document
- 14 CFR Part 77, Safe, Efficient Use, and Preservation of the Navigable Airspace
- Reference
- 77.19 civil airport and 77.21 DoD airport paragraphs used by separate active rule packs
- Usage type
- Directly encoded
- Used for
- Civil Part 77 77.19 airport imaginary surfaces where encoded. DoD Part 77 77.21 airport imaginary surfaces where encoded.
- Notes
- Civil and DoD Part 77 are evaluated independently. Part 77 includes heliport criteria under 77.23, but those heliport surfaces are not yet encoded in the current release.
Source record
FAA airport design criteria
Directly encoded
- Document
- FAA AC 150/5300-13B
- Reference
- Appendix H, Chapter 3, and cited tables such as 3-2 through 3-5 and OFZ-related paragraphs where encoded
- Usage type
- Directly encoded
- Used for
- FAA approach and departure entries. FAA RPZ, approach, departure, and OFZ / ROFA entries where the current AC rule pack is encoded.
- Notes
- Some FAA AC content remains partial; unsupported or dependency-gated surfaces remain not evaluated rather than assumed clear. Heliport / rotor-wing FAA design criteria require a separate rule pack and are not inferred from fixed-wing rows.
Source record
UFC / DoD criteria
Directly encoded
- Document
- UFC 3-260-01, Airfield and Heliport Planning and Design
- Reference
- Chapter 3, Table 3-2, Table 3-5, Table 3-6, Table 3-7, and cited glossary text where encoded. Current source library should be cross-checked against https://www.wbdg.org/dod/ufc/ufc-3-260-01
- Usage type
- Directly encoded
- Used for
- UFC Air Force fixed-wing runway criteria including primary, clear zone, APZ plan-view, approach-departure clearance, transitional, inner horizontal, conical, and outer horizontal entries where encoded.
- Notes
- Army, Navy, Marine Corps, and rotor-wing paths remain planned, partial, or explicitly unsupported. APZ is surfaced as planning/land-use context only and is not an independent vertical obstruction result in the current release.
Source record
Airport / runway geometry lookup
Directly encoded
- Document
- FAA NTAD runway geometry and supplemental airfield lookup sources used by the app
- Reference
- Lookup service outputs shown in the evaluator and diagnostics
- Usage type
- Directly encoded
- Used for
- Airport name, runway pair, runway end coordinates, runway length/width, and map context when available.
- Notes
- Lookup geometry supports evaluation context and overlays. Manual override fields remain available because lookup coverage is not universal.
Source record
FAA Digital Products
Directly encoded
- Document
- FAA Digital Products supplemental references
- Reference
- Airport diagram / chart supplement / other product records when configured
- Usage type
- Directly encoded
- Used for
- Supplemental reporting context and source notes only.
- Notes
- These records do not override the controlling criteria calculations.
Source record
Manual evaluator inputs
Manually entered
- Document
- User-provided project, geometry, and obstacle inputs
- Reference
- Project Information, Required Engineering Inputs, and Advanced Inputs
- Usage type
- Manually entered
- Used for
- Project metadata, obstacle elevations, distances, threshold coordinates, and manual overrides.
- Notes
- Manual input is part of the intended engineering workflow and is preserved in results and exports.
Source record
Derived geometry and elevations
Derived by calculation
- Document
- Internal encoded-rule calculations
- Reference
- Evaluator geometry and surface logic
- Usage type
- Derived by calculation
- Used for
- Object top elevation, runway-relative location, geometry notes, allowable elevation, clearance, and penetration values.
- Notes
- Derived values are traceable through calculation inputs, outputs, and geometry notes in the results and report.
Source record
Planned criteria packs
Planned / Not currently encoded
- Document
- Rule packs with TODO or PARTIAL status
- Reference
- Current codebase TODO and PARTIAL criteria entries
- Usage type
- Planned / Not currently encoded
- Used for
- Unsupported or incomplete surfaces remain not evaluated.
- Notes
- The app documents these gaps instead of inventing a result.