What Is a NOTAM? Understanding Notices to Air Missions

Introduction: Weather Isn't the Only Thing That Changes

Pilots and dispatchers spend a great deal of effort tracking TAF and METAR reports, and for good reason: weather changes constantly and directly affects the safety of a flight. But weather is only one half of the picture. The other half is the state of the aviation infrastructure itself: is the runway you planned to land on actually open? Is the ILS you're briefing for actually serviceable? Is there a temporary restriction over your route? This is the domain of the NOTAM, or Notice to Air Missions (in some jurisdictions still referred to by the older term, Notice to Airmen).

A missed NOTAM is a different kind of hazard than a missed weather update. Briefing an approach that has been taken out of service because the NOTAM was overlooked, or planning a departure through airspace that just became restricted, can turn a routine flight into a serious problem with no weather involved at all.

What Exactly Is a NOTAM?

A NOTAM is a standardized notice, issued through the ICAO-format system, that alerts pilots to the establishment, condition, or change of any aeronautical facility, service, procedure, or hazard, the timely knowledge of which is essential to personnel concerned with flight operations. In plain terms: anything that changes about an airport, a piece of airspace, or a navigation aid, outside of routine weather, is communicated through a NOTAM.

Common categories include runway and taxiway closures, unserviceable or relocated navigation aids (ILS, VOR, NDB, DME), GPS/GNSS outages or interference affecting RNAV approaches, obstacles such as cranes near an approach path, airspace restrictions and temporary flight restrictions, and changes to approach lighting or visual aids like PAPI and VASI. A NOTAM can be as routine as a taxiway light being out of service, or as operationally critical as a runway being completely closed.

Decoding a NOTAM: The Structure

Like a TAF, a NOTAM follows a rigid coded format, so let's walk through a representative example:

A2882/26 NOTAMN
Q) LTAA/QMRLC/IV/NBO/A/000/999/4116N03633E005
A) LTFH B) 2608060000 C) 2608192359
E) RWY 13/31 CLSD DUE WIP

• A2882/26: The NOTAM's unique number and issue year. This identity is what lets a system track whether a given NOTAM is new, or whether a later NOTAM revises or cancels it.
• NOTAMN: The keyword identifying this as a brand-new NOTAM. A revision instead reads NOTAMR followed by the number it replaces, and a cancellation reads NOTAMC followed by the number it cancels.
• Q) line: The Q-code line, a compact machine-readable summary: the FIR, a two-letter subject/condition code (here MR for runway), traffic and purpose flags, the scope, a lower/upper altitude limit, and a coordinate with a radius of applicability.
• A): The ICAO location the NOTAM applies to.
• B) / C): The start and end of the NOTAM's validity period, in UTC. C) may also read PERM for a permanent change.
• E): The plain-text description of what the NOTAM actually means. Here, runway 13/31 is closed due to work in progress.

The abbreviations inside the E) line follow their own standardized contraction list: CLSD for closed, U/S for unserviceable, WIP for work in progress, and so on. That's why raw NOTAM text can look dense until you know the vocabulary.

New, Revised, and Cancelled: A NOTAM Has a Lifecycle

Unlike a METAR, which is simply superseded by the next hourly observation, a NOTAM stays active until it is explicitly cancelled or its end date passes. This means the operationally relevant question is rarely "what's the latest NOTAM." It's "what NOTAMs are currently active, and has anything changed since I last checked." A revision (NOTAMR) is especially easy to miss if you're only glancing at a raw list, since it silently supersedes an earlier notice rather than announcing itself as urgent.

Why Continuous NOTAM Tracking Matters

A busy airport can have well over a hundred NOTAMs active simultaneously, the overwhelming majority of them routine. The practical challenge isn't reading a single NOTAM. It's noticing the one new, revised, or cancelled NOTAM that actually matters, buried among the rest, without re-reading the entire list before every flight. This is exactly the kind of change-detection problem that benefits from automated monitoring: a system that already knows what was active yesterday can flag only what's different today, the same way TAF amendment tracking flags only the forecast that changed rather than asking a pilot to re-read every TAF from scratch.

Tools like AeroSentinel apply this same principle to NOTAMs: establish a baseline of what's currently active for a watched airport, then surface only new, revised, and cancelled NOTAMs as they happen, through the same alert and notification pipeline already used for TAF and METAR changes.

Conclusion

A NOTAM is, in effect, the aviation system's mechanism for saying "something about the infrastructure changed, and you need to know before you rely on it." Reading a single NOTAM is a matter of learning a fairly compact set of abbreviations and the Q/A/B/C/E structure. Reliably catching every NOTAM that matters, across every airport on a route, without missing the one that counts, is the harder and more important problem, and it's the one worth solving with continuous monitoring rather than a manual check before each flight.