Supported
Validated supported scope
Criteria and scenarios described in the validated supported-scope sections below.
Evidence and supported scope
Validation and Criteria Coverage
Clear Path helps airfield, planning, and engineering teams rapidly screen proposed objects against supported obstruction-evaluation criteria, identify likely conflicts, and generate defensible planning reports before formal coordination or final approval.
Clear Path keeps supported coverage distinct from unsupported, dependency-gated, or not-currently-supported criteria, which remain clearly labeled as Not Evaluated, Needs Review, or unsupported.
Coverage Legend
Needs Review
Follow-on review required
Criteria, metadata, or project conditions that require additional confirmation.
Not currently evaluated
Outside current automated scope
Unsupported or dependency-gated paths remain explicitly labeled rather than assumed clear.
How to Read This Coverage
- Clear Path supports planning, screening, documentation, and decision support for obstruction and protected-surface review.
- It helps teams identify likely conflicts early, retain traceable assumptions, and move into formal coordination with a defensible planning record.
- The software does not certify compliance, issue FAA, DoD, airport-sponsor, or command approvals, or replace required engineering, OE/AAA, TERPS, environmental, safety, sponsor, or agency review.
- References to FAA, DoD, UFC, Part 77, or airport criteria identify source criteria only and do not imply endorsement, sponsorship, authorization, approval, or official status from any agency, command, military unit, or airport authority.
- Supported scope is limited to the fixed-wing criteria families and protected-zone findings already encoded in the current release; unsupported or dependency-gated criteria remain visible as Not Evaluated or Needs Review.
- Users should retain exported reports with assumptions, version metadata, and validation-basis metadata so project teams can trace what was checked and what still needs follow-on review.
Supported
Validated Supported Scope
Supported
Current encoded scope
Part 77 fixed-wing surfaces currently encoded in the release.
Supported
Current encoded scope
FAA AC fixed-wing criteria currently encoded in the release, including protected-area findings where implemented.
Supported
Current encoded scope
UFC / DoD fixed-wing criteria currently encoded in the release, including supported protected-zone findings.
Independent validation harness coverage is clean for supported-scope Part 77 fixed-wing surfaces, supported FAA AC fixed-wing surfaces and protected areas, DoD Part 77 supported surfaces, and UFC Air Force Class B supported surfaces and protected zones.
Supported-scope validation currently covers synthetic runway math, the 50-airport deterministic scenario matrix, real-airport smoke checks, boundary cases, clear and violation cases, inside/outside footprint cases, protected-zone cases, and JSON/PDF export consistency checks.
Representative deterministic airport coverage now uses the bundled 50-airport ICAO matrix; unsupported, confirmation-required, or metadata-sparse cases remain explicitly labeled rather than assumed complete.
Internal validation evidence
Representative Validation Coverage
Internal validation
Airport validation matrix
Current deterministic airport validation uses 50 bundled ICAO contexts. Sample airports include KMGM, KATL, KDFW, KDEN, KORD, KLAX, KJFK, KSAT, KHSV, KMXF; sparse or confirmation-required airports such as KMXF remain explicitly gated instead of being treated as clear.
Internal validation
Representative scenarios
- Clear, boundary, and violation cases for supported vertical surfaces across the 50-airport matrix.
- Inside, boundary, and outside cases for supported protected zones.
- Boundary conditions including zero-clearance and exact-footprint edge cases.
- Synthetic runway geometry checks plus bundled real-airport smoke validation.
- Criteria applicability classification for FAA-backed airport data, including confirmation-required and dependency-gated cases.
- JSON and PDF export consistency checks against supported evaluation outputs.
Supported
Current criteria families
- Civil Part 77 primary, approach, transitional, horizontal, and conical surfaces as encoded under 14 CFR 77.19.
- DoD Part 77 primary, clear zone, approach clearance, transitional, inner horizontal, conical, and outer horizontal surfaces as separately encoded under 14 CFR 77.21.
- FAA AC RPZ and selected approach, departure, and OFZ-related entries where currently encoded; ROFA, ROFZ, and broader FAA design dependencies remain partial or dependency-gated.
- UFC Air Force fixed-wing primary, clear zone, APZ plan-view, approach-departure clearance, transitional, inner horizontal, conical, and outer horizontal entries where encoded; APZ remains planning/land-use only and is not an independent vertical obstruction determination.
Needs review or not currently evaluated
Limited or Unsupported Areas
These limits do not make the product unusable. They define where manual review, additional source confirmation, or a future encoded rule pack is still required.
Operational Use Guidance
- Use Clear Path to screen projects early, document criteria-based analysis, and retain a traceable record of assumptions and source references.
- Retain exported JSON or PDF records with evaluation timestamp, source criteria, and version metadata for coordination across engineering, airport, sponsor, and program stakeholders.
- Where a result is Not Evaluated, Needs Review, or derived from sparse metadata, follow through with the applicable FAA, DoD, airport, environmental, safety, surveying, or engineering review path.
For deeper release evidence, see the validation documentation in the repo and the public Documentation and Known Limitations pages.