9.4 NOTAM System & Airport Field Condition Reporting

9.4 NOTAM System & Airport Field Condition Reporting

A flight plan is only as valid as the physical infrastructure supporting it. A catastrophic accident can occur if an aircraft attempts to land on a closed runway, an unlighted obstacle, an out-of-service instrument landing system, or a runway contaminated with ice. Under 14 CFR § 121.533 and § 121.601, the aircraft dispatcher is legally mandated to obtain and evaluate all current airport conditions, weather reports, and Notices to Air Missions (NOTAMs) before authorizing a flight release.

In winter operations, runway surface contamination presents one of the most severe hazards in commercial aviation. Following the landmark Southwest Airlines Flight 1248 overrun accident at Chicago Midway, the FAA established the Takeoff and Landing Performance Assessment (TALPA) initiative, revolutionizing how airport surface conditions are measured, reported, and factored into aircraft landing distance calculations.

---

The Notice to Air Missions (NOTAM) System

In December 2021, the FAA officially updated the acronym NOTAM from "Notice to Airmen" to the gender-neutral and internationally harmonized term "Notice to Air Missions." A NOTAM conveys timely information concerning the establishment, condition, or change in any aeronautical facility, service, procedure, or hazard, the timely knowledge of which is essential to personnel concerned with flight operations.

NOTAM Categories and Classifications

The FAA categorizes NOTAMs into four distinct administrative classes:

1. NOTAM (D) — Distant / Airport NOTAM

Pertains to local airfield facilities, navigational aids, and physical airport infrastructure. Distributed across both local and distant networks.

• Common Subjects:
  • Runway and taxiway closures (e.g., RWY 04L/22R CLSD).
  • Outages of navigational aids (e.g., VOR out of service, ILS localizer or glide slope unserviceable).
  • Airfield lighting system failures (HIRL, REIL, PAPI, taxiway centerline lights).
  • Airport rescue and firefighting (ARFF) index reductions (critical for Part 121 compliance under 14 CFR § 121.590).
  • Construction cranes, temporary obstacles, and wildlife hazards in the airport environment.

2. FDC NOTAM — Flight Data Center NOTAM

Regulatory and mandatory in nature. Issued by the National Flight Data Center (NFDC) in Silver Spring, Maryland.

• Common Subjects:
  • Amendments to published Instrument Approach Procedures (IAPs) (e.g., higher decision altitudes, changes to minimum descent altitudes / MDA, inoperative approach lighting minimums).
  • Temporary Flight Restrictions (TFRs) issued under 14 CFR Part 91.
  • Amendments to Standard Instrument Departures (SIDs) and Standard Terminal Arrival Routes (STARs).
  • Changes to Minimum En Route Altitudes (MEAs) along federal airways.
  • Permanent or long-term corrections to aeronautical charts.

3. Pointer NOTAM

Issued by a Flight Service Station (FSS) or air traffic facility to highlight, cross-reference, or point the reader toward another vital NOTAM that might otherwise be overlooked (e.g., a Pointer NOTAM calling attention to an active FDC TFR or major runway closure).

4. Military NOTAM

Pertains exclusively to military navigational aids, military airfields, and tactical airspace operations that are not part of the civil National Airspace System.

---

Modern ICAO NOTAM Format

To ensure global standardization, the FAA adopted the ICAO NOTAM format. A standard NOTAM string consists of structured fields:

• Header: Issuing agency, NOTAM number, and year (e.g., !ORD 01/142).
• Q-Code Line: ICAO code specifying the subject and condition (e.g., Q) ZAU/QMRLC/IV/NBO/A/...).
• Item A) Airport / Facility Identifier: e.g., KORD.
• Item B) Effective Start Date/Time (UTC): e.g., 2601151200 (YYMMDDHHMM).
• Item C) Expiration Date/Time (UTC): Specified as date/time, PERM (permanent), or EST (estimated, requiring a replacing NOTAM).
• Item D) Schedule: Hours of daily activity, if applicable.
• Item E) Plain-Language Condition Text: Full description of the outage or hazard.
• Items F) and G) Lower and Upper Altitude Limits: Used primarily for airspace restrictions.

---

The TALPA Framework and Field Condition (FICON) Reporting

Prior to 2016, runway condition reporting relied heavily on subjective pilot braking action reports ("fair," "poor") and surface friction measuring devices (Mu values). However, Mu readings proved unreliable on wet or slush-covered surfaces, and subjective pilot reports varied wildly between small regional jets and heavy wide-body transports.

In response to the Southwest Airlines Flight 1248 overrun at Chicago Midway in 2005, the FAA developed the Takeoff and Landing Performance Assessment (TALPA) framework, implemented on October 1, 2016. TALPA established the Runway Condition Assessment Matrix (RCAM), standardizing how airport operators assess contaminant type, depth, and temperature, translating them into objective Runway Condition Codes (RWYCC) reported via Field Condition (FICON) NOTAMs.

---

The Runway Condition Assessment Matrix (RCAM)

The RCAM utilizes an integer scale from 6 (best) down to 0 (worst). Codes are reported for each third of the runway: Touchdown (first third), Midpoint (middle third), and Rollout (final third).

---

The Absolute Prohibition: Runway Condition Code 0 ("Nil")

[!CAUTION] Regulatory and Operational Red Line — RWYCC 0 ("Nil"): Under FAA regulations and airline standard operating procedures:

1. Zero Operations: Takeoff and landing operations are strictly prohibited on any runway with an RWYCC of 0 or a braking action reported as "Nil".
2. No Dispatch: No aircraft dispatcher may release or dispatch a flight to an airport or runway where the current or forecast braking action is Nil.
3. Immediate Runway Closure: Under 14 CFR Part 139, airport management is legally mandated to close the runway immediately upon receiving a verified Nil braking action report or determining conditions equal RWYCC 0, until remediation (plowing, chemical de-icing, sanding) restores braking action to at least RWYCC 1 or higher.

---

Anatomy of a FICON NOTAM

A Field Condition (FICON) NOTAM communicates contaminated runway information in a standardized format:

DEN 01/045 KDEN RWY 16R FICON 5/5/3 100 PCT DRY SN, 100 PCT DRY SN, 50 PCT 1/4IN SLUSH 2601151200-2601151600

Detailed Component Breakdown:

1. DEN 01/045: Facility identifier and sequential NOTAM tracking number.
2. KDEN: ICAO airport identifier (Denver International Airport).
3. RWY 16R: The specific runway surface being evaluated.
4. FICON 5/5/3: The three Runway Condition Codes (RWYCC) for each runway third:
   • Touchdown Third: 5 (Good)
   • Midpoint Third: 5 (Good)
   • Rollout Third: 3 (Medium)
5. 100 PCT DRY SN, 100 PCT DRY SN, 50 PCT 1/4IN SLUSH: Contaminant coverage and type for each third:
   • Touchdown third: 100% coverage of dry snow (<= 0.75 in).
   • Midpoint third: 100% coverage of dry snow.
   • Rollout third: 50% coverage of 1/4-inch slush (triggering the lower code 3 due to slush/wet contamination).
6. 2601151200-2601151600: Valid time period in UTC (January 15, 2026 from 12:00Z to 16:00Z).

---

Downgrade and Upgrade Protocols

• Downgrade Authority: Airport operators can immediately downgrade an RWYCC based on pilot braking action reports (PIREPs) or decelerometer readings. For example, if an RCAM assessment suggests RWYCC 3, but two consecutive arriving aircraft report braking action as "Poor" (RWYCC 1), the airport operator must immediately downgrade the published code to 1.
• Upgrade Restrictions: An airport operator cannot upgrade a runway condition code based solely on a favorable pilot report. An upgrade requires a physical runway inspection, application of chemical treatments or plowing, and temperature verification confirming the contaminant has been removed or transformed.

---

Dispatcher Performance Calculations and Safety Margins

Under 14 CFR Part 121 and FAA Advisory Circular AC 25-32, dispatchers must calculate takeoff and landing performance accounting for reported FICON conditions:

1. Landing Distance Available (LDA): The declared length of runway available and suitable for the ground run of an airplane landing.
2. Landing Distance Required (LDR) with Mandatory 15% Margin:
   • In commercial operations under OpSpec C054 / C060, dispatchers must verify that the aircraft can land and come to a complete stop on the contaminated runway within the Landing Distance Available.
   • The operational landing distance calculated from manufacturer contaminated runway data must include a mandatory minimum safety margin of 15% added to the distance.
   • Factored Landing Distance = Unfactored Contaminated Landing Distance x 1.15 <= LDA
3. Crosswind Adjustments: Airline Operations Specifications establish maximum crosswind limits scaled to reported RWYCC:
   • RWYCC 6 (Dry): Maximum certified crosswind (e.g., 35–38 knots).
   • RWYCC 5 (Good): Typically 25–30 knots.
   • RWYCC 3 (Medium): Typically 15–20 knots.
   • RWYCC 2/1 (Medium to Poor / Poor): Typically 10–15 knots.
   • RWYCC 0 (Nil): 0 knots (Operations Prohibited).