The FAA ground stop investigation gained new detail on Nov. 14, 2026, when Transportation Secretary Sean Duffy described maintenance on a legacy communications network and abnormal router activity as a possible explanation for the nationwide disruption a day earlier. The Department of Transportation emphasized that the precise cause was not yet determined.

The agency's earlier notice identified a telecommunications failure affecting air-traffic communications and radar information. Saturday's briefing added a proposed technical sequence involving a copper-to-fiber transition, but officials said they were still assessing whether the problem was defective equipment or an installation error. That distinction matters because early descriptions of an outage should not become a final investigative finding by repetition.



FAA ground stop investigation examines router activity

According to the Transportation Department, an L3Harris contractor was performing maintenance at at least one remote FAA location, replacing older copper-based communications with a fiber connection. Duffy said a router involved in that transition appeared to generate unusually heavy traffic affecting other routers. He described more than 1,000 connection attempts every four to five seconds as part of the disturbance.

The account links those events to unstable pilot-controller communications and interruptions to radar feeds. It remains the department's working description, not the final technical report. Duffy expressly left open whether a faulty router or contractor execution led to the problem. The public statement did not identify a definitive failed component or publish a completed root-cause analysis.


Why an air-traffic communications problem affects flights

Air traffic controllers rely on communications, surveillance data and coordinated procedures to keep aircraft separated. If the reliability of these systems is uncertain, managers can restrict departures while assessing the available information. A nationwide ground stop prevents new departures covered by the restriction and reduces workload while air-traffic facilities recover; it does not mean every aircraft already flying is automatically ordered to land.

The FAA's safety response also creates a substantial operational recovery problem. Aircraft held on the ground cannot immediately resume all missed departures when a restriction lifts. Airline crews have duty-time limits, aircraft are needed elsewhere, and connection banks become disrupted. TAD's initial nationwide ground-stop report documented the interruption before the more detailed Saturday briefing.


DOT reports thousands of flights handled during recovery

The department said controllers and pilots brought more than 3,500 flights safely to the ground during the crisis and that more than 8,000 flight operations resumed Friday night after restrictions eased. The briefing described the national airspace as open again Saturday, while warning that cancellations and delays might continue as airline networks stabilized.

Those operational totals describe activity during the response and early recovery, not the final number of passengers affected or the dollar cost to airlines. The department did not provide an audited systemwide damage figure. Passengers should continue to rely on their operating carrier's flight status and rebooking notices rather than infer that an open airspace guarantees their particular flight will depart on time.


Aging infrastructure makes the technical review consequential

Duffy described the FAA's legacy telecommunications network as decades old. The migration from time-division multiplexed, analog-style connectivity to internet-protocol networking was presented as necessary because old copper lines were being phased out. That makes the maintenance task routine in principle but potentially consequential when performed on safety-critical communications infrastructure.

The specific incident also raises questions about change control, testing and resilience: how a maintenance action at one location could affect a wider network, what safeguards should isolate abnormal traffic, and how quickly controllers can switch to alternate procedures. Those are questions for a documented review. They should not be treated as proven deficiencies by individual technicians before investigators establish which safeguards existed and what failed.


FAQ: FAA ground stop

What caused the FAA ground stop on November 13?

The original advisory cited communications failures. DOT later described apparent abnormal router traffic during a network transition while emphasizing that the final cause remained under investigation.

Did the FAA ground stop end on Friday?

Yes. Nationwide restrictions were lifted Friday evening, although DOT warned on Saturday that flight schedules could still face delays and cancellations.

Did officials blame L3Harris for the outage?

Duffy identified the contractor's maintenance role, but said officials had not decided whether installation error or equipment failure was responsible.


Looking Ahead

The next important development is a documented determination of the failed equipment, configuration or procedure and any corrective action. DOT had not announced a complete public root-cause report in the Nov. 14 briefing.


Sources

Nabeel Khan

Written by

Nabeel Khan

Nabeel Khan is the founder and editor of The Aviation Diary. A mechanical engineer working in the aerospace industry, he covers military and commercial aviation, defense, and space. Views expressed are his own.

More from this author →