FAA Ignored Its Own Redundancy Warning Twice

A cut fiber-optic cable beneath a Pennsylvania highway on Monday morning disabled air traffic control systems across the Northeast, canceling or delaying hundreds of flights and stranding tens of thousands of passengers.

The Federal Aviation Administration routed traffic through backup facilities. The system held — but the mechanism that nearly broke it has held once before. The second time we notice the same fault line, we stop calling it an accident.

In 2014, an earthquake near Napa severed fiber cables that served 911 call centers across California. The redundancy safeguards everyone assumed existed turned out to be a regulatory fiction — no mandate required telecom carriers to route emergency services through multiple physical pathways.

The FAA audited its own infrastructure and found air traffic control facilities depended on commercial fiber networks with identical vulnerabilities. The recommendation was clear. Carriers should mandate redundant routes and require cables to be buried through different corridors so a single excavator cannot sever the system. Then cost objections from the telecom industry arrived, and the mandate became guidance. Voluntary compliance language replaced enforceable requirement.

Ten years after Napa, a construction crew in North Carolina severed a cable that routed signals through multiple control centers. The system's second pathway should have made this routine. The routing architecture meant both primary and backup lines ran through the same buried conduit in the same geographical area. What's different now is that the mechanism is visible. Every organization that matters watched the same pattern repeat and did nothing twice. That's not vulnerability. That's choice. When you see a system fail in the same way across multiple timescales, what matters is not preventing the next identical failure. Understanding why the people managing the system chose to leave it broken.