Incident sheet · /infrastructure

Filed
Read
4 min · 744 words
Severity
Routine

FBI Joins FAA Probe of Router Behind 4-Hour Nationwide Ground Stop

A routine L3Harris router replacement in Arkansas disrupted 17 of 22 US air traffic control centers, canceled 18,000 flights, and reignited a $50 billion FAA funding fight.

FAA, FBI investigating router responsible for nationwide ground stop
FeedFAA, FBI investigating router responsible for nationwide ground stop — 16301694 / pixabay

Event log

  1. A router installed by L3Harris in El Dorado, Arkansas disrupted 17 of 22 Air Route Traffic Control Centers on Friday.
  2. The nationwide ground stop lasted nearly 4 hours 40 minutes; about 18,000 flights were canceled Friday through Sunday per FlightAware.
  3. The FAA disabled potentially faulty functionality on roughly 60 similar routers as a precaution.
  4. The suspect router is under analysis at an L3Harris lab in Florida with FAA staff and FBI agents present.
  5. Secretary Duffy is asking Congress for $50 billion for the FAA's tech overhaul.

A single router, installed by L3Harris in El Dorado, Arkansas, triggered a nationwide ground stop that disrupted 17 of 22 Air Route Traffic Control Centers and canceled roughly 18,000 flights over three days. That is the official account. The FAA and FBI are now testing the hardware at an L3Harris lab in Florida, and the numbers warrant scrutiny before anyone accepts the full story.

What happened on Friday?

The FAA issued a nationwide ground stop for all U.S. airports Friday afternoon after instability hit 17 of the 22 Air Route Traffic Control Centers and several Terminal Radar Approach Controls. The stop lasted nearly four hours and 40 minutes. Travelers felt the effects through the weekend: about 18,000 flights within, into or out of the United States were canceled from Friday to Sunday, per aviation data tracker FlightAware.

The agency said there was not a full radio and radar outage. The system was disrupted, not dark. That distinction matters for liability and for how regulators frame the severity.

What is the FBI doing in Florida?

Transportation Secretary Sean Duffy said the suspect router is now at an L3Harris lab in Florida, with FAA staff and FBI agents present. Duffy personally requested the Bureau's involvement.

"I called [FBI Director] Kash Patel, and said, 'Kash, would you send your agents just to make sure everything, per the FBI's thought process, it's all being done right,'" Duffy said Monday on CNBC. "Everybody is congregated in Florida, and we are going to do an analysis on the server and the methods that were used on its installation."

Note what the FBI presence signals: the government wants independent verification that the vendor's own lab is conducting the analysis properly. The hardware is being examined inside the facility of the company that installed it.

The router was part of a routine replacement, not a new deployment. The FAA said it has disabled the potentially faulty functionality on roughly 60 similar routers across the system as a precaution, per an FAQ posted Sunday.

Was this tied to the modernization push?

The FAA says no, and it drew the line explicitly.

"None of the upgraded towers that received modifications from the down payment in the Working Families Tax Cuts went down," the agency said Sunday. "This type of work has been going on for years to transition from old copper wires that are being disconnected due to their obsolescence."

"It is important to distinguish routine equipment upgrades from the FAA's broader modernization effort," the FAA added.

Yet Duffy and FAA Administrator Bryan Bedford are using the incident to argue for more money. "I want $50 billion," Duffy told reporters at the White House on Friday — a figure roughly five times the FAA's annual operations budget — and he repeated the demand through the weekend. An old copper-to-fiber transition failed, and the response is a $50 billion request. The gap between those two facts is the political story here.

How is Congress responding?

Bedford met with House and Senate members Sunday, per Politico, and Duffy is set to speak with lawmakers Tuesday. Responses split along predictable but not uniform lines.

  • House Speaker Mike Johnson, R-La., supports the bigger budget.
  • Democrats want answers about the incident and stronger oversight.
  • Some members reject the funding link entirely.

"Recent events are not the result of a lack of funding or support from this Congress," said House Appropriations Committee ranking member Rosa DeLauro, D-Conn., and Transportation, Housing and Urban Development Subcommittee ranking member James Clyburn, D-S.C., in a Sunday statement. "They result from leadership decisions that continue to put politics and private interests above the public's interests."

Sen. Jack Reed, D-R.I., went further on Saturday, calling for an independent probe and public hearings.

"Shoveling money at a problem isn't the same as fixing it," Reed said. "Legitimate questions have already [been] raised about whether the FAA's implementation strategy was moving faster than its safety evaluations, workforce training, and independent oversight actually support."

What is still unknown?

No root-cause finding has been released. The FAA has not said whether the fault lies in the router hardware, its configuration, or the installation method L3Harris used. The agency has also not disclosed how many of the 60 precautionary router changes affected live traffic handling. Until the Florida lab analysis concludes, every claim — routine failure, sabotage ruled out, funding shortfall — remains unverified.

via fedscoop.com (Source)

Filed under

  • faa
  • air-traffic-control
  • router-hardware
  • fbi-investigation
  • aviation-infrastructure
Share this article:

More from Daniel Okafor

Daniel Okafor

Show full bio

Staff writer covering technology and product news in enterprise information technology and the leaders who run at CIO Monitor.

203 articles

The newsroom digest

One email a day with the stories that matter. No noise.

By subscribing you agree to the privacy policy.

Cross-references

‹ Previous articleNext article ›