Live coverage of the FAA nationwide ground stop, 13 November 2026Last checked: Monday 16 November 2026, about 05:30 ET
Home › Government Shutdown Flight Cuts: The 40 Airports
FAA Ground Stop · 13 Nov 2026

Government Shutdown Flight Cuts: The 40 Airports

Before the ground stop, the FAA had already ordered airlines to cut flights at 40 airports because of the government shutdown. The cuts and the stop happened in the same week, at the same airports, and they are constantly confused. They were different events, with different causes and different remedies. This page separates them.

In short

During the 43-day government shutdown of 1 October to 12 November 2025, the FAA ordered airlines to cut flights at 40 major airports: 4 percent from 7 November, raised to 6 percent on 10 November, then eased to 3 percent on 15 November. About 13,000 air traffic controllers worked without pay during the shutdown. The cuts were a planned, scheduled reduction to ease pressure on a short-staffed, unpaid workforce. The ground stop on 13 November 2026 was a different event: an emergency halt of all departures, ordered without warning because the communications network was failing. The shutdown ended the day before the ground stop; the cuts were eased the day after it.

The cuts: 4 percent, then 6 percent, then 3 percent

The sequence is the clearest way to tell the cuts from the stop. On 7 November, the FAA ordered airlines to cut flights at 40 major airports by 4 percent. On 10 November, the cut was raised to 6 percent. On 15 November, two days after the ground stop, the cut was eased to 3 percent. The cuts were scheduled reductions: airlines removed flights from their schedules in advance, passengers were notified, and the remaining flights operated normally. The ground stop was the opposite: no notice, no schedule, all departures held at once. The 40 airports were the country's busiest — Atlanta, Chicago O'Hare, Dallas-Fort Worth, Denver, New York's airports, Los Angeles, Miami, Charlotte, Phoenix, Las Vegas, Seattle, San Francisco, Boston, Washington's airports and others — which is why the two disruptions overlapped so completely in the public mind.

Why the cuts were ordered

The cuts were ordered because the shutdown left the air traffic control workforce working without pay and already short-staffed. About 13,000 controllers worked unpaid during the 43-day shutdown, on top of a pre-existing shortfall of roughly 3,000 controllers. The FAA's judgment was that the system could not safely handle full traffic with an unpaid, stretched workforce, so it reduced traffic to a level the workforce could handle. The cuts were therefore a safety measure of a different kind from the ground stop: a planned reduction to match capacity to staffing, rather than an emergency halt to match traffic to a failing network. The shutdown ended on 12 November, the day before the ground stop, which is why the cuts were eased to 3 percent on 15 November — the workforce was being paid again, and the pressure was lifting.

How the cuts and the stop interacted

The cuts and the stop interacted in two ways. First, the cuts had already thinned the schedule before the stop, which meant there was less slack in the system when the stop hit: fewer spare aircraft, fewer spare crews, fewer empty seats to rebook passengers onto. Second, the cuts complicated the recovery: the airlines were rebuilding their schedules from a reduced base, not from a full one, and the repositioning flights competed with the scheduled flights that remained. The two disruptions also interacted in the public mind, where they merged into a single story about a failing system. That merger is understandable but misleading: the cuts were a response to a political failure — a shutdown — and the stop was a response to a technical failure — a router. Fixing one does not fix the other.

The funding deadline

The shutdown's end did not end the funding question. The continuing resolution that funded the government runs through 11 December 2026, and a lapse would begin on 12 December if no full-year bills or stopgap pass. That deadline falls after Thanksgiving, which is why the Thanksgiving travel advice on this site is not affected by it — but a traveller booking for December should know that the funding question is open. The fact sheet notes later lapses in the record — a 4-day lapse in January to February 2026 and a 76-day Homeland Security-only lapse from February to April 2026 — but those appear only in secondary summaries and are not independently verified here, so they are not stated as settled fact on this site.

Frequently asked questions

A planned reduction in flights at 40 major airports during the government shutdown: 4 percent from 7 November, raised to 6 percent on 10 November, then eased to 3 percent on 15 November.

The 40 busiest airports, including Atlanta, Chicago O'Hare, Dallas-Fort Worth, Denver, New York's airports, Los Angeles, Miami, Charlotte, Phoenix, Las Vegas, Seattle, San Francisco, Boston and Washington's airports.

No. The cuts were a planned, scheduled reduction because of the shutdown. The ground stop was an emergency halt of all departures because the communications network was failing.

On 12 November, the day before the ground stop. The cuts were eased to 3 percent on 15 November.

The continuing resolution funds the government through 11 December 2026. A lapse would begin on 12 December if no further funding passes.

Sources & check time. Shutdown and flight-cuts coverage via nationwire, flyingwith and theairportguide24; Dave Manuel (continuing resolution through 11 Dec 2026). Shutdown year corrected to 2025 on 16 Nov 2026 (fact sheet, section 19). Last checked about 05:30 ET, Mon 16 Nov 2026.
Figures are given with their snapshot time and source. Developing items are marked as developing. Last checked Monday 16 November 2026, about 05:30 ET.