A single copper line upgrade at a remote FAA site shut down every departure in the United States. Yeah. Telco engineers, you know what I’m talking about.

A contractor was switching the old line to new fiber on Friday afternoon. The router then flooded the rest of the air traffic network with more than 1,000 connection attempts every four to five seconds. That artifically created storm, a self-Denial-of-Service, meant controllers lost reliable radio and radar.

Transportation Secretary Sean Duffy gave that account on Saturday. The explanation came right from the top. On Friday night he had been singing a different tune. He told the White House briefing that it was the failure of old hardware and “our new IP switches did not go down.” Homeland Security Secretary Markwayne Mullin stood beside him and said the FAA was putting in new equipment and “it was overwhelming the older system.” Mullin was right, in the sense that a Friday afternoon upgrade went sideways. Yeah. Server engineers, you know what I’m talking about.

The FAA, unable to handle their own storm of stupid packets, held every departure from 3:54 p.m. to 8:15 p.m. Eastern. FAA Administrator Bryan Bedford counted 12,000 flights lost on Friday and expected 4,000 to 5,000 more cancellations on Saturday. The old network was fine carrying about 30,000 flights that day before a botched upgrade plan took it down.

On Friday a reporter asked Duffy directly whether FAA caused the outage with an upgrade. He answered by describing the old analog system. Cute. Asked what was different about the system that day, he said “we’re still working on the details of what went wrong today.” He named a cause and then claimed he didn’t know the cause in the same briefing. Because Duffy is actually spelled with two Ms. How do we know? He asked Congress for $50 billion to do more upgrades faster, and the next day said doing the upgrade is what caused the outage. Talk about a sense of fail-faster privilege.

The reporting was flying by this time, even though the planes could not. CBS sources described a botched network update within hours, and Bloomberg reported the FBI was examining whether a software update did it. CBS said the failure was Cisco routers built between 2001 and 2006 that fed out-of-sync data into the wider system.

Running Cisco gear that was built between 2001 and 2006, in other words staring down two decades of reliability, means having redundancy plans for redundancy plans for redundancy when anything is changed. Yeah. Disaster recovery engineers, you know what I’m talking about.

Saturday’s accounting brought more clarity about the same things. An upgrade job caused the outage. Duffy revealed himself to be a weak leader as he started calling the switchover straightforward work at a small location that should have had a small impact. Yeah, my man, I think everyone knows the truth that it was not a small impact at a small location. It was a national security level disaster caused by a cascading fail unsafe on your watch. Service returned once engineers isolated the work that should have been isolated from before anyone put hands on the network. I can’t emphasize enough the self-incrimination of someone in charge who looks at the Hindenburg in flames and gives only the explanation that it was supposed to be a straightforward landing at a small location.

Is there someone else we can put in charge here?

Duffy’s defense, almost unbelievably, is that doing nothing adds more risk. Ok, so Friday tested that claim and Duffy is exactly upside down and backwards. Doing something is what created the failure. The old copper line was carrying traffic until the switchover began. A rush into a changeover brought down the country. Without having any isolation, without having a clear idea of what could happen, doing nothing seems pretty damn smart. The line was due to be discontinued, so there was a need for work. The quality of a changeover, a safety procedure following decades of migration planning, was the FAA’s to manage. An upgrade managed this way is far, far more dangerous than the network it replaces.

The whole country had to be shut down! How much worse could the migration be managed?

Every part of the Duffy changeover plan failed.

The hour chosen was a peak moment of traffic, Friday afternoon with 3,500 aircraft in the air. Controllers told a Washington Examiner reporter that work like this is done midweek in the middle of the night (one of my favorite times to fly, especially into Dallas where you can skateboard all alone all night inside the airport). A reporter asked Duffy why the department did it at such a dangerously busy time, and he said the timing of this work will be reevaluated. For what? It couldn’t be more obvious that the time was approved on a dummy’s watch.

The impact was the whole country. Duffy said he was under the impression a small wire at a small site would have a small impact. Apparently his team assumed a network fault would stay local and not cascade everywhere. The recovery timeline was more than four hours, which itself negates the “small” framing. A day later the FAA is still choosing between contractor error and faulty equipment, which itself negates the “small” framing. The correctness of the installation and its configuration is still an open question requiring more research, even after it went live.

Richard Clarke, the former White House counterterrorism chief, told CNN Saturday morning that he expected a higher standard. New equipment is tested under high load in a sandbox before it goes live. Under Duffy, apparently America rams new equipment straight into the national airspace on a Friday afternoon without a clue.

Duffy pointed his finger at a contractor. He said L3Harris carried out the upgrade and it owns that legacy network. He told reporters he’s the victim of this story because “I’m stuck with L3Harris.” That seems suspect, because the FAA has had this contractor’s number for two decades. The technicians’ union warned after a 2007 Memphis outage that the network’s design made failures like it likely to happen again. Harris, now L3Harris, has held the contract since 2002. The FAA knew its performance, and even knew its priors in this exact context. After a Dallas outage in September 2025 the FAA said an L3Harris oversight failed to make sure the backup systems worked. In other words, when a manager already has faulted a contractor in writing, and then supervises that contractor’s next switchover, the finger pointing changes. The copper-to-fiber work is an FAA program on an FAA schedule. Who knows this? Duffy knows this. Why? Because in 2025 he was the guy who blamed Newark outages on a mishandled move of that airspace to Philadelphia. He called it the fault of… wait for it… the previous administration. Now his own FAA attributes those Newark outages in part to a move made before adequately testing the telecommunications lines. Friday was the same failure Duffy had criticized for failing before, now under his management.

You see the problem with him claiming he was surprised? It was supposed to be small. And the problem with him claiming it was the contractor? It was supposed to be someone else’s fault. And the problem with him claiming it was old equipment? It was supposed to be a win for upgrades.

The Government Accountability Office audited the program two months ago, just to give some idea of how this outage fits into Duffy’s risk management gaffe. Its September 2026 report records the FAA’s finding on the Newark failure. It also mentions that the FAA pulled the copper replacement deadline forward by 21 months, to December 2028. As of May it had 2,610 fiber installations left to do, which works out to about 84 a month. Each one of those, if Duffy doesn’t step up to the job required, has the risk we just witnessed on Friday.

To make a finer point, there’s other evidence Duffy is in a rush to fail faster. In August 2025 the FAA Administrator issued a blanket waiver that exempted the whole program from the agency’s acquisition rules, including its technology and security reviews. The waiver’s stated reason was that those reviews add months or years. GAO found 11,389 separate project schedules that the FAA had yet to join into one master schedule. FAA officials told the auditors that integrating them would be of little use. GAO said the installations were being scheduled with little attention to disruption of air traffic operations, and it warned of “more system outages, ground stops, flight delays, and safety incidents.” The Transportation Department partially concurred and claimed an integrated schedule already existed. GAO disagreed.

Speed was the stated goal. More national disasters, faster, as the predictable outcome. Just because someone put a Duffy in charge.

Duffy told Friday’s briefing the FAA is moving faster than it ever has. As if we needed to be told that after a botched upgrade shut down national airspace. His 2025 announcement of the program promised “we will not let government bureaucracy get in the way of results.” Yeah, he’s turning off all the safety. Man in a rush to stomp on the accelerator for air travel says he has no time to think about consequences. The department’s September release described spending $12.5 billion at “breakneck speed” calling all 13 workstreams on track. More like derailed by speed as the only measure. The FAA hired Peraton in December 2025 to be their single integrator, with the end of 2028 as the deadline.

Duffy Statement	Reality
The old hardware went down.	A contractor’s copper-to-fiber switchover at one site flooded it.
The new IP switches stayed up.	The upgrade work was the trigger.
The fix points to a legacy network problem.	The fix was isolating the upgrade work at the remote site.
Doing nothing adds more risk.	The old line worked until the switchover began.
Congress owes the program $50 billion.	Congress gave $12.5 billion in 2025. GAO is still waiting for a reliable cost estimate.

The old network has been declared obsolete. A November 2023 safety review commissioned by the FAA said so and warned that an unexpected failure could cut an entire regional center off from the network. After Friday’s nation-wide outage I think we can all agree a regional one would be lesser. The report should have raised the standard of care for every change that is meant to upgrade anything. A fragile, obsolete system is a known state in technology circles. It gets a digital twin, a sandbox, a parallel with a fail safe, a tested change in a quiet hour, with a rollback plan. The Duffy version of the FAA waived its reviews to hit a deadline Duffy set by one man’s calendar, done by the time Trump leaves office, like a rushed SpaceX rocket exploding on the pad.

On Friday Duffy had said he is happy to take the blame when the fault lies with the FAA. On Saturday he blamed the contractor. In 2025 he blamed the previous administration. Now that Bedford has promised a root cause analysis, it will be written by the agency that ran the program. Will it name who approved a Friday afternoon switchover? Will he point fingers and rush the next 2,600 if it doesn’t?

The bottom line is congress should cut-off Duffy from the upgrades and certainly not give him any more money, unless he demonstrates the minimum level of competency for the job. You don’t get to run with scissors and shutdown the entire nation on the basis you’re trying to prevent a small regional outage.

Duffy’s proof that the old network keeps failing is the local outages at Newark and New York, and then his Friday switchover took down the whole country instead. What a complete Duffy, spelled with Ms.