The FAA Network That Keeps Failing

When all twenty-two US air route traffic control centers went dark together on Friday, the architecture told the story before the investigators could: they all ride the same wire. America's air traffic control does not run on twenty-two independent networks — it runs on one, a private contractor-operated backbone that has been failing regionally for eighteen months straight. Friday may simply be the day it failed nationally.

The network nobody's heard of

The FAA Telecommunications Infrastructure (FTI) is the connective tissue of the National Airspace System: a private, nationwide wide-area network designed, built, owned, operated and maintained by L3Harris under a managed-services contract. Per L3Harris's own program literature, it interconnects more than 4,400 FAA sites carrying more than 29,000 telecommunications services — voice, data, radar and video — spanning terrestrial, satellite and microwave last-mile links, marketed at 99.99971% reliability. Critically, L3Harris owns the equipment and leases the underlying telecom capacity: when the FAA's systems talk to each other, they are talking over a contractor's wires.^[1]

The parade of failures

Regional versions of Friday's event have been arriving on a near-monthly cadence — every one mundane, every one instructive:

• Spring 2025 — Philadelphia. Repeated radar outages at Philadelphia TRACON; in one incident the facility lost both primary and backup data lines simultaneously. AP traced a failure to a switch on the primary communications line.^[2]
• June 2025 — Jacksonville ARTCC. A fiber cut took radar, frequencies and automation offline; L3Harris and the local exchange carrier were dispatched to repair it.^[3]
• September 19, 2026 — Dallas. Frontier Communications crews accidentally severed two fiber cables carrying both primary and backup links into Dallas TRACON — and L3Harris's redundancy failed to operate correctly. Hundreds of flights canceled, 100,000+ travelers stranded.^[4]
• September 21–23, 2026 — Philadelphia again. Error messages on a telecom circuit prompted L3Harris to shift to a backup fiber line; the resulting outage still snarled thousands of East Coast flights.^[5]
• November 13, 2026 — everywhere. The same failure signature, now at all 22 centers simultaneously: a "telecommunications outage," per DHS.^[6]

Why the redundancy keeps failing

The recurring theme across these events is not a single weak link — it is designed redundancy that doesn't survive contact: two fiber paths cut in the same trench (Dallas), a backup that doesn't take over cleanly (Philadelphia, Dallas), maintenance on a primary that exposes a fragile secondary (September). FAA officials have conceded that much of the system still runs on decades-old infrastructure dependent on external telecom providers, patched and upgraded but retaining analog-era equipment.^[4]

A shared backbone is efficient exactly until it isn't. Every regional event since mid-2025 was a dress rehearsal: the blast radius grows only because the dependency is national. A single backbone fault touching all 22 centers produces the observed signature — a simultaneous national stop — with no adversary required.

What it means for the investigation

Friday's event is unremarkable in everything except scale — and scale is what a common-mode failure looks like when it finally happens. The companion analysis arguing this is the most probable explanation is at Why The Skies Went Dark; the case that the same signature could conceal a demonstration attack — since living-off-the-land intrusions are built to look like faults — is at Chinas First Cyber Pearl Harbor. Both rest on the same uncomfortable truth this article documents: the FAA cannot currently tell the difference between its own decay and someone else's work.

See also

• FAA Grounds All US Flights November 13 — hub coverage
• What Is SMART FAA AI Air Traffic System — the new variable riding the same backbone
• Every Time America Grounded Every Flight
• ALB Wiki Launches News