FAA Halts All U.S. Departing Flights After L3Harris Telecom Update Crash

The Three-Question Framework

What Happened?

At 3:54 p.m. ET (20:54 UTC) on November 13, 2026, the U.S. Federal Aviation Administration halted all departing flights nationwide citing a communications failure across Air Route Traffic Control Centers while 4,042 inbound and domestic flights were airborne.

Why It Matters

Rare nationwide ground stops have occurred only twice before since 2001, revealing how a single contractor-managed backbone—L3Harris's FAA Telecommunications Infrastructure linking over 4,400 sites—can freeze U.S. civil aviation and strand up to 400,000 travelers.

What Could Happen Next

Investigators from multiple U.S. agencies are examining why the FTI communications update crashed on reboot while FAA technicians stagger flight resumptions into November 14 to clear hub gate and taxiway bottlenecks.

Executive Key Takeaways

CBS News and The Register reported an update to L3Harris's FAA Telecommunications Infrastructure caused the network connecting more than 4,400 facilities to reboot and crash.

Flightradar24 counted 4,042 airborne U.S.-bound flights when the order landed, while Dartmouth professor Vikrant Vaze estimated 3,000 to 4,000 flights were delayed during the initial hours.

Homeland Security Secretary Markwayne Mullin and senior U.S. officials said early checks found no sign of cyberattack and no link to Microsoft's concurrent cloud outage.

FAA contractor Air Space Intelligence issued a public statement confirming its $875 million SMART traffic management software did not trigger the suspension.

Sources: NBC News live coverage of November 13, 2026, and The Register's reporting updated at 23:53 UTC.

The FAA Air Traffic Control System Command Center issued its advisory ordering every departing aircraft to remain parked until further notice, noting that inbound international traffic would be cleared on a case-by-case basis. According to NBC Chicago, both O'Hare and Midway airports had entered localized ground stops minutes earlier under an equipment outage notice before the restriction expanded across all high-altitude Air Route Traffic Control Centers.

Federal officials moved quickly to separate the failure from malicious activity or overlapping enterprise cloud troubles. Department of Homeland Security Secretary Markwayne Mullin attributed the disruption to a telecommunications outage and stated there was no indication of nefarious involvement, while U.S. Transportation Secretary Sean Duffy confirmed FAA technicians were troubleshooting communications across the regional control centers. Three senior federal officials told NBC News that early diagnostics showed neither cyberattack signatures nor any overlap with Microsoft's global M365 outage.

Inside crowded terminals and cockpits, the safety freeze rapidly cascaded into physical gridlock as landing jets filled gates vacated by no outgoing departures. LiveATC feeds captured controllers at Newark Liberty International Airport warning of severe gate congestion, while a source familiar with operations told NBC News that Reagan Washington National reached full parking capacity by 6:00 p.m. ET and Chicago O'Hare approached its limit. Aviation safety expert Jeff Guzzetti noted that backup radio relays kept airborne aircraft safely separated even as airport taxiways backed up.

Beyond L3Harris's legacy FTI backbone—where the contractor has not yet issued a public comment—FAA vendor Air Space Intelligence distanced its new $875 million, 12-year Strategic Management of Airspace, Routes and Trajectories (SMART) software from the incident on X. Exact root-cause forensics on the faulty network update remain incomplete pending formal FAA and L3Harris engineering disclosures.

The Three-Question Framework

What Happened?

Why It Matters

What Could Happen Next

Executive Key Takeaways

Primary Sources & Citations