Clear Path

Menu

Clear Path knowledge center

Documentation

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.

This page collects the buyer-facing and user-facing documentation that describes what the current Clear Path release does, how results are exposed, and where follow-on review is still required.

Product
Clear Path
Version
v0.1.2
Revision
e2444be
Last Deployed
2026-07-27

Choose the right resource

Documentation Library

Start with the group that matches the decision or review task in front of you.

Resource group

Reports and Exports

Review a public report example before working with evaluator outputs.

Resource group

Purchasing and Organizational Guidance

Review current commercial and organizational readiness information.

Current release

Calculation Capabilities

Object top elevation

  • Ground elevation MSL plus object height AGL, with a direct object-top-elevation override when the evaluator chooses to use one.

Runway-relative location

  • Longitudinal distance from the selected threshold.
  • Lateral distance from runway centerline or extended centerline.
  • Runway-end orientation tied to the selected threshold for directional surfaces and overlays.
  • Inside/outside runway-related footprints where the current rule pack supports a footprint test.

Supported surface evaluations

  • 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.

Clearance / penetration outputs

  • Allowable elevation at the object location where encoded geometry permits evaluation.
  • Object top elevation used by the calculation.
  • Clearance amount or penetration amount in feet.
  • Geometry notes describing the controlling distance mode used by the surface logic.

Visualization and reporting

  • Engineering map view with selected overlays and object marker when geometry is available.
  • 3D angled and 3D overhead engineering graphics generated from active evaluator geometry.
  • PDF export with project information, input summary, results, source references, and preliminary-use disclaimer.

Audit Trail and Calculation Transparency

  • Project information, airport/runway selection, runway end, and object inputs are preserved in the evaluation state and exported report.
  • Each evaluated surface carries geometry notes, input rows, output rows, and source references where the active rule pack provides them.
  • Distance mode is exposed through geometry notes such as longitudinal from threshold, lateral from controlling edge, radial from boundary, or footprint-only checks.
  • Manual overrides remain visible in the input summary rather than being hidden by auto-filled values.
  • Where the code does not expose a formula as literal algebra, the methodology is documented as encoded rule logic rather than reverse-engineered text.

Authority Basis and Operational Use

  • 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.

Buyer-readable validation coverage detail remains available on the Validation and Criteria Coverage page.

Integration Readiness

Scroll horizontally to view the complete table on smaller screens.

Clear Path integration readiness by topic
TopicCurrent capability
Frontend frameworkNext.js 16 with React 19 client/server components.
Backend/APINext.js App Router routes provide the current backend/API layer for authentication, persistence, admin, billing, and evaluator workflows.
State modelEvaluation state is JSON-serializable and can be exported without secrets or environment variables.
Current export formatsKnown-location evaluations and placement-limit calculations can both be exported as PDF reports and structured JSON, with mode-specific audit content.
Deployment patternsSuitable for hosted web deployment, local/internal network hosting, or wrapping in a controlled desktop shell.
EmbeddingThe evaluation flow is component-based and can be integrated into a broader internal web application with additional engineering work.

Support

Commercial and Legal Contact

Commercial licensing, ownership questions, privacy contact, and organization-specific legal terms are handled through the public contact workflow.

Use Contact or support@airspaceevaluator.com for support, licensing, privacy, and commercial coordination. No public mailing address is published at this time. Public terms are governed by the laws of Alabama.

Typical response: within 2 business days.

Support workflow
  • Access/account issue
  • Billing or invoice question
  • Report question
  • Airport/runway data issue
  • Criteria/supportability question
  • Bug or technical issue
  • Demo/access request
For report or data questions, include
  • Airport identifier or airport name
  • Runway pair and runway end / reference end
  • Criteria profile used
  • Object latitude/longitude
  • Ground elevation and object height AGL
  • Screenshot or exported report, if available
  • What looked wrong, unclear, or blocked
  • Account email if the issue is access or billing related

Release history

Change Log

2026-07-03

v0.1.2

  • Added admin-only free beta evaluator invitations with full evaluator access and internal beta labeling.
  • Cleaned evaluator UI copy, saved-record quota messaging, and hosted smoke/preflight policy checks.
  • Shortened PDF known-limitations output while preserving detailed public limitations documentation.
  • Added account airport/airfield context editing for organization-backed users.
2026-05-09

v0.1.2

  • Added an internal validation-scenario system with eight structured sample cases.
  • Added scenario loading into the evaluator, validation comparison, and JSON validation-summary export.
  • Added validation-scenario documentation and local persistence for run results.
2026-05-09

v0.1.1

  • Added project information fields and report metadata export support.
  • Added grouped collapsible result panels to reduce vertical sprawl.
  • Added source notes, known limitations, documentation, and commercial-readiness content.
  • Added evaluation JSON export and optional PDF technical appendix toggle.
  • Corrected surface-specific distance mode logic for non-approach surfaces.
2026-05-01

v0.1.0

  • Initial packaged Clear Path workflow with evaluator, criteria comparison, engineering views, and PDF export.