Why FNS Retired
The new FAA NOTAM system 2026 finally went live on April 18, replacing infrastructure that was old enough to vote. Parts of the U.S. NOTAM System and the Federal NOTAM System (FNS) traced back to architecture written in the 1980s, with text-handling routines and message exchanges that predated most of the EFBs feeding off them. The system was reliable in the sense that it ran for decades, but it was brittle, hard to patch, and exposed in ways that became impossible to ignore after the January 2023 outage that grounded every commercial flight in U.S. airspace.
That outage forced a modernization mandate with congressional teeth. The FAA had been working on a replacement under its NOTAM Modernization program for years, but the 2023 ground stop turned a slow procurement into a hard deadline. The new NOTAM Management Service (NMS) was built to fix the foundation: cloud-hosted infrastructure, redundant message routing, and an architecture that does not require taking the whole stack offline to push a fix.
What Changed in the New NMS
The new NMS is, mostly, a back-end swap. The user-visible NOTAM format on April 19 looks almost identical to what you read on April 17. What changed is everything underneath.
The NMS is cloud-hosted with built-in redundancy and resiliency, designed to survive the kind of single-point failure that took FNS down in 2023. Message exchange between the FAA and downstream consumers, including third-party EFB providers, was modernized to support near-real-time data sharing instead of the older batch-flavored pushes. The system processes more than 4 million NOTAMs annually and is sized to absorb growth without the legacy bottlenecks.
The longer-term piece is format. The FAA has stated the NMS is built to support three presentation formats in parallel: the U.S. domestic format pilots have read for decades, full ICAO format, and a plain-language layer aimed at making things like GPS outages, taxiway closures, and TFRs easier to parse at a glance. Domestic NOTAMs are not going away on a fixed date, and the FAA is asking pilots to stay current with all three formats until it announces a phase-out. Treat that as the long-term direction, not a near-term action item.
How NOTAMs Reach Your EFB Now
If you fly with ForeFlight, Garmin Pilot, FltPlan Go, or SkyDemon for U.S. trips, you almost certainly noticed nothing on April 18. Those apps pull NOTAMs from FAA APIs, and the cutover routed those API endpoints through the NMS instead of the retired FNS back-end. NBAA, briefing operators ahead of the switch, called the change "completely transparent" for most users, and that played out fairly close to script.
The real-world wrinkle was the cutover window itself. The FAA performed the switch between roughly midnight and 4 a.m. EDT on Saturday, April 18. During that window, fresh NOTAM ingestion paused. Active NOTAMs issued before the maintenance window remained available through normal channels, but pilots filing or briefing in those four hours reported a mix of delayed updates, occasional duplicate notices, and a few EFB providers showing a "data may be stale" advisory. By mid-morning Saturday everything was flowing again.
If you fly internationally and your trip touches U.S. airspace, the same API change applies. Anyone who set up an EFB in the last few years probably has nothing to do; if you have a custom NOTAM feed wired into a dispatch tool, your IT team has likely already updated the endpoint. If not, that's the first thing to check before your next flight. For a refresher on getting EFBs talking cleanly to your hardware, see our walkthrough on setting up your portable ADS-B receiver for ForeFlight, SkyDemon, and beyond.
What Broke (and What to Check Before Your Next Flight)
The cutover was clean by aviation IT standards, but "clean" is not the same as "perfect." A handful of recurring complaints have surfaced in the twelve days since.
- Stale or duplicated NOTAMs. A small subset of NOTAMs got re-issued under the new system with fresh timestamps, so EFBs flagged them as new. Cross-check anything that looks unfamiliar against the issue date, not just the appearance date.
- Search-syntax differences on the FAA website. The FAA NOTAM Search tool now points at NMS data, and a few of the more obscure search filters behave slightly differently. If a saved search is not returning what it used to, rebuild it from scratch rather than tweaking it.
- Briefing-package formatting quirks. Some flight-service briefing packages came through with NOTAMs in a slightly different order or with extra header lines. The content is correct; the layout is not yet stable. Read end-to-end, do not skim.
- Cached NOTAMs in EFBs. If you flew Friday April 17, downloaded a briefing, and then flew Saturday morning without refreshing, you may have been looking at pre-cutover data. Force a fresh briefing for the first few flights after a long break.
- TFR latency for short-notice notices. A few short-fuse TFRs in the first 48 hours took longer than expected to propagate to third-party apps. Confirm TFRs against a primary source if anything feels off.
None of this is a reason to ground yourself. It is a reason to brief the way you would after any system change: a little slower, a little more carefully, with one extra cross-check.
How to Read a NOTAM Without Losing Your Mind
A NOTAM is a tiny dense puzzle. The trick is not reading every word, it's scanning for what matters to your flight.
Start with the contractions. RWY (runway), TWY (taxiway), OBST (obstacle), ILS U/S (instrument landing system unserviceable), GP U/S (glideslope unserviceable), MEDA (military emergency diversion airfield), ALS (approach lighting system). The FAA contractions handbook has the full list, but ten or twelve cover ninety percent of what shows up in domestic NOTAMs.
Then run a keyword scan. Departure airport identifier, destination identifier, every alternate, and any en-route waypoint or fix you actually plan to use. Ignore everything else on first pass. After the scan, walk back through the flagged NOTAMs and ask one question: does this affect a runway, taxiway, frequency, or procedure I'm relying on? If yes, plan around it. If no, move on.
Stay aware of format. U.S. domestic NOTAMs read differently from ICAO NOTAMs (the Q-line, A/B/C/D/E/F/G fields, and explicit time groups). The new NMS surfaces both formats depending on the source, so the same notice can look different on two apps. Recognize the shape, do not get thrown by it.
Frequently Asked Questions
What changed with the new NOTAM system on April 18, 2026?
The FAA retired the legacy FNS and U.S. NOTAM System and brought up the cloud-hosted NOTAM Management Service in their place during a four-hour maintenance window between midnight and 4 a.m. EDT. The format pilots see is largely unchanged for now. The infrastructure underneath was rebuilt for resilience and faster data sharing.
Do I need to do anything different in ForeFlight or Garmin Pilot?
No. Both apps pull NOTAMs from FAA APIs that were re-pointed at the NMS automatically. There is no setting to change. If you see something odd, force a fresh briefing rather than tweaking app settings.
Why am I seeing duplicate or stale NOTAMs?
A small number of NOTAMs were re-issued under the new system with fresh appearance times during the migration. Check the original issue date inside the NOTAM body before treating it as new information.
Will domestic NOTAMs move to ICAO format?
That's the long-term direction. The NMS supports domestic, ICAO, and plain-language formats in parallel, and the FAA has asked pilots to stay current with all three. There is no announced cutover date for retiring the domestic format, so do not change your habits yet.
Is the FAA NOTAM Search website still up?
Yes. The public NOTAM Search tool now pulls from NMS data. A few advanced search filters behave slightly differently. If a saved search misbehaves, rebuild it.
What if I miss a critical NOTAM because of the cutover?
Treat the next few flights with extra care. Brief twice if it's a busy field, cross-check TFRs against a primary source, and do not rely on a cached briefing from before April 18. If something does not look right, call Flight Service.
Carry the same discipline you'd use after any major system change: one extra cross-check on your next brief, a fresh briefing pull rather than a cached one, and a careful read of anything that smells stale. For the bigger picture on how surveillance and information systems are evolving around GA, our pillar on electronic conspicuity in general aviation covers where the rest of the modernization wave is heading.
