The Federal Aviation Administration says the nationwide ground stop that froze U.S. departures was caused by telecom equipment and two routers that started flooding the agency’s network. The agency’s fresh Q&A and briefings lay out a narrow, technical explanation — and a very big mess that cost travelers and commerce dearly. Below is the FAA’s account, the vendor responses, and why Congress should stop treating this like a grown-up’s PowerPoint and start doing real oversight.
FAA’s preliminary explanation: routers, floods and two trouble spots
The FAA says technicians saw instability in radar and communications after legacy telecommunications equipment “became unstable when data began flooding the FAA FTI network, at a rate of 1,000 connection attempts every 4 to 5 seconds.” That is the short version of why the agency stopped departures. The FAA points to two locations — a radio site in El Dorado, Arkansas, and a radar site in Amarillo, Texas — and says a router deployed during replacement work at El Dorado was blocked, then disabled, which helped stabilize the system. The FAA also says it turned off the broadcasting function on similar new routers as a precaution while the forensic work continues. FAA Administrator Bryan Bedford told reporters investigators have so far found “zero evidence of anything nefarious.”
Vendors push back and investigators keep digging
Contractors and vendors are not taking blame neatly. L3Harris, the contractor involved in the replacement work, says it is cooperating with the probe. Hewlett Packard Enterprise, which owns Juniper, told reporters the device “functioned as it was configured to by the installer. It did not fail or act improperly.” Meanwhile the maker of the FAA’s new SMART AI analytics tool, AirSpace Intel, flatly denied its product caused the shutdown, saying the outage was “not based on or a result of the SMART system.” Homeland Security Secretary Markwayne Mullin said there is no sign yet this was a cyberattack, but FBI and other investigators remain on the case. Translation: the story looks narrow, but the real root cause — bad kit, bad config, or bad integration — is not settled.
Wider fallout and the modernization fight
Make no mistake: this was not a minor hiccup. The FAA’s Q&A lists roughly 12,462 cancellations tied to that day, with thousands more delays and schedule chaos in the days after as airlines tried to recover. Transportation Secretary Sean Duffy used the moment to argue Congress needs to authorize serious funding to modernize the FAA’s aging systems, saying “our switches, our routers, actually got overloaded with data … and started to give us inconsistency in the data from those routers.” That’s a fair point — but it’s only half the answer. Throwing money at a system without real project discipline, clear standards, and hard accountability is how you end up with shiny gear that doesn’t play nice with decades-old systems.
Congress should demand answers — and real fixes
Here’s the conservative prescription: yes, fund modernization. But Congress must attach tough oversight, performance milestones, and vendor accountability. Subpoenas, public hearings, and technical after-action reports should follow. If the problem was a misconfigured router or sloppy installation, those vendors should explain themselves under oath. If it was a design mismatch between new routers and legacy networks, the FAA needs to explain why it let the system drift into this brittle state. Travelers deserve planes in the sky, not excuses on the runway. We can fix this — but only when politicians stop treating this as a talking point and start demanding results.

