NATS Goes Down Again — and the Flight Planning Vendors Sitting on Top of It Should Be Taking Notes
If the name NATS appearing in your morning news feed triggers a specific kind of dread, you’re not alone. The UK’s air navigation service provider is conducting what it’s calling a “full investigation” into a system issue that disrupted thousands of flights across UK airspace — and while the initial statement confirmed this wasn’t a cyber attack, the disruption itself is the more commercially consequential story for anyone building or buying flight operations software.
This isn’t NATS’s first high-profile system failure. The August 2023 outage remains one of the most vivid recent examples of how completely a centralized ANSP software failure can collapse the flight planning pipeline — not because of anything the airlines or their vendors did wrong, but because the upstream data source simply went dark.
The Dependency Problem That Flight Ops Vendors Don’t Advertise
Flight planning software — whether it’s a commercial EFB platform, a route optimization engine, or a dispatch system — is built on a stack of data inputs it doesn’t own. NOTAMs, airspace restrictions, flow control advisories, and real-time routing constraints all flow through ANSP systems that are, by design, centralized. That centralization is a feature of air traffic management architecture, not a bug — but it creates a structural dependency that every flight ops software vendor inherits whether they acknowledge it or not.
What makes NATS outages particularly instructive is the scope. UK airspace sits at the intersection of transatlantic traffic, intra-European routing, and some of the highest-density domestic corridors in the world. When that system stutters, the disruption doesn’t stay neatly inside one airline’s operation — it fans out through every flight plan that touches UK airspace, cascading into crew legality windows, fuel calculations, and downstream connections that no vendor’s optimization layer can fully absorb.
Having spent years on both the product and bid sides of flight ops software deals, I can say honestly that I don’t recall upstream ANSP data resilience ever appearing as a formal criterion in an airline RFP. Airlines evaluate EFB platforms and flight planning tools on feature depth, UI quality, and integration architecture — all legitimate criteria. But the resilience of the underlying data pipeline rarely gets the same scrutiny, partly because vendors don’t volunteer it and partly because it’s genuinely difficult to test for in a demo environment.
What This Means for the Vendor Landscape
For the vendors building on top of ANSP data feeds, today’s outage is a useful stress test of a question that rarely surfaces in sales cycles: what does your platform do when the upstream data disappears, degrades, or becomes unreliable mid-flight?
The more sophisticated platforms — particularly those that have invested in data redundancy, multi-source NOTAM ingestion, or caching architectures — are quietly differentiated from those that assume a clean, continuous feed. That’s not a feature that tends to appear on a product comparison slide, but it’s a real operational distinction, and events like this have a way of making it visible in a hurry.
For airlines currently evaluating or re-procuring flight planning and EFB platforms, it’s worth asking vendors directly: what is the degraded-mode behavior when an upstream ANSP feed is unavailable, and what has your platform’s actual track record been during past ANSP disruptions? That’s a procurement criterion the 2023 NATS outage arguably should have put on every RFP template. That it apparently didn’t is worth reflecting on now that the scenario has recurred.
My honest read is that outages like this tend to get absorbed rather than acted on — filed somewhere between “act of God” and “not the vendor’s fault” in a way that never quite translates into changed procurement behavior. That’s understandable in the short term, but it does mean the same conversation resurfaces every time an ANSP has a bad day.
The broader commercial implication is harder to resolve. Flight ops software vendors can build more resilient data architectures, but they can’t fix a centralized ANSP system from the outside. The real strategic question — one that EUROCONTROL and individual ANSPs have been circling for years — is whether the ATM data layer itself needs a resilience architecture overhaul, and who pays for it. That’s a much longer conversation. But for the vendors and airlines sitting on top of the current infrastructure, today’s outage is a concrete reminder that the platform layer and the data layer aren’t the same thing, and that conflating them is a risk that eventually shows up in operations.