TL;DR
The FAA halted departures nationwide on Nov. 13 after reported radar and communications instability at facilities across the country. Transportation Secretary Sean Duffy attributed the disruption to overloaded legacy telecom equipment, while officials said they had seen no evidence of a cyberattack. The FAA has not published a written root-cause report.
The Federal Aviation Administration halted departures at airports nationwide on Nov. 13 after radar and communications instability affected air traffic facilities, grounding flights for about four hours and 23 minutes. Transportation Secretary Sean Duffy said the problem involved overloaded legacy telecommunications equipment, but the FAA has not released a written report establishing the root cause.
Get the latest gadgets delivered free with Prime
- Fast, free delivery on millions of items
- Prime Video, Amazon Music and more included
- Member-only deals all year
The FAA Air Traffic Control System Command Center’s advisories show equipment problems affecting Chicago flights before the nationwide order. At 3:21 p.m. Eastern Time, the center cited equipment issues in an advisory about delays at Chicago O’Hare. It then restricted departures to O’Hare and Chicago Midway. Duffy said the broader instability began at 3:36 p.m., affecting radar and communications at en route centers and terminal radar approach control facilities around the country.
At 3:54 p.m., the Command Center ordered all airports to hold departing traffic, citing “extraordinary circumstances and for reasons of safety.” The order also warned that aircraft could be held in the air. Duffy said more than 3,500 planes were airborne when the stop began and fewer than 400 remained in the air by 8 p.m. Medevac flights, life-saving cargo and law enforcement flights were allowed to continue, according to the source account.
The FAA’s cancellation advisory was issued at 8:16 p.m. ET; Duffy said airspace reopened at 8:15 p.m. The stop’s duration, calculated from the advisory times, was about 4 hours and 23 minutes. FlightAware counted 9,159 cancellations within, into or out of the United States on Friday and 3,515 more by 7:58 a.m. Saturday. Those figures cover all cancellations during those periods and are not a count of flights caused solely by the FAA order.
A Disruption With Nationwide Reach
The ground stop affected flights across the country because departures were held while air traffic officials dealt with unreliable radar and communications data. Even after the order ended, airlines and airports faced the task of resuming operations amid delays and cancellations. The reported cancellation totals show the scale of the disruption across the travel system, though they do not isolate the stop’s direct contribution.
The incident also highlights how air travel depends on communications and surveillance systems working reliably across multiple facilities. Duffy warned that similar disruptions could occur without investment in a replacement system and said he wants $50 billion from Congress. That is his stated position; the source material does not establish whether Congress will provide the funding or what specific upgrades would be made.
Products Worth Considering
Amazon Kindle Paperwhite (2024, 16 GB) – 7-inch Display, Black
Samsung Galaxy Tab A11+ Kids Edition, 128 GB Android Tablet, Royal Blue
LG UltraGear evo 27-inch 5K Mini-LED Gaming Monitor
As an affiliate, we earn on qualifying purchases.
From Chicago Delays to a National Halt
The FAA’s advisories trace the first equipment-related disruption in the account to O’Hare. At 3:28 p.m. ET, the Command Center restricted departures to the airport from across the United States and several Canadian airports, labeling the cause “equipment / outage” and the comment “comms issues.” Chicago Midway followed shortly afterward. At 3:30 p.m., the center activated its diversion recovery tool for all airports.
The nationwide order followed less than half an hour later. BBC News described the roughly 4-hour-23-minute halt as the longest nationwide ground stop since the Sept. 11, 2001, attacks. The source account says the only other nationwide stop since then was in January 2023 and lasted about 1 hour and 40 minutes. These comparisons are attributed to BBC News and calculations based on FAA advisory event times.
Duffy said older analog telecommunications switches and routers became overloaded with data and delivered inconsistent information. He said the system did not lose all radar or telecommunications service. The source also says Duffy and the maker of the FAA’s SMART traffic tool stated that SMART was not connected to the equipment that failed.
““ALL AIRPORTS ARE GROUND STOPPED.””
— FAA Air Traffic Control System Command Center
The Cause Has Not Been Documented
No written root-cause report has been published in the source material. Duffy attributed the instability to overloaded legacy switches and routers, but the details needed to independently assess the failure, its precise scope and how it was resolved remain unavailable here. Mullin said officials had seen no evidence of a cyberattack while also declining to rule one out, so that possibility was not definitively closed.
The source account says the FAA’s SMART traffic tool was not connected to the failed equipment, according to Duffy and the tool’s maker. It does not provide a technical account of the systems involved or a post-incident review. The cancellation figures also do not specify how many cancellations were directly caused by the ground stop.
Funding and a Root-Cause Review
The next key information would be an FAA account of what failed, how the agency restored reliable radar and communications, and what changes are planned to reduce the chance of recurrence. The source material does not give a publication date for such a report or describe a specific FAA review schedule.
Duffy has called for $50 billion in congressional funding for a new system and warned of further disruptions without it. Whether lawmakers will act, what system would be replaced or upgraded, and when any changes could take effect remain unsettled.
Key Questions
When did the FAA ground stop begin and end?
The nationwide order was issued at 3:54 p.m. ET on Nov. 13. The FAA’s cancellation advisory was issued at 8:16 p.m.; Duffy said airspace reopened at 8:15 p.m.
What caused the ground stop?
Duffy attributed the disruption to radar and communications instability and said legacy telecommunications switches and routers were overloaded with data. The FAA had not published a written root-cause report in the source material.
Was the disruption caused by a cyberattack?
Homeland Security Secretary Markwayne Mullin said officials had seen “zero evidence” of a cyberattack and that the issue appeared mechanically driven, while saying they would not rule a cyberattack out.
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 all cancellations during the periods, not only those attributed to the ground stop.
Could another nationwide ground stop happen?
Duffy warned that more disruptions could occur without investment in a new system and requested $50 billion from Congress. The source material does not establish whether Congress will fund the proposal or predict when another disruption might happen.
Source: Thorsten Meyer AI
