How do runway closure NOTAMs affect the dispatch release for a Part 121 flight?

A runway closure NOTAM at the departure, destination, or alternate airport can change which runways are available for performance calculations, invalidate a selected alternate if its only usable runway is closed, and trigger Traffic Flow Management programs that alter departure slot times. The dispatcher must review all relevant NOTAMs and confirm the release reflects these conditions before signing. Failing to account for a closure can make the release illegal under 14 CFR 121.599.

What is the difference between a NOTAM D and an FDC NOTAM for runway closures?

A NOTAM (D) covers physical conditions such as pavement closures, construction, and lighting outages, and is disseminated nationally — this is the type typically used to close a runway. An FDC (Flight Data Center) NOTAM carries regulatory force and primarily contains amendments to published instrument procedures, airway changes, and TFRs — for example, suspending an ILS approach because of an outage, which effectively closes that runway for IFR operations even if the pavement is intact. Both types appear in a standard preflight NOTAM briefing and must be checked before release.

How do airport surface closure NOTAMs connect to FAA ground delay programs?

When a runway closure reduces an airport's acceptance rate, the FAA's Traffic Flow Management system may respond with a Ground Delay Program or Ground Stop to meter traffic. Dispatchers should treat a GDP or GS as a signal to look for a corresponding surface or runway closure NOTAM explaining the capacity reduction. Understanding the NOTAM behind the TFM program helps dispatchers estimate whether delays are temporary, adjust fuel loads, or reassess alternate choices.

Airport Surface and Runway Closure NOTAMs in the Release Process

Every aircraft dispatcher release is, at its core, a legal document asserting that the planned flight can be conducted safely and in compliance with all applicable regulations. One of the most operationally critical steps in building that release is verifying current NOTAMs — Notices to Air Missions — with special attention to airport surface and runway closures. A closed runway or restricted taxiway that slips through the NOTAM review process can force a diversion, strand an aircraft on the movement area, or — in the worst case — contribute to a surface incident. For dispatchers working under 14 CFR Part 121, the obligation to account for airport conditions is not optional; it is embedded in the dispatch release requirements and the joint responsibility framework shared with the pilot-in-command.

This article walks through what surface and runway closure NOTAMs contain, how they are generated and disseminated, where they fit inside the dispatch release workflow, and how to avoid the traps that catch even experienced dispatchers off guard.

What Airport Surface and Runway Closure NOTAMs Are

A NOTAM is an official notice distributed by aeronautical authorities to alert pilots and other aeronautical personnel of conditions that are not adequately covered by standard aeronautical charts or published procedures. The FAA classifies NOTAMs into several types; the ones most relevant to airport surface operations are NOTAM (D) — distant dissemination NOTAMs that cover runway, taxiway, and other airport facility conditions, including runway closures — and FDC NOTAMs, which carry regulatory force and primarily contain regulatory information such as amendments to published instrument approach procedures, airway changes, and temporary flight restrictions. An FDC NOTAM can suspend or amend an instrument approach procedure serving a given runway, which effectively closes that runway for IFR purposes even though the runway itself may be issued a separate NOTAM (D) closure for the pavement condition.

A runway closure NOTAM typically specifies the runway designator (e.g., RWY 28L), the nature of the closure (construction, displaced threshold, arresting gear installation, lighting outage), and the effective time window expressed in UTC using the standard NOTAM format: a ten-digit date-time group (YYMMDDHHmm) for the start and end. Taxiway closure NOTAMs follow the same structure and may affect the only viable route to a particular gate or deicing pad. Apron and ramp closures, while sometimes handled by the airport operator rather than the FAA NOTAM system, can also appear as NOTAMs when they affect the movement area under ATC jurisdiction.

How NOTAMs Are Generated and Disseminated

Airport operators, the FAA, and military authorities all have the ability to originate NOTAMs through the FAA NOTAM Office (FNS — FAA NOTAM System). An airport operations department typically contacts the Air Traffic Control Tower or the Airport Traffic Control Tower coordinator, who then files the NOTAM through official FAA channels. Once entered, the NOTAM propagates through the Domestic Notices to Air Missions System and is available via the FAA's official NOTAM search system at notams.aim.faa.gov, through approved electronic flight bag providers, and through airline operations center NOTAM aggregation systems.

The Aeronautical Information Manual (AIM), Chapter 5 establishes the NOTAM framework that pilots and dispatchers rely on. It describes how NOTAMs are filed, their time-of-applicability format, and the responsibility of pilots-in-command to review relevant NOTAMs before flight — a responsibility that the Part 121 dispatcher shares during the preflight planning and release process. The FAA's Traffic Flow Management (TFM) system, operated by the Air Traffic Control System Command Center (ATCSCC), can issue ground delay programs, ground stops, and reroutes that interact directly with surface closures; a runway closure that reduces airport acceptance rate (AAR) often triggers TFM initiatives that affect departure slots across the national airspace.

The Dispatcher's Role in the Release Process

Under 14 CFR Part 121, a flight may not depart unless both the pilot-in-command and the aircraft dispatcher have signed the dispatch release. The release must reflect the conditions at the departure airport, the destination, and all required alternates. NOTAMs bearing on any of those airports are therefore part of the required preflight information package. The dispatcher's analysis must address at least the following questions:

Is the planned departure runway available? A closure on the primary departure runway may require a performance recalculation if the alternate runway has a shorter field length, a different obstacle environment, or different lighting that could affect low-visibility operations.
Are the required instrument approach runways at the destination open? If the destination has only one ILS and the ILS runway is NOTAMed closed, published minimums for that approach are unavailable, which directly affects alternate airport requirements under 14 CFR 121.619 and 121.621.
Is the alternate airport truly viable? An alternate selected because it has low ceilings may also have a runway closure NOTAM that disqualifies it operationally even if it meets weather criteria.
Do surface closures affect ground movement time or gate access? A major taxiway closure can increase taxi time significantly, affecting fuel burn calculations for long taxi operations and pushing the aircraft closer to minimum fuel thresholds.
Has TFM issued any program in response to the closure? Ground stops and ground delay programs often reference the triggering event in their advisory text; a dispatcher who sees a GDP at the destination should look for an associated surface or runway NOTAM explaining reduced AAR.

Reading and Interpreting the NOTAM Format

NOTAMs use a compressed, abbreviation-heavy format that rewards deliberate reading. A typical runway closure NOTAM might read: !ORD ORD RWY 10C/28C CLSD 2505151200-2505151800. Decoded: the NOTAM is for Chicago O'Hare (ORD), it affects Runway 10C/28C, the runway is closed (CLSD), effective from May 15, 2025 at 1200 UTC through 1800 UTC, using the ten-digit date-time group format (YYMMDDHHmm). The ! prefix identifies it as a NOTAM (D). Dispatchers must cross-check the UTC window against the planned block-out, en-route time, and arrival time to determine whether the closure is active during any phase of flight that matters.

A conditional NOTAM uses language such as WIE (with immediate effect) or specifies a time estimated (EST) for reactivation. Estimated closure end times can change; dispatchers should build in a protocol to re-check NOTAMs for flights with planned departure or arrival near the boundary of a conditional closure window.

Interaction with Traffic Flow Management

The FAA's Traffic Flow Management system processes real-time airport capacity data, including runway configuration and closures, to calculate Airport Acceptance Rates. When a runway closure reduces the number of available arrival or departure fixes, ATCSCC may implement a Ground Delay Program (GDP), a Ground Stop (GS), or an Airspace Flow Program (AFP). Dispatchers monitoring TFM advisories through tools such as the Aviation System Performance Metrics (ASPM) system or airline-specific TFM feeds will see these programs reference the impacted facility.

A critical dispatcher skill is working backward: when a GDP appears at a destination, check the NOTAMs for that airport to understand why the program exists. If the cause is a closed runway that is scheduled to reopen before your aircraft's estimated arrival, it may be possible to absorb the delay without holding fuel or diverting. If the closure is indefinite or weather-dependent, alternate planning and fuel uplift become essential adjustments to the release.

Key Numbers and Rules

NOTAMs use UTC (Zulu) time exclusively; dispatchers must correctly convert local schedule times to UTC to compare against NOTAM windows.
Under 14 CFR 121.599, no dispatcher may release a flight unless satisfied that the flight can be conducted safely — airport surface conditions are explicitly part of this determination.
The alternate airport weather minimums under 14 CFR 121.619 become meaningless if the alternate's runway(s) are closed; a NOTAM closure effectively removes that airport's utility as an alternate regardless of its weather.
NOTAM duration varies by the nature of the condition rather than a fixed universal limit; temporary closures are periodically reviewed and reissued or canceled as conditions change, and permanent changes are eventually incorporated into charts and Airport/Facility Directory (Chart Supplement) data.
A NOTAM with a PERM (permanent) designation has no expiration and remains in effect until the associated chart or procedure is updated.
The FAA NOTAM system is the authoritative source; third-party briefing systems, EFBs, and airline NOTAM feeds should be treated as aids — the dispatcher bears the responsibility to verify currency and completeness.

Common Test Traps

Confusing NOTAM time zones: A NOTAM showing 1200-1800 is always UTC. Converting to local time incorrectly is a frequent source of missed closures, especially across daylight saving time transitions.
Assuming the alternate is unaffected: Exam scenarios often present a destination with deteriorating weather alongside an alternate that has a runway closure NOTAM — both problems must be resolved before a legal release can be issued.
Ignoring taxiway closures as operationally irrelevant: A taxiway closure can make a runway physically inaccessible even if the runway itself is open, affecting performance calculations and departure options.
Treating an estimated end time as a guaranteed reopen: NOTAM EST times are estimates; dispatchers must plan for the possibility that the closure extends beyond the stated window.
Missing FDC NOTAMs that suspend approach minimums: An FDC NOTAM can suspend an ILS or other instrument approach, effectively closing a runway for IFR purposes even though the pavement is physically open — this directly affects alternate qualification and release legality.