US halts flights at busy East Coast airports, says fiber line cut
A widespread flight halt at major U.S. East Coast airports, triggered by a severed FAA fiber line and a failed backup link, is prompting scrutiny of how critical air-traffic communications are engineered and monitored. Commenters highlight long-standing issues with redundancy, testing of backup systems, and the risks of outsourced or poorly audited network infrastructure, noting that even “dual” links can share single points of failure. Some raise concerns about possible sabotage or geopolitical context, while others argue the more likely cause is systemic underinvestment, bureaucracy, and inadequate operational discipline in life-critical systems.
New ATC Systems and DC Deployment
- Discussion of a new FAA ATC system and AI-based controllers rolling out, with Washington DC as an early deployment.
- Some are skeptical it’s being rushed (“vibe coded”), others argue DC is the right place to dogfood because politicians use that airport heavily.
- One detailed comment explains DCA’s chronic over-scheduling and runway constraints, arguing better prediction and slot management software is badly needed.
- Others note “new ATC systems” have been “rolling out” for decades, and this particular system would not have prevented this fiber-related outage.
Fiber Cuts and Locating Underground Infrastructure
- Multiple anecdotes describe how easy it is for construction to cut buried fiber, even with 811/call-before-you-dig.
- Locating cables is imperfect: tracer wires can break, markers get removed, soil shifts, records are incomplete or wrong.
- Some utilities themselves do not know where legacy copper/fiber runs are.
- Hydrovac and careful boring are used where risk is high; jokes abound about “summoning” backhoes by burying fiber.
Redundancy, Backups, and Monitoring Failures
- ATC facilities have primary and backup dedicated links; here the primary failed and the backup was already cut.
- Several commenters stress that untested backups are effectively no backups; monitoring should have detected the dead backup line earlier.
- Broader pattern: organizations resist paying for true redundancy (fully separate paths, environments, and restore testing), even for critical systems.
- Debate over dual-use vs. standby backups: using all paths continuously exposes failures early, but is harder to engineer.
- There is concern that for something as critical as ATC, having only two links and weak validation is unacceptable.
Public Internet, Starlink, and Tertiary Paths
- Some insist ATC must not rely on the public internet; others propose encrypted internet tunnels as tertiary backup, arguing it’s better than nothing.
- Starlink (or similar satellite links) is suggested as an emergency path; pushback focuses on over-dependence on a single private actor, though many see it as acceptable as a last-resort layer.
Sabotage vs. Incompetence
- A few speculate about state-backed sabotage or “grey-zone” operations, connecting this to European cable incidents and other ATC outages (UK, Netherlands).
- Others counter that accidental utility strikes are extremely common, and low engineering quality or bureaucratic dysfunction can explain much without invoking sabotage.
- Overall, the thread is split between seeing systemic incompetence/underinvestment and seeing primarily bad luck layered on weak backup practices.
Institutional and Contracting Issues
- Some blame “incompetent people” running tech; others defend FAA staff as caring but constrained by bureaucracy, outsourcing, and conflicting priorities.
- Concerns about regulatory capture and past FAA failings are raised as context for distrust.
- Several emphasize that even when infrastructure is outsourced, the government still needs enough in-house expertise to demand, verify, and audit real redundancy.