🔍 Read the full analysis: What Failed During The FAA’s US-Wide Flight Pause? on ThorstenMeyerAI.com
Get business pricing on office and shipping supplies
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
TL;DR
The FAA halted departures across U.S. airports on Nov. 13 after communication and radar instability affected air traffic control facilities. Transportation Secretary Sean Duffy blamed overloaded older telecom switches and routers, but authorities have not published a written root-cause report and say a cyberattack has not been ruled out.
The Federal Aviation Administration halted departures from airports across the United States for just over four hours on Nov. 13 after communication problems and radar instability affected air traffic control facilities. Transportation Secretary Sean Duffy said older telecom switches and routers became overloaded and supplied inconsistent data, but the FAA has not released a written report establishing the precise root cause.
The FAA Command Center’s advisories show equipment trouble first affecting Chicago-area flights. At 3:21 p.m. ET, the center cited equipment issues for arrival delays and airborne holding at O’Hare. It restricted departures to O’Hare at 3:28 p.m., describing the cause as an equipment outage and “comms issues”; Midway followed at 3:31 p.m. The national ground stop took effect at about 3:53 p.m. and was announced one minute later.
Duffy said the broader problem began at 3:36 p.m., affecting radar and communications at en route centers and approach control facilities around the country. He said the system did not lose all radar or telecom service, but the inconsistent information made it unsafe to continue normal departures. FAA advisories cited a “nationwide comms failure” and later a “communications failure.” The agency said technicians were investigating, and labeled its public account preliminary.
More than 3,500 aircraft were airborne when the ground stop began, according to Duffy; he said fewer than 400 remained in the air by 8 p.m. Medevac flights, life-saving cargo and law enforcement flights were permitted to operate. The FAA’s cancellation notice records the stop ending at 8:16 p.m.; Duffy said the airspace reopened at 8:15 p.m. Recovery continued afterward, with airport- and airline-specific restrictions as carriers repositioned planes and crews.
FAA ground stop · Nov 13, 2026 · times ET (UTC−5)
Unreliable data, a full stop, a slow restart
What the FAA Command Center’s advisories and Transportation Secretary Sean Duffy describe, step by step.
US airspace (schematic)
plane (schematic)airports
3,500+ planes in the airwhen the stop began, Duffy says Fewer than 400still airborne by 8 p.m. ET, Duffy says Restartground stop cancelled; flights resume slowly
What the FAA and Duffy said
- 3:21 p.m.Chicago O’Hare: arrival delays “due to equipment issues”FAA advisory 106
- 3:36 p.m.Radar and communications unstable at centers and TRACONs nationwideDuffy
- 3:54 p.m.“All airports are ground stopped”; departures heldFAA advisory 111
- 4:20 p.m.Airborne holding expected at “any and all airports”FAA advisory 116
- 8 p.m.Fewer than 400 planes still airborne, down from 3,500+Duffy
- 8:16 p.m.Nationwide ground stop cancelled; Duffy: airspace reopened at 8:15 p.m.FAA advisory 005
Sources: FAA Air Traffic Control System Command Center advisories 106, 111 and 116 (Nov 13) and 005 (Nov 14, 2026, UTC dates); Transportation Secretary Sean Duffy at the White House briefing, Nov 13 (transcript: Roll Call Factba.se) and on X (as quoted by Fox Business); BBC News, Nov 14. Durations: own calculation from advisory event times (2026: 20:53 to 01:16 UTC; 2023: 12:20 to 14:00 UTC). The radar picture is a schematic, not real traffic.
Graphic: Powered by Thorsten Meyer AI
How the Failure Disrupted Air Travel
The ground stop affected more than U.S. departures. According to the supplied account, European air traffic manager Eurocontrol suspended US-bound departures from its member states at the FAA’s request from 22:00 UTC on Nov. 13 until 05:00 UTC on Nov. 14. The account also says Sydney Airport held US-bound flights and Air Canada cancelled flights between Canada and the United States. Those measures show how a disruption in U.S. air traffic control can affect routes and schedules abroad.
FlightAware counted 9,159 cancellations within, into or out of the United States on Friday, and 3,515 more by 7:58 a.m. ET Saturday. These totals include all cancellations on those days, not just cancellations caused by the FAA ground stop, so they do not measure the stop’s direct impact. Even with that limitation, the episode highlights how delays can persist after an operational restriction is lifted: aircraft and crews may be out of position, and airlines must rebuild schedules.
The incident also puts attention on the reliability of air traffic control communications and the cost of replacing aging infrastructure. Duffy has argued that Congress should fund a new system, but his request for $50 billion is a policy position, not a confirmed estimate of the repair cost for this incident. For passengers, the immediate concern is the possibility of further delays if systems fail again; the specific risk and timeline remain unknown.
Popular right now
Ninja Flip Toaster Oven and Air Fryer SP151
KitchenAid 3-Piece Pasta Roller and Cutter Set for Stand Mixers
Dyson V8 Cyclone Cordless Vacuum
As an affiliate, we earn on qualifying purchases.
From Chicago Equipment Alerts to a U.S. Stop
The Command Center advisories trace a progression from local disruption to a nationwide halt. After the Chicago-area restrictions, the FAA enabled a diversion recovery tool for all airports at 3:30 p.m. At 4:20 p.m., it warned that aircraft could be held in the air at any airport. One minute later, it extended flight-plan drop times at all en route centers to 240 minutes, allowing filed plans to remain active longer while flights waited on the ground.
At 5:46 p.m., the FAA said departures would be released as en route facilities recovered, in coordination with the Command Center. By 7:37 p.m., some coastal facilities were releasing international departures. The national restriction was cancelled at 8:16 p.m., according to the advisory’s event time. The supplied material describes this as the longest nationwide ground stop since the Sept. 11, 2001, attacks, citing BBC News.
FAA-commissioned research published in 2023 counted 21 en route centers, which largely control aircraft traveling between airports. The FAA’s Nov. 13 statement attributed the pause to communication issues affecting multiple Air Route Traffic Control Centers. Its initial statement did not provide a detailed technical explanation; Duffy’s remarks offered the account of overloaded older equipment.
“We didn’t lose all telecom we didn’t lose all radar.”
— Transportation Secretary Sean Duffy
The Root Cause Is Still Under Review
The precise technical failure has not been established in a published root-cause report. Duffy attributed the inconsistent data to older analog telecom switches and routers that became overloaded, but the FAA’s public statement was preliminary and said technicians were still investigating. The material does not identify a specific component, software process or initiating event that caused the reported instability.
Mullin said officials had found “zero evidence” of a cyberattack and that the problem appeared mechanically driven, while explicitly declining to rule out an attack. Duffy and the maker of the FAA’s new SMART traffic tool said SMART was not connected to the failed equipment. The source material also says the previous day’s Microsoft outage was among the early speculation, but provides no evidence linking it to the FAA disruption.
FlightAware’s daily cancellation counts cannot establish how many cancellations resulted directly from the ground stop. Nor do the available details quantify the total delay, passenger count or financial losses attributable to the incident. Those impacts should not be inferred from the broader daily totals.
FAA Investigation and System Funding
The FAA’s next stated step is to investigate the communications issue; the source material does not give a publication date for findings or identify a specific technical repair deadline. A written account of the failure would help clarify which facilities and equipment were affected, how the overload developed and what safeguards could prevent a repeat.
Duffy has called for $50 billion in congressional funding for a new air traffic control system and warned that disruptions could happen again without investment. Congress has not, in the supplied material, approved that funding, and the figure is Duffy’s request rather than a confirmed cost for this incident. Airlines continued handling airport- and carrier-specific restrictions after the nationwide stop ended, while passengers faced schedule changes as flights and crews were repositioned.
Key Questions
What caused the FAA to stop departures?
The FAA cited communication issues affecting multiple air traffic control centers. Transportation Secretary Sean Duffy said radar and communications became unstable and blamed overloaded older telecom switches and routers. A final written root-cause report was not available in the supplied material.
How long did the nationwide ground stop last?
The FAA’s advisories place the start at about 3:53 p.m. ET and the cancellation at 8:16 p.m. ET on Nov. 13, a little over four hours. Duffy said the airspace reopened at 8:15 p.m.
Was the disruption caused by a cyberattack?
Officials had not established that. Homeland Security Secretary Markwayne Mullin said there was “zero evidence” of a cyberattack at the time but said officials were not ruling one out.
Did the FAA’s new AI traffic tool cause the problem?
No connection was reported in the source material. Duffy and the maker of the FAA’s SMART traffic tool said it was not connected to the equipment involved in the failure.
How many flights were cancelled because of the stop?
The direct number is not stated. FlightAware counted 9,159 cancellations within, into or out of the United States on Friday, but that total includes cancellations for all reasons that day and cannot be treated as the number caused by the FAA ground stop.
Source: ThorstenMeyerAI.com
