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 Notes
FAA Part 77
- Document
- 14 CFR Part 77, Safe, Efficient Use, and Preservation of the Navigable Airspace
- Reference
- 77.19 and 77.21 paragraphs used by the active Part 77 rule packs
- Usage type
- Directly encoded
- Used for
- Part 77 primary, approach, transitional, horizontal/inner horizontal, conical, clear zone, and outer horizontal logic where encoded.
- Notes
- Civil and DoD airport variants are evaluated independently where intentionally modeled, but user-facing output is normalized by current family handling.
FAA airport design criteria
- 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 OFZ / ROFA entries where the current AC rule pack is encoded.
- Notes
- Some FAA AC content remains partial; unsupported surfaces remain not evaluated rather than assumed clear.
UFC / DoD criteria
- 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
- Usage type
- Directly encoded
- Used for
- UFC Air Force fixed-wing runway criteria including primary, clear zone, APZ, approach-departure clearance, transitional, inner horizontal, conical, and outer horizontal entries where encoded.
- Notes
- Army, Navy, Marine Corps, and some rotor-wing paths remain planned or partial.
Airport / runway geometry lookup
- 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.
FAA Digital Products
- 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.
Manual evaluator inputs
- 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.
Derived geometry and elevations
- 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.
Planned criteria packs
- 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.