Transportation Secretary Sean Duffy said a contractor’s fiber upgrade collided with air-traffic safety. According to Duffy, L3Harris was swapping Federal Aviation Administration (FAA) telecommunications lines from copper to fiber at a remote FAA site when a router flooded other routers on the network. He said the surge destabilized controller-to-aircraft communications and disrupted radar feeds, prompting the FAA to impose a nationwide ground stop at about 3:36 p.m. Eastern.
What officials say happened
Duffy said the network saw “over 1,000 connection attempts every four to five seconds,” overwhelming parts of the system and triggering cascading effects. With communications and radar feeds wobbling, the FAA ordered planes to remain on the ground until systems stabilized.

How far it spread
Coverage cited in the source article said the disruption touched 17 of the FAA’s 22 en‑route centers, the backbone facilities that manage traffic between takeoff and landing. Major hubs reported delays and cancellations into the weekend as operations recovered.
What investigators are testing
Officials, as summarized in the source article, are examining whether the event stemmed from an L3Harris installation or configuration mistake, or from defective router hardware. The source notes that detailed logs and forensics are expected in a final report.
Context: aging systems flagged by GAO
The Government Accountability Office has warned for years about FAA modernization challenges. In 2024, auditors reported that more than three-quarters of 138 systems were “unsustainable” or “potentially unsustainable,” underscoring resilience risks when a single node fails.

Impact on travelers
Reports referenced by the source article tallied thousands of cancellations and delays, with knock-on effects as aircraft and crews fell out of position. Planes already airborne continued flying with added spacing, while departures waited for stable communications and clear handoffs.


What remains unsettled
The precise root cause—contractor error versus hardware failure—was not resolved in the material provided. Some details, including the exact number of affected FAA centers and final disruption totals, were attributed to broader media coverage and may be refined by the FAA’s after‑action findings.
