So yesterday morning every single flight in the country was grounded because of, as far as anyone can tell, a busted file sitting in a database somewhere in the bowels of the FAA. Not a hack. Not weather. A file got corrupted, the system that pushes out NOTAMs (Notice to Air Missions, they renamed it from Notice to Airmen a couple years back) fell over, and by 6:30 in the morning the FAA had ordered a full nationwide ground stop. Nothing left the runway anywhere in the US until around 9am Eastern. Thousands of delays, over a thousand flights canceled outright, and a whole news cycle of people speculating cyberattack before the FAA came out and said no, it looks like a damaged database file, not anything malicious.
I had a work trip booked out of Newark next month and my stomach did a little drop when I saw the news, even though it obviously had nothing to do with my flight. That's not really the point of this post though.
What I keep thinking about is that NOTAMs, the little bulletins that tell pilots "hey this runway's closed" or "this navigation beacon is down," run on a system that by most accounts is genuinely old. Not retro-cool old, just old in the bad way, the way government IT tends to be old. There's been talk for years about the NOTAM system needing a real overhaul and it just never happens because it's not broken until suddenly it is, spectacularly, and grounds every domestic departure in the largest air travel market on earth.
I don't think this is a story about the FAA being incompetent, for what it's worth. Big legacy systems like this are terrifying to touch. You've got decades of accumulated behavior, some of it undocumented, some of it held together by one guy who retired in 2004 and nobody fully understands why a certain job runs at 2am on Thursdays. You don't rewrite that from scratch, you patch around it forever, and every patch is one more thing that can eventually snap. I deal with a much, much smaller version of this at my own job — we've got an invoicing system from probably 2009 that nobody wants to touch because the guy who wrote most of it left years ago, and every time someone pokes at it something unrelated breaks. Multiply that by infinity and give it responsibility for national airspace and you get yesterday.
What's a little wild is how invisible this stuff usually is. Nobody thinks about NOTAMs. I didn't know what one was until yesterday, honestly, and I've been writing about tech on this blog since 2011. The whole apparatus of air travel runs on this quiet substrate of old government software that just works, silently, until one day it very much does not, and then it's the top story on every network for twelve hours and congressional hearings start getting scheduled. There's a pattern here that shows up everywhere in tech, not just aviation — the boring reliable infrastructure nobody thinks about is usually the stuff running on borrowed time, and the flashy new thing gets all the attention and funding while the load-bearing wall quietly rots.
CES wrapped up in Vegas a few days ago and I've seen approximately nine hundred posts about AI-this and screen-that from the show floor, which, fine, that's what CES is for. But I'd honestly rather read a good writeup of what actually went wrong inside the NOTAM system than another slideshow of concept EVs I'll never own. Somebody's going to write that piece eventually, probably months from now once there's an official report, and I'll be reading it.
Anyway. My flight next month is fine, the system's back up, air travel resumed like nothing happened by lunchtime. But it's a good reminder that a shocking amount of what keeps modern life running is old, patched-over, and one bad file away from a very bad morning. Worth remembering next time someone tells you legacy systems are a solved problem.