Clear Path

1. Open the evaluator and choose the evaluation mode that matches the task.
2. Start with the selected runway workflow for a single runway/end review, or switch to the all-runway workflow when the object may affect more than one runway context.
3. Clear or replace any restored snapshot values before entering a new project.

1. Enter the airport ICAO and use the lookup/load action to populate supported airport and runway geometry fields.
2. Confirm the runway pair, runway end, threshold coordinates, and runway dimensions after the lookup completes.
3. If a runway or criteria field remains unresolved, treat it as requiring user confirmation before relying on the result.

1. Turn on only the criteria families that actually govern the project or that you need to compare side by side.
2. Review the per-runway criteria cards. Pair defaults apply first, and end-specific overrides only apply where you explicitly set them.
3. Keep Part 77 obstruction-surface results separate from FAA AC design dependencies and UFC protected-surface results when making decisions.

1. Enter object location using the supported runway-relative fields, map context, or direct coordinates where available.
2. Enter the ground elevation MSL and the object height AGL so Clear Path can derive the object-top elevation MSL.
3. Recheck the selected threshold and sign conventions before running the calculation.

1. Run the evaluation and review each criteria family independently.
2. Read Violations, Protected-Zone Findings, Clear, Not Applicable, and Not Evaluated separately. Not Evaluated and Unsupported do not mean Clear.
3. Use the effective criteria provenance labels to verify whether each result came from source metadata, a runway-pair override, an end-specific override, or still requires user input.

1. Open the map workspace tab to review the current runway geometry, object marker, and selected overlays in plan view.
2. Switch between OpenStreetMap, Light Basemap, and Engineering Plan View to compare geographic context versus schematic geometry.
3. Use Fit Map when you want to refocus the current view, not as a prerequisite for the initial render.

1. Open the 3D workspace tab to inspect surface relationships, runway context labels, and obstacle elevation visually.
2. Use 3D Angled View, 3D Overhead View, Zoom In, Zoom Out, Fit to View, and Reset View deliberately to control the camera.
3. Treat omitted-visualization notes as real limits on what the current release could render, not as proof that the omitted surface is clear.

1. Save the current evaluator workspace when you want to keep inputs, criteria selections, and result context together.
2. Use My Evaluations to manage saved records and reopen a saved evaluation back into the evaluator.
3. After reopening, verify the restored runway, runway-end overrides, and object inputs before making a new decision.

1. Use PDF or JSON export when you need a structured record of the current evaluation and assumptions.
2. Use the view capture controls to download the currently displayed 2D map or 3D engineering view image when you need a visual snapshot for coordination.
3. Review the disclaimer, assumptions, and known limitations before sharing any export outside the working team.

• Applicable criteria selection for the project context.
• Runway, runway end, runway width, and supporting geometry inputs.
• Object location relative to the selected runway reference.
• Object height above ground level and ground elevation MSL.
• Established airfield elevation, runway-centerline elevation, or other required datum inputs where the selected criteria family uses them.

Clear Path keeps Civil Part 77, DoD Part 77, FAA criteria, and UFC criteria separate. The evaluator does not silently blend standards into one controlling answer. If multiple criteria families are selected, review each result set independently and confirm which authority or standard actually governs the project.

For more detail, review the Criteria Comparison and Definitions & Assumptions pages.

Always review the calculation notes, geometry notes, assumptions, and known limitations before using any output for formal review, design development, operational planning, or compliance-related coordination. Some criteria remain partial, dependency-gated, or unsupported in the current release.

Review the Known Limitations page and Definitions & Assumptions as part of every formal review workflow.

PDF exports provide a formatted report with project information, input summary, criteria and source references, grouped results, assumptions, limitations, imagery, and disclaimer language. JSON exports provide a structured record of the evaluation inputs, outputs, source labels, and limitations for internal workflow or integration use.

Use exports as structured technical support for review, documentation, and coordination. They do not certify compliance or replace review by the authority having jurisdiction.