FAA Communications Outage Halts Over 2,500 U.S. Flights; Cyberattack Not Evident
What Happened — On the afternoon of Friday, November 12 2026, the U.S. Federal Aviation Administration (FAA) issued a ground‑stop order just before 4 p.m. ET after a nationwide telecommunications outage knocked out the radio‑frequency links that feed flight‑hazard information to every Air Route Traffic Control Center (ARTCC). The outage forced operators to ground more than 2,500 flights, creating the most extensive U.S. air‑space disruption since the 2023 incident.
FAA officials quickly ruled out a cyberattack. Homeland Security Secretary Markwayne Mullin told reporters that “zero evidence” pointed to a malicious intrusion, and Transportation Secretary Sean Duffy emphasized that the newly‑deployed AI‑driven SMART system—intended to augment air‑traffic decision‑making—was not connected to the legacy STARS/ERAM platforms that failed.
The agency traced the failure to “old, old switches, old routers” and antiquated copper wiring dating back to the 1980s. These legacy network elements became overloaded, causing a cascade that knocked out the system that shares real‑time flight‑hazard data across the national airspace. Technicians worked through the evening to restore the links; the FAA lifted the ground‑stop at 8:30 p.m. ET, but full service recovery is expected to take several days.
The incident follows a recent Microsoft cloud‑service disruption, which the tech giant attributed to a network‑capacity upgrade and also denied any cyber‑attack link. While the FAA’s AI‑based SMART platform—designed to ingest 200 data streams and provide predictive traffic flow analysis—was rolled out three days earlier, officials confirmed it was not involved in the outage.
In a White House press briefing, Secretary Mullin cautioned that “you just can’t rule out anything at this point,” but reiterated that the current evidence points to aging infrastructure rather than malicious activity. The FAA announced plans to seek $50 billion in funding to modernize its air‑traffic control (ATC) communications architecture, replacing the obsolete hardware that precipitated the failure.
Why It Matters for Trust & Control Assurance — The event underscores the need for robust business‑continuity and disaster‑recovery controls that are continuously monitored and evidentially mapped to audit frameworks.
Who Is Affected — Aviation operators, airlines, passengers, and any organization that relies on U.S. air‑traffic services; broadly, the transportation and logistics sector.
Recommended Actions
- Review and test incident‑response and recovery procedures for critical communications infrastructure.
- Map continuity controls to the Verisq Common Framework (VCF) objectives for audit readiness and collect defensible evidence of resilience.
- Prioritize modernization of legacy network components and document the upgrade roadmap as part of governance risk management.
Source: DataBreachToday
Technical Notes
- Outage vector: failure of legacy copper‑based switches and routers, leading to overload of the flight‑hazard data distribution system.
- No CVEs or malware reported; investigation ongoing but no indication of a vulnerability exploit.
- Systems impacted: STARS (Standard Terminal Automation Replacement System) and ERAM (En Route Automation Modernization) communication links across all 22 ARTCCs.
- Recovery timeline: ground‑stop lifted after ~4 hours; full service restoration projected over several days.

