Every pilot who has filed a flight plan in the last decade has bumped into FAA NOTAMs — those dense, all-caps blocks of text that fill the bottom half of every preflight briefing. The acronym used to stand for Notice to Airmen; in December 2021 the agency officially renamed it Notice to Air Missions to reflect the broadening scope of users (drone operators, balloon pilots, commercial space operators) and to drop the gendered language.

The new name stuck quickly inside the agency. Pilots still say "NOTAMs" the same way, but the underlying definition matters: a NOTAM is a time-critical aeronautical notice that affects the safety of flight, and you are legally required to review the ones that apply to your route before you push the throttle.

You can break the system down into three layers. The first is the publishing layer — the Federal NOTAM System (FNS), the FAA's central database that ingests notices from air traffic facilities, flight service stations, airport operators, military installations, and contracted users. The second is the distribution layer — the websites, apps, and briefing services that pull from FNS and put the notices in front of pilots. The third is the interpretive layer — the Airman Certification Standards, the Aeronautical Information Manual, and a slow-moving plain-language reform initiative that's trying to make NOTAMs readable without a decoder ring.

This guide walks through each layer in order, then covers the categories you'll actually see in a briefing (FDC, GPS, MILITARY, SAA, U, O), the currency rules that come up on every checkride, and the two major NOTAM system outages — January 2023 and a smaller event in early 2026 — that drove the most recent round of modernization spending. By the end you should be able to decode a working briefing, know what to skip and what to call flight service about, and understand where the system is headed over the next two or three years.

The Federal NOTAM System launched in 2008 and replaced a much older patchwork of regional NOTAM offices that had been creaking along since the teletype era. Before FNS, a NOTAM about a runway closure at a small airport in Idaho might or might not propagate to a flight planner in Boston, depending on how the originating facility filed it.

FNS centralized everything into one authoritative database run out of the FAA's William J. Hughes Technical Center in Atlantic City, New Jersey. When a controller at a tower issues a NOTAM about a temporary obstruction, it lands in FNS within minutes, and from there it gets pushed to every distribution channel the agency operates.

That sounds boring until you realize that FNS is what holds the system together. The reason a ForeFlight briefing can show you the same NOTAMs as DUATS-era tools or as a paper printout from a flight service station is that all those tools are pulling from the same FNS feed via the agency's NOTAM Manager interface.

When FNS goes down — as it did spectacularly in January 2023 — the entire distribution chain freezes. Briefing apps go stale. Flight service can still issue verbal NOTAMs over the phone, but the digital channels lose their authoritative source, and the FAA cannot legally allow commercial IFR departures until the database is verified.

The 2023 outage came from a corrupted database file during a routine sync between primary and backup FNS instances. Engineers had to roll back to the last clean snapshot, which took most of a day, and during the recovery the agency issued a nationwide ground stop on commercial flights. Roughly 11,000 flights were delayed or canceled.

Congressional oversight committees demanded an after-action review, and the resulting investment plan accelerated work on a successor system that's now in development. The early 2026 outage was much shorter — a few hours — but it triggered the same playbook and reminded everybody how fragile the dependency on FNS still is.

How does a pilot actually see NOTAMs in 2026? The distribution layer has gotten more sophisticated over the last decade. The historical default — Direct User Access Terminal Service (DUATS) — was retired in 2018 and replaced by 1800wxbrief.com, the Leidos-run flight service portal that handles standard, abbreviated, and outlook briefings. Most pilots still touch 1800wxbrief at some point in their flying career, especially when they need a documented briefing for legal currency or for a checkride scenario.

For day-to-day use, though, the mobile electronic flight bag (EFB) apps have taken over. ForeFlight, Garmin Pilot, and FltPlan Go all pull NOTAMs from FNS via the FAA's public data feeds and present them inside the route-planning workflow.

The user experience is dramatically better than reading raw NOTAM text: relevant notices show up as map overlays, expandable cards in the briefing, or flags on specific airports along your route. Pilots who used to skim 30 pages of raw NOTAM text in the legacy briefing tools can now see, in a glance, whether a runway is closed or a TFR is in effect.

The FAA also operates the NOTAM Search website at notams.aim.faa.gov/notamSearch — a free, public tool that lets anyone query the NOTAM database by airport, location, or NOTAM number. It's not as polished as the EFB apps, but it's the canonical source. If there's a discrepancy between what ForeFlight shows and what the FAA database says, the NOTAM Search site wins. Working flight dispatchers, military mission planners, and accident investigators all rely on it as the system of record. The interface looks like it was designed in 2009 (because it was), but the data underneath is current to the minute.

Beyond those primary tools, the system also distributes NOTAMs through Hub Site Concept (HSC) data feeds that third parties license, through automatic weather observation system (AWOS) broadcasts that include local NOTAMs, and through the old standby — calling Flight Service at 1-800-WX-BRIEF for a verbal briefing. The phone briefing is still legally valid currency for a Part 91 flight, and for some pilots flying out of remote strips with no internet, it's the only option.

Reading a raw NOTAM is where most newer pilots get tripped up. The format is a legacy of the teletype era — abbreviated, all caps, no punctuation, formatted as a single block. A typical NOTAM looks like !ORD 06/123 ORD RWY 10L/28R CLSD 2406151200-2406151800.

Decoded, that's: a NOTAM at Chicago O'Hare, the 123rd issued in June 2024, affecting Runway 10L/28R, which is closed from 1200 to 1800 UTC on June 15, 2024. Once you've decoded a few hundred of these, the format becomes second nature, but the learning curve is real, and the FAA's plain-language initiative is specifically aimed at flattening it.

The plain-language NOTAM project is part of a broader push toward structured, machine-readable aeronautical data using the ICAO Aeronautical Information Exchange Model (AIXM). The end state is a system where NOTAMs are issued as structured data fields (airport, runway, start time, end time, condition) rather than as free-form text, and where the human-readable presentation is generated automatically from the data. This solves several problems at once: machines can parse it reliably, briefing apps can render it consistently across platforms, and pilots can read it without memorizing abbreviations.

Adoption is slow. The legacy text format remains in use for backward compatibility, and the FAA has committed to a phased transition that runs through the late 2020s. Pilots flying in 2026 still see mostly the old all-caps format, with a growing minority of plain-language NOTAMs mixed in. The transition is more visible in ICAO countries that adopted AIXM earlier — flight planning across Europe or Asia today often shows much cleaner NOTAM presentation than the same workflow over the US.

Currency rules around NOTAMs are simpler than most pilots think, but they're worth getting right because they come up on every checkride and in every enforcement action. Under FAR 91.103 ("Preflight action"), the pilot in command must, before any flight, become familiar with all available information concerning that flight — and NOTAMs are explicitly named in the advisory circular that interprets the rule. There's no fixed look-back window in the FAR, but the practical industry standard is that NOTAMs reviewed within the four hours preceding a flight are considered current; anything older deserves a re-check.

The FAA's own guidance, in AIM 5-1-3 and Advisory Circular 91-92, recommends that pilots check NOTAMs as part of the standard preflight, then re-verify any time-critical notices (TFRs especially) immediately before takeoff. For longer flights — anything where the en-route phase will exceed three to four hours — best practice is to either receive an in-flight update from Flight Service or to confirm via Datalink that no new TFRs have popped up along the route.

For instrument pilots, there's an additional wrinkle around FDC NOTAMs. Chart amendments published as FDC NOTAMs are legally binding the moment they're published. If you're flying an RNAV approach into a non-towered airport and an FDC NOTAM has amended one of the waypoints since your chart was printed, you're required to fly the amended procedure, not the chart. Modern EFBs handle this automatically by overlaying FDC NOTAM data on the approach plate, but pilots flying paper charts are responsible for cross-referencing manually.

One practical note that surprises a lot of pilots: NOTAMs about your departure aren't waived just because you didn't see them. If you depart from an airport with an active NOTAM about a runway closure or a light-out condition, and you didn't review it, the FAA's enforcement position is that you failed to comply with FAR 91.103. The fact that the NOTAM was inconvenient to find doesn't change the regulatory standard. This is exactly why the EFB apps have become so dominant — they reduce the friction of checking enough that most pilots actually do it.

The January 11, 2023 outage was, by any measure, the worst single day in NOTAM system history. At roughly 0300 Eastern, a damaged database file inside FNS began corrupting downstream replicas during a routine sync. By dawn, the system was returning errors to every connected briefing tool, and the FAA's NOTAM Manager interface was offline.

Without an authoritative NOTAM feed, dispatchers couldn't legally release commercial IFR flights, and at 0728 Eastern the agency issued a domestic ground stop. The ground stop lifted at 0900 after engineers confirmed FNS was operating from a clean snapshot, but the cascade of delays propagated through the day — 11,000+ flight delays and 1,300+ cancellations.

The post-incident report identified three contributing factors: an aging codebase originally designed for a much smaller NOTAM volume, insufficient isolation between primary and backup database instances, and a maintenance procedure that didn't include a clean-state verification step. The FAA's response combined emergency funding for FNS hardening with an accelerated timeline for the long-planned NOTAM Modernization Program. That program is now the agency's flagship project for replacing the legacy FNS architecture with a cloud-native, structured-data platform built on AIXM.

The early 2026 outage — a shorter, less disruptive incident — was a separate root cause: a software bug in a new ingestion service introduced during a routine deployment. FNS itself stayed up, but ingestion of new NOTAMs stalled for about three hours, meaning the briefing tools showed stale data without obviously flagging it as stale. The FAA caught the issue and rolled back the deployment within four hours, but the incident prompted another round of process tightening around staged rollouts and canary deployments for FNS-adjacent services.

Both incidents reinforced the case for modernization, which the FAA has now committed to completing in phases through 2028. The new system will run on a containerized cloud platform with automated failover between geographic regions, native AIXM data ingestion and output, and a built-in plain-language rendering engine for human-readable NOTAM presentation. Pilots won't see most of the change directly — the user-facing apps will keep working the same way — but the back-end resilience improvements should significantly reduce the risk of a 2023-style cascade.

International flying changes the NOTAM picture in a couple of important ways. Most foreign countries follow ICAO Annex 15 standards for aeronautical information, which means the basic NOTAM format is consistent across borders, but the distribution channels and currency conventions differ. A flight from Miami to Nassau pulls Bahamian NOTAMs from BAHAMASNOTAM rather than from FNS, and the format will look slightly different — different abbreviations, different way of expressing time, often a smaller volume of total notices.

Within the US, the FAA distinguishes between domestic NOTAMs (issued under the agency's NOTAM specification) and ICAO-format NOTAMs (issued for international flights, conforming to Annex 15). The ICAO-format notices use a more structured field-based layout — Q, A, B, C, D, E, F, G codes that map to specific data points — and are required when filing internationally. EFB apps and dispatch systems handle the translation automatically for most pilots, but it's worth knowing the distinction exists because it comes up on commercial-pilot oral exams and in dispatch coordination.

Pilots flying transoceanic also need to factor in NAT NOTAMs (North Atlantic Track System notices) and special use airspace activations along oceanic routes. These tend to be more stable than domestic NOTAMs — the NAT track structure is published daily, and the relevant notices are usually issued well in advance — but they're critical for any flight crossing the Atlantic, where ATC separation depends on precise compliance with the published track configuration.

Most working pilots develop a personal shorthand for the categories of NOTAMs they actually care about and the ones they can safely skim. Runway closures, lighting outages, and TFRs are top priority — they directly affect operational decisions. Procedure amendments (FDC NOTAMs) for instrument approaches you'll use are mandatory reads. GPS outages get attention if you're flying RNAV, otherwise they're informational.

On the other end of the spectrum, NOTAMs about minor obstruction lights at airports far off your route, or about helipad closures at hospitals you won't transit, can be safely ignored. The trick is configuring your EFB's filter settings so the irrelevant notices don't drown out the relevant ones. ForeFlight, for example, lets you filter by NOTAM category, route proximity, and altitude band — set the filters tight enough and the briefing goes from 30 pages to 3.

A couple of patterns worth knowing: NOTAMs starting with !FDC are FAA-issued regulatory notices, almost always worth reading. NOTAMs starting with !GPS or !RAIM affect satellite-based navigation availability. NOTAMs with airport identifiers (like !ORD or !JFK) are local to that airport's operating environment. NOTAMs starting with !FDC 4/ followed by a long alphanumeric string are usually TFRs and special security restrictions — these deserve full attention regardless of where you're flying.

For pilots studying for knowledge tests, the practical advice is to spend an hour or two reading a sample briefing carefully, then to read the same briefing the next morning to see what changed overnight. The system has rhythm: certain NOTAMs (military exercise schedules, recurring runway closures for maintenance) repeat on predictable cycles, and pattern recognition develops quickly. By the time you're a couple hundred briefings in, the meaningful notices jump out and the routine ones blend into the background.

Where is the NOTAM system headed over the next three to five years? The agency's published roadmap has three pillars: resilience (the post-2023 hardening of FNS infrastructure), data modernization (the AIXM-based structured data transition), and plain language (the readability push). All three are funded in the current FAA Reauthorization Act and all three have committed milestone dates through 2028.

On resilience, the cloud-native replacement for FNS is in active development and is expected to complete phased rollout by 2027. Pilots won't see most of this directly — the user-facing tools will keep working the same way — but the back-end should be substantially more fault-tolerant. The agency has also invested in expanded monitoring and a faster incident response process, both lessons learned from the 2023 and 2026 outages.

On data modernization, the AIXM transition is the structural change that will eventually transform what NOTAMs look like to end users. As briefing apps update to consume AIXM feeds natively, the presentation layer can become much cleaner — structured cards instead of all-caps text blocks, dynamic filtering based on actual flight parameters, automatic translation between domestic and ICAO formats. The user experience over the next few years will quietly improve as the underlying data gets cleaner.

On plain language, the FAA has committed to retiring most legacy abbreviations and reformatting NOTAMs into readable English by 2030. The transition is incremental — abbreviations are being phased out one category at a time, with the most user-affecting (runway and approach NOTAMs) prioritized. Pilots flying today will see a slow improvement; pilots learning to fly in 2030 may never need to memorize the old NOTAM contractions list.

The agency's longer-term goal is to put the NOTAM system on par with weather products like METAR and TAF — still technical, still structured, but readable without training. That's the bar they're aiming for, and progress is genuinely visible cycle to cycle. The transition is the single biggest improvement to pilot-facing aeronautical information in a generation, and it's worth tracking through the FAA's news channels and the trade press as it unfolds.