🔍 Read the full analysis: Why The FAA Stopped Flights Across The US—and What Remains Unknown on ThorstenMeyerAI.com
Get business pricing on tech for your team
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
TL;DR
The FAA stopped departures at U.S. airports on Nov. 13 after communications and radar instability affected air traffic facilities, according to Transportation Secretary Sean Duffy. The stop lasted about four hours and 23 minutes; officials said they had seen no evidence of a cyberattack, but had not ruled one out, and no written root-cause report was available in the source material.
The Federal Aviation Administration halted departures at U.S. airports on Friday, Nov. 13, after communications problems affected multiple air traffic control centers, disrupting flights nationwide for about four hours and 23 minutes. Transportation Secretary Sean Duffy said radar and communications systems became unstable; officials reported no evidence of a cyberattack at that point, but said they had not ruled one out.
The FAA Command Center issued its nationwide ground-stop advisory at 3:54 p.m. Eastern Time, directing departing aircraft to remain on the ground. Its notice cited “extraordinary circumstances and for reasons of safety.” In a statement, the FAA said communication issues were affecting multiple Air Route Traffic Control Centers and that technicians were investigating. The agency labeled its account preliminary and subject to change.
The disruption had begun to appear in Chicago-area advisories earlier in the afternoon. At 3:21 p.m., the Command Center warned of arrival delays and airborne holding at O’Hare because of equipment issues. It stopped departures to O’Hare at 3:28 p.m., citing equipment and communications problems; Chicago Midway followed at 3:31 p.m. Duffy said the broader problem began at 3:36 p.m. and affected en route centers and approach control facilities around the country.
Duffy said more than 3,500 aircraft were airborne when the ground stop began, falling to fewer than 400 by 8 p.m. He said medevac flights, life-saving cargo and law enforcement flights were permitted to continue. The FAA’s advisories describe extended flight-plan times and coordination with recovering facilities as flights were gradually released. The agency recorded the national stop’s cancellation at 8:19 p.m., with an effective time of 8:16 p.m.; Duffy said the airspace reopened at 8:15 p.m.
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
Disruption Reached Beyond U.S. Airports
A nationwide ground stop affects more than planes waiting to take off. Aircraft already in the air may need to hold or divert, while airlines must reset schedules, aircraft and crew assignments after departures resume. The stop therefore continued to affect travelers after the FAA lifted it, as carriers worked through the backlog.
FlightAware counted 9,159 cancellations within, into or out of the United States on Friday, and 3,515 additional cancellations by 7:58 a.m. ET Saturday. Those figures cover all cancellations in those periods; they do not isolate flights caused by the FAA stop. The source material also reports that European departures to the United States were suspended at the FAA’s request for a period, while Sydney Airport held US-bound flights and Air Canada cancelled some Canada-U.S. services.
The incident also highlights the consequences of relying on aging air traffic systems, though the exact equipment failure remains under investigation. Duffy warned that similar disruptions could occur without investment in a replacement system and called for $50 billion in funding. That is his stated position, not a finding that the requested amount would prevent another outage.
Products Worth Considering
Amazon Kindle Scribe (32GB) with Premium Pen, Tungsten (Like-New)
Bose QuietComfort Headphones – Wireless Bluetooth Over-Ear Noise Cancelling Headphones, Petal Pink Limited Edition
Kindle Paperwhite 16GB (2024 Model) – Graphite
As an affiliate, we earn on qualifying purchases.
From Chicago Advisories to a National Stop
The FAA’s public notices show the problem widening through the afternoon. Chicago was the first location in the supplied advisories to cite equipment issues. At 3:30 p.m., the Command Center activated a diversion recovery tool for all airports. The national stop followed 24 minutes later, with inbound international flights to be managed case by case.
As the disruption continued, the FAA warned at 4:20 p.m. that aircraft could face airborne holding at any airport. One minute later, it extended flight-plan drop times for all en route centers to 240 minutes, allowing filed plans to remain active longer while aircraft waited. At 5:46 p.m., the agency said flights would be released in coordination with the Command Center as en route facilities recovered. Some coastal facilities released international departures later that evening.
The source account describes 21 en route centers, citing a 2023 FAA-commissioned review. These centers largely manage aircraft traveling between airports, while approach control facilities manage traffic near airports. The supplied material does not include the underlying review or a detailed technical inventory of the equipment involved.
“We didn’t lose all telecom we didn’t lose all radar.”
— Transportation Secretary Sean Duffy
The Root Cause Has Not Been Published
The supplied source material does not include a written FAA root-cause report. It therefore remains unclear exactly which components failed, why they became unstable, and whether a specific technical or operational trigger caused the communications problems. Duffy attributed the issue to aging analog telecommunications switches and routers that became overloaded with data, but that account is not a published final investigative finding.
Mullin said officials had seen no evidence of a cyberattack and that the event appeared mechanically driven, while adding that investigators were not ruling out cyber activity. Duffy and the maker of the FAA’s new SMART air traffic tool said that system was not connected to the failed equipment. The source material does not provide a technical report independently documenting those assessments.
The cancellation totals also need qualification: the cited figures include all flight cancellations during the stated periods, not only those linked to the ground stop. The precise number of disrupted passengers and the full financial impact are not established in the supplied account.
FAA Investigation and Funding Debate
The FAA said technicians were investigating, but the supplied material gives no publication date for a final report or a specific next technical milestone. The central unanswered issue is what failed and what changes the agency will make to reduce the chance of another nationwide disruption.
Airlines and airports must continue handling schedule, aircraft and crew recovery after the stop. Travelers with affected flights should check directly with their carrier for current itinerary information; the broad cancellation counts do not show whether a particular flight was affected.
Duffy’s call for $50 billion to replace or upgrade the system puts the event into a wider funding debate. Whether Congress will approve that request, what the money would cover, and how quickly any upgrades could be implemented remain unresolved in the source material.
Key Questions
Why did the FAA stop departures across the United States?
The FAA said communication issues affected multiple air traffic control centers. Sean Duffy described instability in radar and communications systems at en route centers and approach control facilities.
How long did the nationwide ground stop last?
FAA advisory times indicate it ran from about 3:53 p.m. to 8:16 p.m. ET on Nov. 13, or roughly four hours and 23 minutes. Duffy said the airspace reopened at 8:15 p.m.
Was the disruption caused by a cyberattack?
Officials said they had seen no evidence of a cyberattack at the time, and Mullin said the problem appeared mechanically driven. He also said investigators would not rule cyber activity out. No final root-cause report is included in the source material.
How many flights were cancelled?
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. Those totals include cancellations for all reasons, not just those caused by the ground stop.
What is the FAA doing to prevent another stop?
The FAA said technicians were investigating, but the source material does not give a final report or a confirmed remediation plan. Duffy called for $50 billion in funding for a new system and warned that further disruptions could occur without investment.
Source: ThorstenMeyerAI.com
