U.S. NOTAMs and Temporary Operational Changes

01

Start with the flight, not the length of the list

Long NOTAM lists invite two opposite errors: scanning so quickly that a critical amendment is missed, or reading every line with equal attention until the operational picture disappears. Begin with the proposed runway, taxi route, SID, route, arrival, approach, destination, and alternates. Review the whole applicable briefing, then mark the items that alter one of those elements.

A useful sequence is to begin with the intended operation and then search for changes to each part of it. At departure, that means the stand and surface route, runway, departure procedure, required navigation, and first part of the route. At destination, it means the arrival, approach, runway, landing aids, and movement to parking. The alternate deserves its own pass. This sequence makes a notice relevant because it touches a specific choice, rather than because it appears high in a vendor's list.

Place each affected item on a timeline. A runway closure that begins after the scheduled departure may still matter if a delay moves the flight into its validity period. A procedure amendment that expires before arrival may still matter if the flight arrives early. Check issue time, effective start, end, and any daily schedule, using UTC unless the source explicitly states otherwise.

Build a short change statement: “The planned landing runway remains available; the preferred ILS has an amendment effective before ETA; the alternate has a taxiway closure affecting gate access.” This turns notices into questions the crew can resolve in the release, chart, performance, and briefing workflow.

Time should include a realistic window around the estimate, not only a single ETA. A delayed pushback may bring a runway closure into force; holding may extend an arrival beyond the end of a service period. For a notice with a daily schedule, identify the days and hours that actually apply and keep all comparisons in the same time basis. If the notice contains an exception or uncertain end time, read the complete text and use the approved source to resolve it.

02

Understand the U.S. information structure

The FAA AIM distinguishes domestic NOTAMs, FDC NOTAMs, international NOTAMs, and military NOTAMs. Domestic notices often concern airport conditions, surfaces, aids, communications, and services. FDC notices can amend an instrument approach or published chart and can communicate regulatory information, including temporary flight restrictions. International notices use the ICAO format. A label indicates distribution and subject; it does not determine whether the item matters to the flight.

A NOTAM search limited to the airport identifier can miss a route constraint. The FAA AIM specifically calls for attention to ARTCC notices, which may concern temporary flight restrictions, GPS operations, special use airspace, or route changes. The crew should match the applicable center areas and planned route to the briefing provided by the operator. The purpose is to catch a notice whose location field is broader than a single airport.

Keywords provide a useful first pass: RWY, TWY, APRON, AD, NAV, COM, AIRSPACE, SID, STAR, IAP, and CHART name different affected domains. Do not discard an item because its keyword looks unrelated. A GPS testing notice can affect a planned RNAV operation; an airport service notice can affect a diversion; an IAP amendment can change the procedure on a chart that still appears current in the EFB.

Use the FAA Federal NOTAM System or an operator-approved briefing service to verify the current text. A map pin, color, or EFB summary is only an index to a notice. Read the original wording and its associated location and time before making an operational decision.

Notice categories and keywords help sort the briefing; they do not establish operational priority. A runway closure can change takeoff performance, an unserviceable lighting system can change an approach's usability, and an FDC amendment can alter published procedure information. The operational question is what the notice changes for this aircraft and this flight. Where abbreviations are unclear, use the official contractions reference instead of guessing from familiar-looking letters.

03

Decode a notice into an operational change

Extract five fields: affected location or facility; exact asset or procedure; nature of the change; effective period and schedule; and the action required in the flight plan or briefing. For example, “RWY 18/36 CLSD” means more than a closed strip. It can change departure performance, expected taxi, arrival runway, crosswind exposure, approach choice, and alternate viability.

Read the text as a bounded instruction about an identified object. A NOTAM for one runway threshold, one taxiway segment, or one IAP variant does not automatically apply to every similar item at the airport. Confirm the identifier, direction, facility, and period before transferring the meaning to the chart. The crew should distinguish a full closure from a partial limitation, such as a changed declared distance or unavailable component, because the resulting performance or approach calculation can differ materially.

For a NOTAM affecting an instrument procedure, compare the notice with the current chart and the aircraft or operator authorization. Identify whether the amendment changes a minimum, missed approach, fix, navigation requirement, or procedure availability. If the procedure data in the FMS, chart, notice, and ATC clearance do not reconcile, stop the setup and resolve the difference using approved sources.

For a navigation aid outage or GPS interference notice, ask which segments depend on the affected source and what approved alternate navigation remains. Do not assume a navigation display that appears normal proves the underlying service is available for the intended operation.

Translate the notice into the systems and decisions it touches. A displaced threshold may require review of the usable landing distance and visual references; an unavailable approach light may affect authorized minima; a NAVAID outage may remove an intended segment or require an approved alternative. These are questions for the current chart, approved aircraft documentation, and operator procedures. The NOTAM text identifies the change; it does not by itself complete the crew's calculation or authorization check.

04

Review airport and surface notices as a route

Compare runway, taxiway, apron, lighting, construction, and work-in-progress notices with the airport diagram. Trace the movement from stand to runway or from landing runway to parking. A taxiway closure may create an unfamiliar crossing or a longer taxi with a new performance, fuel, or timing consequence.

A surface restriction can create a second-order risk even when the intended runway remains open. The remaining route may pass a hot spot, a runway holding position, a narrow taxiway, or a construction boundary. The crew should trace an actual path on the diagram and identify where a new clearance is needed. If ATC offers a route that appears inconsistent with a closure or the aircraft's limitations, stop and clarify before proceeding.

At a destination, check whether the expected landing runway, runway exit, and access to the planned stand remain feasible. At an alternate, check the approach, runway, services, and surface route. “Airport open” is not enough to establish that the alternate is suitable under the operator’s dispatch rules.

After ATIS or a clearance changes the expected runway, revise the NOTAM scan around the new choice. An item originally irrelevant to runway 27 may become central to runway 09. Make that reassessment explicit in the arrival briefing rather than assuming the preflight filter still applies.

After landing, the runway exit that was expected during descent may no longer be usable. The crew should have enough awareness to avoid an improvised turn, while treating the actual taxi clearance as controlling the route. If the exit differs from the briefing, reestablish position, confirm the new path and any runway boundaries, and postpone nonessential cockpit work until movement is understood. Surface NOTAMs and the companion NFA airport-surface study should be read together.

05

Treat airspace and GNSS information as route constraints

FDC NOTAMs may announce a temporary flight restriction. Check the exact lateral and vertical limits, effective window, conditions, and published source. A graphical portrayal helps orient the crew but does not replace the notice. Determine whether the cleared route and likely vectors intersect the affected area and coordinate through dispatch or ATC as appropriate.

A TFR must be interpreted from its current notice, including lateral limits, vertical limits, validity, exceptions, and any contact or authorization conditions. A map overlay can help locate the area but may conceal a boundary detail or an amended effective time. A reroute should be checked against fuel, terrain, weather, airspace, and ATC clearance, rather than treated as a simple line around a graphic.

The FAA AIM describes GPS status, testing, and anomaly notices. A published testing area signals possible degraded or unavailable service; its effect depends on actual timing, aircraft capability, and intended route or procedure. Cross-check the flight’s navigation plan and alternatives. If the aircraft encounters an anomaly, use the operator’s procedures and promptly tell ATC.

Large-scale restrictions and navigation changes can propagate beyond the named airport. A departure route amendment can alter a downstream clearance; a GNSS interruption can remove an intended approach at the destination. Think through the next decision, not only the first affected waypoint.

GNSS testing and interference notices require careful distinction between an area of possible effect and actual navigation performance. Consider the planned use of GNSS for en route segments, RNAV arrivals, approaches, and aircraft functions that depend on position data. Monitor the aircraft's annunciations and integrity indications under approved guidance. Do not infer that an apparently normal map display confirms the integrity or availability required by an approach.

06

Recheck at operational decision points

An effective NOTAM picture is maintained, not simply collected before departure. Recheck changes when the release is updated, departure is delayed, the runway or route changes, the alternate changes, and before setting up an affected arrival or approach. In flight, use approved company and ATC channels for updates within the available communications and workload.

Define who owns the update at each decision point. Before departure, the crew can reconcile the dispatch release, current NOTAM briefing, ATIS and charts, and record a meaningful change. In flight, the PM can review a new airport or procedure notice while the PF preserves flight-path control and ATC awareness. The result should be a short shared conclusion: what changed, whether the current plan remains valid, and when it will be checked again.

Distinguish a new notice from an old notice that only became relevant after a clearance change. Either can require the same response: revisit charts, performance, briefing, and operational control. If critical source data are missing or contradictory, obtain clarification before crossing the relevant decision point.

Do not treat an EFB “download successful” indicator as proof that the notice set was refreshed at the required time. Confirm the update timestamp and applicability, and use the operator’s accepted method for offline or connectivity-limited operations.

A recheck should be proportionate to the change. A gate delay calls for a new time comparison; a runway swap calls for a runway, approach, performance and surface scan; a diversion calls for a full review of the new airport and alternate chain. If data connectivity is limited, follow the operator's contingency process and communicate uncertainty rather than treating an old briefing as current.

07

Worked example: amended arrival and changing runway

A crew initially expects an ILS to runway 27 and has briefed that approach. During descent, ATIS announces runway 09 and a new release note identifies an IAP amendment. The useful question is not simply “Are there NOTAMs?” It is whether the newly selected runway and approach remain authorized and how the amendment changes the flown procedure.

The crew first establishes the actual time of the amendment and whether it applies to the newly expected approach. A notice titled for runway 09 is not enough to know which procedure variant or minima changed. The PM reads the full text, identifies the chart affected and compares the new information with the available procedure and database. The PF retains the flight path and avoids an accelerated setup that compresses the cross-check.

The PM reads the full notice, checks its effective time and exact approach designation, and compares it with the current chart. The PF and PM verify FMS selection, constraints, minima, missed approach, and landing performance under operator procedures. They request time or vectors if needed to complete the change safely. If the data do not agree, they do not construct their own hybrid procedure.

Learning point: changes to runway, approach, chart, and NOTAM relevance should be treated as one connected event. The earlier briefing remains useful history, but the new clearance requires a new shared plan.

If the amendment makes the intended approach unusable or cannot be reconciled through approved procedures, the crew requests time and space from ATC to choose another option. That may mean vectors, holding, a different approach, or diversion under the operator's procedures and fuel situation. The example's core lesson is that a runway change also changes which notices matter; both pilots must be able to explain the new plan before the critical segment.

08

Match NOTAMs to charts and loaded data

An EFB chart, an FMS navigation database, and an airport diagram can have different update cycles. A current subscription or green synchronization symbol does not prove that all three depict the same temporary condition. Compare the chart revision and the NOTAM’s effective period whenever a procedure or movement area is affected.

Treat these as separate layers: the published procedure, a temporary amendment, the electronic chart presentation, and the loaded navigation path. They can disagree for legitimate timing reasons. The check should begin with the exact airport, runway, procedure title and revision, then compare waypoints, altitude constraints, missed-approach information and minima where relevant. A chart that looks current may still need an FDC amendment applied.

The crew should keep separate questions in mind: Is the chart itself current? Has a NOTAM temporarily changed the charted procedure? Does the loaded navigation database represent the intended charted path? Is the aircraft authorized and equipped for that path? A “yes” to one question does not answer the others.

If an amendment affects approach minima, do not silently apply a number from a notice to an unrelated procedure variant. Confirm the exact runway, approach name, equipment and category, and use the operator’s method for incorporating the amendment. Where ambiguity remains, seek authoritative clarification or choose another approved option.

The same discipline applies to departures and arrivals. A SID or STAR notice may alter an altitude, fix, transition, or chart note. Trace the amended instruction from clearance through chart and flight management system, with independent crew verification before the affected segment.

If a temporary change cannot be entered into the FMS as published, the crew must use only methods permitted by the aircraft and operator, or select another procedure. Avoid forcing a visual match by editing a route whose underlying procedure data remain uncertain. Explain which source controls each discrepancy and how it was resolved in the briefing; the other pilot should independently recognize the consequence.

09

Build an alternate that survives the actual restriction

A weather-qualified alternate can lose its practical value if the usable runway is closed, the required approach is unavailable, or airport services are restricted during the estimated alternate arrival window. Review alternate NOTAMs with the same attention to time and aircraft capability used at the primary destination.

Alternate review asks whether an aircraft can actually reach, approach, land and move at that airport in the expected period. Weather suitability alone is incomplete. A runway closure, approach outage, navigation limitation, rescue and firefighting restriction, or unavailable lighting can each affect that judgment depending on the operation. The operator's dispatch and regulatory criteria determine the formal alternate decision.

Consider a destination that remains suitable but a preferred alternate whose ILS is unavailable. The right conclusion depends on weather, other available procedures, runway performance, aircraft capability, the release and regulatory requirements. The notice raises a decision that dispatch and crew must resolve; it does not automatically prohibit the airport.

When delays or diversions alter arrival time, repeat the alternate scan. A notice that starts at 0200 UTC may be irrelevant to the original 0100 UTC alternate ETA and decisive after an hour of holding. Recompute the usable options before the flight reaches a fuel or routing decision point.

For international crews entering U.S. airspace, pay special attention to units, UTC windows, and the local airport identifier. A similar airport name or nearby navigation aid can make a correct notice appear to apply to the wrong facility if its location line is skimmed.

Compare the alternate with the same changing circumstances that threaten the destination. A regional GNSS disruption could affect both airports; a construction program may remove a preferred runway at night; a delay may move the alternate arrival into a closure window. The crew should know a second option before the last convenient decision point, and coordinate a change with operational control as required.

10

A practical crew briefing model

Summarize NOTAM effects in four layers. First, name the flight element: departure surface, en route navigation, arrival procedure, or alternate. Second, name the temporary change and its valid window. Third, state the effect on the planned operation. Fourth, state the approved action or open question.

The summary should be short enough to be spoken in the cockpit but specific enough to support action. For each material item, identify the affected flight element, the notice's time window, the operational consequence, the changed plan, and the next check. The PM can retain the source detail while the PF confirms how the change affects the flight path or aircraft setup. A meaningful readback within the crew closes the loop.

Example: “Destination ILS 27 is unavailable through our ETA. We plan RNAV 27 if authorized and weather supports it; we have verified database, chart, minima and missed approach. If GNSS becomes unreliable, we need a different approach or destination.” This is a reasoning pattern, not a substitute for actual operator and airport data.

Avoid vague phrases such as “NOTAMs checked” when a notice has an effect. The briefing should let the other pilot detect a missing consequence. If the PM believes a runway closure affects taxi only and the PF sees a takeoff performance issue, discussing the concrete change exposes the mismatch early.

Record unresolved questions in the crew’s normal workflow. Close each one with its source, action, and time of verification, especially when the departure is delayed or the clearance changes.

For example, a closed destination taxiway may require a different exit and a runway crossing after landing. The briefing would name the closure, the likely new route and its hold-short boundary, and the point at which the crew will obtain the actual ATC instruction. This is more useful than a generic statement that ground NOTAMs have been reviewed.

11

Crew review and final takeaways

For any relevant notice, each pilot should be able to state: what changed, where, when, how it affects the intended operation, and what action or verification closes the issue. The PM can track source and amendment details while the PF retains the flight path picture; operator role assignments govern the actual division of work.

During recurrent study, ask the crew to explain how a single change propagates. If an ILS becomes unavailable, what other approaches remain, which navigation sources do they require, what does the weather permit, and what happens to the alternate? If a runway closes after a delay, which performance, surface, fuel and release items must be reviewed? These questions test reasoning rather than recall of abbreviations.

Review questions: What would make a runway closure relevant after a delay? Why can an IAP NOTAM override a current-looking chart? When does a GPS testing notice require a navigation reassessment? Which airport notices affect an alternate after touchdown? What event triggers a second NOTAM review in flight?

The professional standard is a traceable decision. Identify the notice, connect it to a flight element and time, make the required adjustment using approved procedures, and reassess when the flight changes.

A good debrief distinguishes detection from decision. The crew may have noticed a NOTAM yet failed to connect it to the selected procedure; it may also have made a safe change without documenting the source and time. The aim is a repeatable habit: find the relevant change, verify it against current official material, decide under approved procedures, and recheck when the plan or time changes.

Operational review card

1. Locate: Confirm airport or facility identifier, the named runway, taxiway, aid, procedure, or airspace, and whether the affected item is part of the intended flight.

2. Time: Compare effective start, end, and any daily schedule with departure, arrival, and alternate arrival estimates in UTC. Revisit the comparison after a meaningful delay.

3. Consequence: State what changes in the flight release, aircraft capability, runway and performance assessment, chart, taxi path, or FMS setup.

4. Cross-check: Read the original notice and compare the current chart, airport diagram, approved EFB data, ATIS, and clearance. Resolve differences before the affected phase.

5. Decide and monitor: Use approved operator processes to change the plan, brief both pilots, and define when a new NOTAM check becomes necessary.

Worked prompt: If the assigned landing runway changes during descent, which previously screened notices now apply? If holding moves the alternate ETA across the start of a runway closure, what options remain?

Official sources and editorial scope

• FAA AIM 5-1-3, Notice to Airmen System
• FAA NOTAM Order, Scope and Keywords
• FAA Federal NOTAM System
• FAA NOTAM and TFR Information

Review current source material before operational use. Aircraft and operator procedures, regulations, flight release, and ATC clearances control the flight.