Why The Skies Went Dark

Every alarming explanation for Friday's nationwide ground stop has to beat a boring one first — and the boring one is very strong. The most likely cause of the 13 November outage is not a foreign cyberattack. It is the same failure the FAA has been having, publicly and repeatedly, for three years: a fault in the shared telecommunications backbone that all twenty-two air route traffic control centers depend on, possibly tangled with a new software rollout the agency itself flagged within hours.

This article makes that case. The companion piece — Chinas First Cyber Pearl Harbor — argues the other side.

The machine that failed, probably

U.S. air traffic control does not run on twenty-two independent networks. The Air Route Traffic Control Centers, radar sites, towers and radio links ride a single contractor-operated wide-area network: the FAA Telecommunications Infrastructure, or FTI, designed, built, owned and operated by L3Harris under a managed-services contract. L3Harris's own program literature describes a private WAN interconnecting over 4,400 FAA sites with over 29,000 telecommunications services, marketed at 99.99971% reliability.^[1]

That architecture is the tell. A failure in one ARTCC's local systems grounds one region. A failure in all twenty-two at once — which is what Transportation Secretary Duffy described Friday — is not twenty-two failures; it is one failure in the thing all twenty-two share. The observed signature of Friday's event, a simultaneous communication loss across every en-route center, points at the backbone by shape alone, before any forensics.^[2]

The FAA has this exact outage constantly

This is the part of the story that gets lost in the novelty of a nationwide stop: regional versions of this failure have been arriving on a near-monthly cadence, and every one of them has resolved to mundane infrastructure causes.

• January 11, 2023 — the only other nationwide stop since 9/11. The NOTAM database failed, the FAA ground-stopped every departure in the country, and the public immediately suspected a cyberattack. The cause, per the FAA's own preliminary review and the acting administrator's Senate testimony: contract personnel unintentionally deleted files while correcting synchronization between the primary and backup databases, producing "a cascading series of IT failures." No evidence of a cyberattack was ever found.^[3][4][5]

• Spring 2025 — Philadelphia. The Philadelphia TRACON suffered repeated radar outages; in one incident the same facility lost both its primary and backup data lines simultaneously. The Associated Press traced it to a failed switch on the primary communications line.^[6]

• June 2025 — Jacksonville ARTCC. A fiber cut in Florida took radar, frequencies and automation offline; L3Harris and the local exchange carrier were dispatched to repair it.^[7]

• September 19, 2026 — Dallas. Frontier Communications crews accidentally severed two fiber cables carrying both the primary and backup data links into Dallas TRACON, and L3Harris's redundancy failed to operate correctly. Hundreds of flights canceled, more than 100,000 travelers stranded.^[8]

• September 21–23, 2026 — Philadelphia again, four days before this writing. Error messages on a telecommunications circuit prompted L3Harris to shift an East Coast facility to a backup fiber line — and the resulting outage still snarled thousands of flights.^[9]

FAA officials themselves have conceded the underlying disease: much of the U.S. air traffic system runs on decades-old infrastructure dependent on external telecom providers, patched and upgraded but still carrying analog-era equipment.^[8] A senior official described the 2023 NOTAM collapse to ABC News the same way — "antiquated software overdue for replacement inside a critical IT network."^[10]

Five documented telecom-driven outages in eighteen months, two of them in the last eight weeks, every one resolved to fiber cuts, failed switches, deleted files or broken redundancy. A system failing regionally every few weeks will, on a long enough timeline, fail nationally once. That is not a conspiracy — it is the failure curve.

The second suspect: the FAA's own new system

There is one genuinely new variable, and the government named it themselves. DHS Secretary Mullin said investigators would examine any link to the FAA's SMART system — Strategic Management of Airspace Routing Trajectories — the AI-backed routing-advisory platform whose wider rollout began in September.^[2][11]

SMART is architecturally a poor attack target and a plausible accident cause: it runs from one site near Washington and only recommends routes to the centers — but a new software system feeding all twenty-two centers is precisely the kind of shared dependency that turns a single bad state into a simultaneous national fault. If Friday's failure traces to a software push, a poisoned data feed, or a cascade triggered by SMART's inputs, the story will rhyme with 2023's deleted files: a self-inflicted wound, not an enemy's.

Why "no evidence of attack" actually means something here

Skeptics will note — correctly — that absence of evidence is not evidence of absence, and the companion article lays out why a pre-positioned actor would want to look exactly like this. But three features of Friday's response cut against the attack reading, and they are worth stating plainly.

First, the diagnosis was immediate and specific. Within hours, DHS was calling it a "telecommunications outage" in a named infrastructure domain — not "an incident under investigation." Agencies do not produce a fault domain that fast when they see something they cannot explain; the 2023 NOTAM event took days to diagnose precisely because it was a genuine mystery.

Second, nothing demanded attention. Every disruptive infrastructure attack on record either claims credit (hacktivists want propaganda value) or produces escalating physical effect (state actors want damage). A silent demonstration that stops at inconvenience is possible — the Pearl Harbor article argues it — but it is the rarer pattern.

Third, the failure mode matches the documented failure mode. Fiber cuts produce this signature. Corrupted databases produce this signature. Failed switches produce this signature. The observed event is unremarkable except in scale — and scale is exactly what a shared backbone produces when it fails once.

The prediction — labeled

The most likely outcome of the investigation, in order: (1) a common-mode FTI telecommunications failure — a backbone circuit, a routing fault, or a botched maintenance/change window on L3Harris infrastructure, essentially the September 21 Philadelphia event at national scale; (2) a cascade triggered by the SMART rollout or another internal software change; (3) contractor/procedural error in the 2023 mold; and a distant (4) — a genuine intrusion in the telecom layer. The resolution will look like the 2023 NOTAM review: a preliminary statement naming a component and a mistake, within weeks, plus a redundancy directive.

That prediction is falsifiable the same way the darker one is. If the FAA cannot produce a fault and a fix that engineers find coherent — if the answer stays "telecommunications outage" forever — the counter-article's thesis deserves a second look.

See also

• FAA Grounds All US Flights November 13 — hub coverage of the event
• Chinas First Cyber Pearl Harbor — the companion analysis arguing the attack thesis
• The FAA Network That Keeps Failing
• What Is SMART FAA AI Air Traffic System
• Every Time America Grounded Every Flight
• ALB Wiki Launches News