The Federal Aviation Administration (FAA) issued a nationwide ground stop for all U.S. airports on Friday, November 13, 2026, at approximately 20:54 UTC (3:54 p.m. Eastern Time). The order stated: “Due to extraordinary circumstances and for reasons of safety. Attention all aircraft operators, by order of the Federal Aviation Command Center all airports are ground stopped. All departing traffic should remain ground stopped until further notice. Inbound international flights will be managed on a case by case basis.”
Flights already airborne were permitted to continue to their destinations. International departures were handled on a case-by-case basis. The ground stop remained in effect into the evening, with the FAA outlining a tiered recovery plan as affected en-route facilities restored communications.
Technical Context: Role of the Air Route Traffic Control Centers
The United States operates 22 Air Route Traffic Control Centers (ARTCCs, or Centers). These facilities manage en-route traffic—aircraft in cruise at higher altitudes—between terminal areas. They are not located at airports. Each Center controls a defined volume of airspace and hands aircraft off to adjacent Centers or to approach control facilities near airports.
Primary communication is via radio frequencies (VHF/UHF). Controllers access these frequencies and ground lines through voice switches. Radar data and electronic flight strips are carried over the FAA’s Telecommunications Infrastructure (FTI), a private wide-area network operated by L3Harris that connects more than 4,400 sites. FTI includes optical backbones, metro rings, and redundancy features and is undergoing a multi-year transition from copper/TDM circuits to fiber and IP as part of the Brand New Air Traffic Control System (BNATCS) modernization program.
Controller and internal reports described the outage as loss of radio frequencies, with some facilities also losing radar and automation functions used for handoffs and flight strips. The problems began regionally—including at the Chicago, Boston, New York, and Washington Centers—before expanding to all or nearly all of the 22 Centers. The FAA later characterized the event as a “temporary telecommunications outage” and a “nationwide comms failure.”
Officially Stated and Investigated Possible Causes
The FAA and the Department of Transportation identified the immediate cause as a communications problem or telecommunications outage affecting the Air Route Traffic Control Centers. Transportation Secretary Sean Duffy stated: “The @FAAnews issued a nationwide ground stop for all U.S. airports following a communication issue impacting all Air Route Traffic Control Centers. FAA technicians are investigating the issue.” The FAA referred to “communication issues impacting multiple Air Route Traffic Control Centers” and later to a “temporary telecommunications outage.” Flights were halted out of an abundance of caution; the agency said every flight had been accounted for.
Homeland Security Secretary Markwayne Mullin said there was no indication of a “nefarious attack.” He described the event as a telecommunications outage and stated that airborne flights were being handled safely. He did not categorically rule out other possibilities.
According to Bloomberg, the FBI is examining whether a software update triggered the outage. The Bureau has not publicly confirmed the line of inquiry. The FAA has not identified the specific failed system or component.
Investigators are also looking at the AI-supported SMART system (Strategic Management of Airspace, Routes and Trajectories) supplied by Air Space Intelligence. SMART was expanded to all 22 ARTCCs on November 10, 2026. It aggregates roughly 200 data streams (weather, flight plans, staffing) and generates routing recommendations. The vendor stated that the ground stop “is not based on or a result of the SMART system, any product of ASI or our integration with FAA and ATC.” Secretary Mullin said officials were examining a possible link through the Cybersecurity and Infrastructure Security Agency (CISA) and were not ruling anything out at that stage.
Under the BNATCS program the FAA is systematically replacing radios, converting voice switches to VoIP, modernizing radars, and upgrading telecommunications. As of October 2026 the agency reported that roughly 68 percent of planned telecommunications connections had been replaced. Parallel work continues on the migration from time-division multiplexing to IP. Earlier Government Accountability Office reports had noted residual vulnerabilities in FTI redundancy, including cases in which primary and backup paths failed simultaneously.
Concurrent events without a confirmed connection include a Microsoft 365 outage and a National Weather Service radar outage. Secretary Mullin stated there was no reason to link the ground stop to the Microsoft incident.
Sequence and Operational Impact
Regional ground stops and frequency problems preceded the national order (including at Chicago O’Hare, Boston Approach, and Washington Center). The Air Traffic Control System Command Center extended flight-plan drop times to 240 minutes for all en-route Centers “due to nationwide comms failure.” A tiered release of traffic was planned as facilities recovered; the stop was initially set to run until 04:00 UTC (11:00 p.m. Eastern).
FlightAware and Flightradar24 reported more than 10,000 delays and approximately 1,900–2,000 cancellations by evening. At the moment the ground stop was issued, more than 4,000 flights were airborne and destined for U.S. airports; that number later declined sharply. Several major airports recorded no departures for hours.
Historical Context
This was the third nationwide ground stop since the September 11, 2001, attacks and the first since January 2023, when a failure of the Notice to Air Missions (NOTAM) system disrupted more than 10,000 flights. Air-ground communications, radar, and telecommunications systems have long been identified as requiring modernization; additional funding for infrastructure replacement has been allocated in the current period.
The precise technical root cause had not been conclusively determined at the time of this analysis. FAA technicians, the FBI, and CISA continued their investigations. The agency indicated that further updates would be provided.
