The November 2025 Shutdown Nearly Broke the U.S. Sky

The November 2025 Shutdown Nearly Broke the U.S. Sky

Eighteen of 22 air traffic controllers at Atlanta's Hartsfield-Jackson didn't show up for work on Sunday, November 9, 2025. Not because of a storm. Not because of a strike. Because they hadn't been paid in over six weeks — and, as Transportation Secretary Sean Duffy put it bluntly on CNN, they were "making decisions to feed their families."

That single staffing collapse at the country's busiest airport set off a cascade that grounded more than 2,900 flights and caused over 10,000 delays on Sunday alone. By Monday, over 1,500 more flights were canceled, with another 1,400 delayed. The FAA had already announced restrictions on all aviation operations, including general aviation, at 40 U.S. airports — and then issued further restrictions that would effectively prohibit business aviation operations at 12 of those airports. The hardest-hit airports included Atlanta, Newark, Chicago O'Hare, Houston, and New York's JFK. The hub-and-spoke system that makes American air travel efficient in normal times became a chain of dominoes: one understaffed tower, and the cancellations roll coast to coast.

American Airlines COO David Seymour sent a memo to employees that didn't mince words: "This weekend's operation was incredibly challenging for our industry, for our customers, for our airline and for you, our team members. This is simply unacceptable, and everyone deserves better." He acknowledged "concrete progress" in Washington talks but warned that "the next several days will continue to be challenging." Treasury Secretary Scott Bessent separately warned on ABC that economic growth for the quarter could be cut by as much as half if the shutdown continued — and that cargo slowdowns could produce holiday shortages, given that roughly 10% of U.S. cargo moves by air.

Duffy's warning about Thanksgiving wasn't hypothetical: the shutdown had already hit 37 days, making it the longest in U.S. history, and the FAA was short between 2,000 and 3,000 air traffic controllers nationwide. TSA had already closed two security checkpoints in Philadelphia due to staffing shortages, and Houston airport security lines were stretching out the door.

If you had a flight that week, "the government is still negotiating" was the only explanation you got — and no gate agent could tell you when it would end.

Gobble's Take: A budget standoff in Washington doesn't stay in Washington — it lands on your gate screen as a cancellation notice while you're already at the airport.

Sources: Fox News · CBS News · Tour de Kay

Shutdown Chaos: Practical Advice That Held Up

When the shutdown hit the 37-day mark in October 2026, a few practical guides cut through the noise. The clearest advice: if your trip was short-haul — think a Los Angeles–Las Vegas or San Francisco–LA hop — driving or taking a train was almost certainly faster than waiting out the cancellation queue. For longer routes, booking nonstop was the single best hedge, because one-stop itineraries were the first to get cut when airlines trimmed schedules.

The airports absorbing the worst of it were the ones travelers should have been watching most closely: Chicago O'Hare, Newark, JFK, Houston, and Atlanta. Routes between major hubs that normally run a dozen flights a day — like New York to Miami — risked being reduced to a handful, or fewer. Domestic flights bore the brunt because they depend on the tight, high-frequency scheduling that falls apart fastest when ATC staffing thins out.

The most actionable insight: FAA flow-control cuts targeted busy hub markets, so travelers connecting through a hub faced compounding risk — their inbound leg might make it, but the connection might already be gone.

Gobble's Take: Nonstop isn't just a convenience upgrade when the system is cracking — it's the difference between getting there and sleeping in terminal C.

Source: Tour de Kay

What It Takes to Actually Close a U.S. Airport

According to a documented catalog of U.S. aviation events since 2000, there have been at least 14 "closure-class" events where flights were broadly halted because safe operations couldn't be assured. That verified lower bound includes today's El Paso shutdown.

The causes break down as follows: five events stemmed from technical failures or loss of critical systems — including cascading power failures and FAA safety-information outages. Three were triggered by credible drone sightings near approach paths. Two were hurricane-driven multi-day shutdowns. Three were security or terrorism-related actions — most notably the national shutdown on 9/11, plus an airport-wide shooting incident and today's El Paso "special security reasons" TFR. One was an accident response that temporarily closed a major international airport (SFO).

Closure-class events are dominated by sudden, hard-to-predict tail risks — a security decision made in minutes, an IT failure, or a drone sighting that forces a ground stop before the threat is confirmed.

Gobble's Take: Closure-class events span five distinct cause types — knowing the pattern is more useful than assuming weather is your biggest risk.

Source: Brendon Beebe / Substack

FAA Flight Reductions During November Shutdown: What Travelers Faced

Writing on Sunday, November 9 — Day Three of the FAA's shutdown-era schedule — aviation analyst James Fallows documented the real-time impact of federally mandated flight reductions at the nation's busiest hub airports. Under the FAA's Emergency Order, airlines were required to cut flights by 4% in the first days, with cuts set to reach 10% the following week.

Fallows reported departure boards showing preemptively cancelled flights and multi-hour delays across remaining departures. At Newark alone, inbound flights faced an average of 134 minutes of flow-control delay, with outbound flights waiting more than 75 minutes for takeoff clearance — and that was still at the introductory 4% cut level.

Because of the hub-and-spoke model, flow limits at a single major airport ripple across travelers nationwide.

Gobble's Take: A 4% cut at one hub produced two-hour delays system-wide. The 10% week hadn't even started yet.

Source: Fallows / Substack

In Case You Missed It

Yesterday's top stories:

• Four Hubs, One Ugly Day: New York, Charlotte, Denver, and San Francisco Are All Clogged at Once
• Spirit's Gone — and Your Cheap Fare Search May Have Gone With It
• Taipei's Songshan Airport: 34 Delays, 13 Cancellations, and a Full Day Derailed
• A United Flight Got Diverted to Dulles. One Passenger. Everyone Else's Problem.