Duffy Ties Nationwide FAA Ground Stop to Copper-to-Fiber Cutover

Transportation Secretary Sean Duffy said that Friday's nationwide FAA ground stop was related to work replacing outdated copper wire with a fiber-optic line at a remote FAA facility. The ground stop took place on Friday, 13 November 2026, and Duffy's account was reported on 14 November.

Duffy described the copper-to-fiber project as routine maintenance rather than a major modernization effort. He said the old copper circuits were being discontinued and would have been shut down, which made the upgrade necessary. The Verge reported his remarks.

According to Duffy, the root cause is not yet clear. He said it could have been faulty hardware, a misconfigured router, or incompetence by contractor L3Harris. He also said the newly installed router flooded other routers in the air traffic control system. Duffy described more than 1,000 connection attempts every four to five seconds, which disrupted radar feeds and communication with aircraft.

A router is the device that decides where data packets should go. Routers that exchange routing information directly with one another are called peers, and the shared link between them is an adjacency. Think of a set of postal sorting offices that pass instructions to each other about where mail should go. If one office starts sending out a flood of bogus instructions, every neighbor has to process them.

Duffy also called on Congress for additional funding to modernize the air traffic control system. He said Congress had provided only a partial payment for the work the system requires.

The broader context here is the gap between the label and the outcome. A copper-to-fiber cutover is typically a transport-layer change, meaning it alters how bits physically move across the network, and maintenance crews usually treat it as low risk. The failure Duffy described appears instead to have spread through the routing and control plane, the layer that governs path decisions. There, a single new device that behaves abnormally can affect every peer that shares its adjacency. Whether the fault lay in the hardware, the configuration, or the contractor's implementation, the operational lesson is the same. Legacy and replacement paths in a safety-critical network need to be isolated from each other, and a new router needs to be validated against the failure modes of its neighbors before it carries live traffic. Rollback procedures matter as much as the cutover plan itself.

The funding request sits in the same frame. Duffy framed the copper retirement as a requirement the FAA could not postpone, because the copper service was being discontinued. The maintenance work and the modernization effort therefore depend on each other, and Duffy's comments suggest the agency is working with a partial budget for the larger one.

In my view, the questions that will matter most in the coming weeks are technical and procedural rather than political. What was the sequence of configuration changes on the new router, how was the legacy path isolated from the replacement path, and why did the flood of connection attempts reach the radar feeds and voice communication? Those answers will determine whether this was an isolated misconfiguration or a design gap that exists elsewhere in the network.

There is also a more constructive reading. Fiber transport and modern IP-based systems are the foundation that a more resilient air traffic control network would require. Retiring copper is a necessary step in that direction, and the incident is a concrete reminder that the cutover process is where that foundation can fail. Once the root cause is established, the fixes it prompts, including tighter change control, better fault isolation between control-plane peers, and clearer rollback paths, could make the next upgrade safer than this one.