NATS Broke Again. Your Hotel Found Out From the Guests.
NATS lost its flight processing system at 1:46pm yesterday and had a fix in by 4:40. Under three hours. In that window it broke close to a thousand flights, cancelled at least 625 of them outright, and left 65,000 Ryanair passengers alone sitting somewhere they didn't plan to be, some of them for eight hours.
Here's the part that should bother you more than the outage. Most UK hotels found out from a guest standing at the front desk at ten at night.
What actually happened
The failure hit the flight processing system, which is the bit that turns filed flight plans into something controllers can work with. When it goes, departures stop. NATS announced it was investigating at 13:46, implemented a fix around 16:40, and said systems were "starting to recover."
By mid-afternoon FlightAware had 490 delayed departures out of Heathrow, Gatwick, London City, Luton, Edinburgh and Bristol, plus another 525 arrivals delayed or cancelled into the same airports. Flightradar24 counted at least 625 cancellations across UK airports over the day. Manchester, Stansted, Birmingham and most of Scotland got dragged in. So did European airports holding UK-bound aircraft on stand.
British Airways binned at least 16 Heathrow departures. Ryanair cancelled more than 50 flights and is now publicly calling for NATS chief executive Martin Rolfe to resign. Wizz Air went with "not fit for purpose." The CAA wants a full report.
Ryanair's COO Neal McMahon put it about as bluntly as anyone has: after the 2023 collapse, everyone was told lessons had been learned and the systems were fixed. Then July 2025 happened. Now this.
He's right, and the airlines will get their inquiry. But airlines being angry doesn't put a single head back in your beds.
The recovery is where the money moves, not the outage
The outage was yesterday afternoon. Your problem is this morning.
NATS fixed the software. It did not fix the aircraft parked at the wrong airport or the crew that ran out of legal hours in Palma. That unwinds over 48 to 72 hours, and it unwinds unevenly. Some of your arrivals today were meant to land yesterday. Some of your departures today already left without their passengers. A chunk of your Thursday check-ins are currently rebooking onto flights that don't exist yet.
Two thousand and twenty-three cost the airlines north of £100 million in refunds and compensation. Nobody published what it cost hotels, because hotels didn't measure it. They just watched a bad week and blamed the weather.
The three ways hotels lose money on a day like this
One: you refund the no-show. Someone doesn't turn up, calls at 11pm, and a night manager with no guidance and a strong desire to avoid a bad review waives the first night. Do that thirty times across a portfolio and you've donated the week. The right answer is almost never a full refund. It's a date move with the rate held, which costs you close to nothing and buys goodwill that a refund doesn't.
Two: you panic and drop rates. Occupancy looks soft at 6pm, someone opens the extranet, and suddenly you're the cheapest four-star in the postcode on the exact night when stranded passengers with airline vouchers are hunting for anything with a bed. Disruption nights are demand events, not distress events. The people trying to book you at 9pm have no alternative and an airline paying. Holding rate is not gouging. Cutting rate on the night an ATC system fails is just handing money away for no gain, because inventory that close in sells on availability, not price.
Three: you staff the shift you planned instead of the shift you got. Late arrivals need a manned desk, a kitchen that hasn't shut, and somebody who can find a taxi at midnight. If your last F&B cover finished at nine and your night porter is alone with forty confused arrivals, the reviews you get are the ones you'll be paying for in Q4.
What to do today, in order
Pull your arrivals list for today and tomorrow and flag every booking with a flight number or an inbound from a UK airport. If you don't capture flight numbers at booking, that's the first thing to fix after this week.
Send one message to every arrival for today. Not a marketing email. One line: "We know today's flights are a mess. Your room is held, no matter what time you get here, and we'll sort food. Reply if you need to move a date." That message costs you nothing and it stops half the 11pm phone calls before they happen.
Set the cancellation position now, in writing, so the night manager doesn't have to invent one. Date move at held rate, yes. Refund, no. Escalation to a duty manager for anything else.
Call your closest sister property or a friendly competitor and agree a walk arrangement in both directions before you need it. Everyone in your comp set has the same problem today and half of them will be oversold by tonight.
And check your OTA connectivity. Cancellation and modification volume spikes hard after a disruption event, channel managers fall behind, and the fastest way to turn a good night into a disaster is to sell a room twice because your inventory didn't sync.
The uncomfortable bit
This is the third significant NATS failure in three years. August 2023, July 2025, September 2026. Whatever the CAA report says, the honest planning assumption is that it happens again, probably inside eighteen months, probably with no warning.
Which means the response should not be a decision you make on the day. It should be a trigger. When a UK airport goes into disruption, the same four things fire automatically: arrivals get messaged, rates get frozen, late food gets authorised, and a duty manager owns the desk until 2am. Written down, one page, taped inside the back office door.
Most hotels will read about yesterday, nod at the Ryanair quotes, feel briefly angry at NATS, and change nothing. The ones that write the page are the ones who will make money the next time a screen goes dark in Swanwick.
That's the whole difference. Not luck, and not location. Just having decided in advance.
