Back to Insights
  • SMB/SME
  • Enterprise

· ASC Editorial Team

£33m From One Supplier's Outage: What the NATS Failure Teaches About Your Dependencies

On 8 September 2026, a previously unknown defect in legacy flight data software disrupted UK air traffic control. On 4 November, the Cyber Monitoring Centre (CMC) estimated the UK financial impact at about £33 million, within a range of £24 million to £42 million, and said more than 70 UK organisations were affected. It placed the event in Category 1, the lowest on its five-point scale.

This wasn't a cyber attack. NATS has said there is no evidence of malicious activity and no controller or operator error. Its preliminary report found that the defect was triggered when a routine request for an aircraft identification code and a higher-priority system message collided within about one millisecond. The CMC assesses accidental disruption as well as attacks, because the effect on the organisations that depend on a system can be much the same.

The most useful finding is who paid. Over three quarters of the impact fell on airlines. The CMC estimates that NATS itself lost less than £1 million in route charges on the cancelled flights, although that excludes the cost of its investigation and any future investment in resilience.

The timeline holds a second lesson. The flight data system was restarted at 16:09 and restrictions were lifted at 19:30, but airline schedules weren't back to normal until 11 September. The recovery took days because aircraft and crews had to be returned to the right places. A supplier's restored service is not the same as your restored service.

Most organisations have a dependency like this, even if it isn't a national one. It might be a payments processor, a managed service provider, a hosting platform or a logistics partner. Three questions are worth asking about each critical one.

First, what would an outage cost you, not the supplier? Check that figure against what your contract and your insurance would actually pay.

Second, how long would you need to recover after the supplier is back? Your plan should cover the backlog, the reconciliation and the customers waiting, as well as the outage itself.

Third, what would you do without good information? The CMC recommends the aviation industry assess whether earlier and more frequent estimates of how long the outage would last could have limited the disruption. You may have to make decisions before your supplier can tell you when it will be back.

The CMC also warns that the risk of similar defects remains high while NATS relies on legacy systems, and says the Cyber Security and Resilience Bill wouldn't by itself prevent a similar incident. Regulation can improve reporting and oversight. Knowing what you depend on, and how you would cope without it, remains your own job.

Which supplier could stop your business for a day, and would it bear much of the cost if it did?

Source: Cyber Monitoring Centre: Statement on the NATS Incident, November 2026

Get Insights by email

A short round-up of new articles every Monday morning. Nothing else.

We only keep your email address, and we don't track opens or clicks. Every email has an unsubscribe link. See our Privacy Notice.