A nationwide ground stop that halted flights across the United States on Friday was caused by a router failure during what officials described as routine maintenance work, Transportation Secretary Sean Duffy said Saturday.
Duffy said that contractor L3Harris, a longtime FAA vendor, was upgrading copper wire to fiber optic cable at a remote location when a router overloaded a critical communication system, triggering the ground stop.
"It's pretty straightforward work that we were doing yesterday at, again, a very remote location," Duffy said at a Saturday press conference. "What we're working to determine was whether we had incompetence — meaning, was it user error or [installer] error from L3Harris? Or did they install a faulty router?"
FAA acting CTO Rebecca Guy provided additional technical detail, saying the agency observed two nodes generating an outsized volume of connection requests. "When we started to see the occurrence where our network was having instability, we started to look at what was the cause," Guy said. "And as such, we saw two places that were actually pinging our network at a very high rate — a thousand connections over every four to five seconds."
Guy said the FAA disabled both sources of network instability and was able to stabilize the system, and that a root cause analysis is now underway.
The event represents only the third nationwide ground stop of the 21st century. More than 8,200 flights were canceled Friday evening, according to aviation data firm Cirium, and the disruption carried into Saturday, with at least another 3,000 flights canceled after the ground stop was lifted.
Questions arose about why the maintenance work was conducted at 3 p.m. on a Friday afternoon rather than during off-peak hours. Duffy acknowledged the timing, saying that while switchovers at larger airports are scheduled late at night, remote-location switchovers are typically performed during the day. "There will be reevaluation of when we do this work," he said.
The incident coincided with an unrelated FAA announcement the previous day regarding the rollout of an AI tool for air traffic controllers — a timing that prompted speculation about a possible connection. FAA administrator Bryan Bedford moved quickly to dismiss that line of inquiry. "We want to be clear that we have an equipment issue, and we're working through what this defective piece of equipment was," Bedford said, adding there was "zero evidence of anything nefarious and zero evidence of anything AI-related."
The air traffic controllers union said it had not been consulted in the design of the AI tool, though that system was not implicated in the outage.
Duffy has used multiple press conferences surrounding the incident to press Congress for increased funding for aviation infrastructure upgrades, reinforcing a longer-standing argument that aging FAA systems present systemic risk. With a formal root cause analysis still in progress and questions about L3Harris's role unresolved, the findings could carry implications for how the agency schedules and oversees contractor work on critical communications infrastructure going forward.