Civilian Airports / Field Conditions

Field Condition (FICON) Reporting

Runway assessments, draft FICON wording, and a condition ledger with recorded dissemination, restrictions, and restoration.

Request a demo

A condition report needs both an assessment and a communication record

An observation describes what is on the runway. Operations also needs to know what was communicated, whether an authorized restriction is active, and what supports restoration.

Field Conditions connects runway assessments with the Airport Condition & Restriction Ledger. Snow & Ice and Construction extend that workspace to seasonal and project work.

From the observation to documented follow-up

  1. Assess the runway as it is

    Record contaminant, depth, coverage, and observation time for the runway thirds. Codes are derived where applicable; an unassessed runway shows no active report.

  2. Prepare and review FICON wording

    Generate draft wording from the assessment for review and use in the authorized FAA channel. Glidepath does not submit the NOTAM.

  3. Record dissemination and restrictions

    The condition ledger retains exact messages and external NOTAM identifiers. Restrictions require a separate authorized activation; filing a condition does not activate one.

  4. Verify restoration and retain history

    Link corrective work, completed condition checks, closing dissemination, and restoration evidence. New assessments supersede prior reports while preserving their history.

What it automates

Unknown conditions stay visible

No active report is not represented as a dry runway or a current assessment.

Communication has evidence

The ledger retains what was actually sent, through which channel, and its external reference.

Closure has a documented basis

Corrective-action completion, restriction authorization, and condition restoration remain distinct steps.

Straight answers

What shows when a runway has no active report?

Conditions are not currently assessed. Glidepath does not assume a dry runway or publish a default condition-code triplet.

Does Glidepath publish the FICON NOTAM?

No. It prepares wording for review. The airport submits through an authorized channel and records the external identifier and dissemination evidence.

Does every assessment receive a runway condition code?

No. Code assignment depends on the assessed conditions and coverage. A report can retain contaminant information without assigning codes.

Does a new report erase the earlier one?

No. A new report supersedes the previous assessment. Issuance, updates, and cancellations remain in the retained history.

Connected modules