Airline Failure And Please Stop

(This column is posted at www.StevenSavage.com and Steve’s Tumblr.  Find out more at my newsletter, and all my social media at my linktr.ee)

So apparently I’m going to be writing more on current events lately. I’d like to think a little more broadly, but current events (here in November 2026) are very critical and very stupid. Besides, specifics sometimes teach us best about generalities because we have a concrete set of things to learn from.

So let’s talk the week of November 9th, 2026 CE. The week that saw assorted political dumbness, the Microsoft Outlook outage, and the FAA shutting down all air travel in the United States because some update or something crashed communications systems. I’m going to focus on the latter, even if I don’t think we have the full story. Trust me, it’s still relevant and because I need to get a rant out.

Don’t worry, there’s all sorts of great IT and Project Management lessons there because that’s what you come here for. Also because I need to do this. I work in IT, my friends work in IT, so the week I want to discuss was rough on me and everyone I know.

So there was SOME kind of upgrade going on at FAA communications, apparently multiple kinds. There was some AI rollout, there was a cabling switch a few weeks ago, a router switch, there’s probably other things going on that we may not know. At one point the US Government just grounded all air travel because their systems went down. I’ve read several summaries and don’t feel like we have the big picture.

Keep in mind this was on top of the Microsoft Outlook outage, while also being unrelated to it. I guess. I don’t know anymore.

So let me round up. There were SOME kind of upgrades going on in our air control systems. Some were recent. At the start of November. At the start of holiday season. ON A FRIDAY. And some things went wrong – apparently with routing technology at two locations – and we shut airspace down.

This is where I, the Project and Program Manager, the guy with over 30 years in IT, says simply “no.”

You don’t upgrade or alter systems vital systems on a FRIDAY. It’s an invitation to disaster because if something goes wrong, if they’re cascading effects, then you’ve created chaos. In fact we’re lucky that things broke NOW because if these upgrades or improvements or whatever happened and the bugs didn’t show up to later, it could have made Thanksgiving or Christmas much worse. Keep “Planes, Trains, and Automobiles” a comedy, people.

Holidays in fact are times you lock down. I’ve been there before. In fact I’m a believer that it’s a good idea to lock down systems from change twice a year no matter the organization. Make no changes unless forced. Spend a month making sure you’re caught up. Do nothing to your computer systems for a month unless there’s some critical issue you didn’t cause. It’s a good way to practice stability and get breathing room.

But instead I guess our government and the contractors they get kickbacks from decided it was time to upgrade systems.

If there was an emergency? Fine. Great. Then shut down or slow down a few systems. Have a plan. Let people know. Keep us informed. I mean what would they have to hide? Yeah I know the answer to that, but still, this is not how things are usually done in IT, or should be done.

If there was a need for upgrades? Do it earlier. Do it later. Do it incrementally (which it may have been) but sit down and find the idea time to do whatever yo you have to do to the software or physical infrastructure. Just not the holiday season. Or close to the holiday season like this.

Of course maybe all of the above was being done. Maybe there was a problem and the response by Sean Duffy was to shut all airspace down. Which seems a little extreme if some router in Arkansas and such goes down. We’ve had this happen before, we should have failover, we should be used to it. Stuff fails all the time, right?

Did we see someone panic-cancel all flights in America?

There was also no public engagement when people will understand. Airlines can adapt to slow down or spread flights out or understand. Explain the bug don’t make people keep guessing (I still am as I write this). People will usually guess WORSE than the actual situation, and if the situation IS Worse than the public is guessing, you need the public to help you out.

That tells me the people in charge are scared to discuss what’s going on, don’t know, or both. Makes me wonder how many sweetheart deals are out there. How much DOGE and other cuts affected flying. I can’t even guess at how bad things are so I’m going to assume the worst and I’m good at that.

So the FAA basically didn’t follow basic update procedures that any competent IT person knows, didn’t communicate, may have panicked, and created further mistrust. I’ve been advising people to reconsider flying for awhile, because right now I smell potential outages in the future because I’ve seen this all before.

Steven Savage