Clear Path

Menu

Buyer readiness

Commercial Readiness Summary

This page is intended for buyer conversations, evaluation reviews, and early diligence. It answers the common questions commercial reviewers ask without overstating what the current release does.

Operational readiness is not regulatory approval
Clear Path supports planning, screening, documentation, and decision support by helping teams screen proposed objects against supported obstruction-evaluation criteria, identify likely conflicts, and generate defensible planning reports before formal coordination or final approval. Results are not official FAA, DoD, airport sponsor, engineering, surveying, or legal determinations. 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. Final filing, approval, and enforcement authority remains with the applicable FAA, DoD, airport sponsor, or other authority having jurisdiction. Users are responsible for verifying all inputs, assumptions, criteria, and outputs before relying on results for formal submissions, approvals, construction, acquisition, operations, or compliance actions.

Buyer Questions

Q: What does it calculate?

A: It calculates runway-relative obstacle location, object top elevation, supported protected surface evaluations, clearance/penetration values, and preliminary violation status for supported Civil Part 77, DoD Part 77, FAA AC, and UFC criteria.

Q: What does it not calculate?

A: It does not calculate surfaces or standards that remain not encoded, does not replace official FAA/DoD/airport determinations, and does not make legal applicability decisions between conflicting authorities.

Q: What sources does it use?

A: It uses the source documents and encoded tables listed in the Source Library. Each result identifies its source where the active rule pack exposes it.

Q: How does it handle conflicting standards?

A: It evaluates selected standards independently and displays separate results. It does not silently merge standards or substitute one authority for another.

Q: Can results be audited?

A: Yes. Results expose inputs, geometry notes, methodology/source references where available, clearance/penetration values, and reportable calculation details.

Q: Can it integrate into our existing software?

A: The current architecture supports mode-aware PDF export and structured JSON export for known-location and placement-limit workflows. The app already ships Next.js route handlers for its current backend/API responsibilities; broader external integration may still warrant a dedicated service layer depending on scale and ownership boundaries.

Q: Who owns the code?

A: Clear Path is operated by Three Rivers Technologies LLC. Commercial ownership, licensing, and transfer terms are handled through the operator's written agreements and the public support contact.

Q: Is it documented?

A: Yes. The tool includes workflow help, source notes, known limitations, methodology notes, changelog/version data, and commercial-readiness guidance.

Handling of Multiple Standards

When multiple criteria are selected, Clear Path reports each standard independently. More restrictive results are visible, but the platform does not silently merge standards or substitute one authority for another.

  • FAA, UFC/DoD, and other criteria are evaluated independently.
  • Clear Path does not silently blend standards into a single controlling answer.
  • Each result identifies the criteria family and source document used by that result where available.
  • If multiple selected standards produce different outcomes, the outcomes remain visible side by side.
  • The evaluator remains responsible for selecting the applicable standard for the project context.

Preliminary-Evaluation Reminder

Clear Path supports planning, screening, documentation, and decision support by helping teams screen proposed objects against supported obstruction-evaluation criteria, identify likely conflicts, and generate defensible planning reports before formal coordination or final approval. Results are not official FAA, DoD, airport sponsor, engineering, surveying, or legal determinations. 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. Final filing, approval, and enforcement authority remains with the applicable FAA, DoD, airport sponsor, or other authority having jurisdiction. Users are responsible for verifying all inputs, assumptions, criteria, and outputs before relying on results for formal submissions, approvals, construction, acquisition, operations, or compliance actions.