This week, the US aviation industry is counting the cost of a nationwide FAA ground stop that triggered thousands of flight cancellations and delays over the weekend. Although airlines now expect operations to return largely to normal, the technical failure has raised further questions about the resilience of America’s ageing air traffic control infrastructure.
The disruption began on Friday 13 November, when instability in the Federal Aviation Administration’s (FAA) telecommunications network affected communications and radar feeds used by air traffic controllers. The agency responded by temporarily halting departures across the country, grounding flights for almost five hours.

While the immediate problem has been isolated, the FAA and its network service provider, L3Harris, are still investigating the underlying cause. The incident has also renewed attention on the condition of the infrastructure supporting one of the world’s busiest aviation markets.
The FAA began experiencing technical problems at approximately 15:30 Eastern Time on Friday. Instability affected radar and communications systems used by air traffic control centres and Terminal Radar Approach Controls (TRACONs). At 15:54 ET, the agency issued a nationwide ground stop, temporarily preventing departures across the US. Aircraft already airborne were allowed to continue to their destinations and land safely.
Approximately 3,500 aircraft were in the air when the disruption began. The ground stop was lifted at 20:15 ET, after the FAA had isolated the immediate problem and established that the network was stable enough for operations to resume. The FAA subsequently confirmed that instability had affected 17 of its 22 Air Route Traffic Control Centres, spreading into several TRACON facilities.
This was not a complete loss of radar or radio communications. Some frequencies and radar feeds remained operational, allowing controllers to maintain contact with aircraft and track their movements. The ground stop was therefore a precautionary safety measure rather than a response to a total communications outage. The FAA confirmed that all aircraft landed safely during the incident.
What Caused the Disruption?
The FAA’s initial investigation points to excessive data traffic overwhelming parts of its legacy telecommunications network. In an update published on Sunday 15 November, the FAA said its network had received approximately 1,000 connection attempts every four to five seconds. This created instability in communications and radar feeds.
Investigators identified two potential sources of the excessive data traffic: a radar site in Amarillo, Texas, and a radio communications site in El Dorado, Arkansas.
The FAA’s network service provider, L3Harris, had been carrying out upgrade work at the sites, including installing new routers and copper wire maintenance. When the new router at El Dorado was activated, excessive data traffic affected the wider network. After identifying inconsistencies in the data, L3Harris blocked the two locations, which helped stabilise the network.
As an additional precaution, the broadcasting functionality on the newly installed routers was disabled. The FAA also disabled the same functionality on approximately 60 similar routers elsewhere in the system. However, the agency has not yet established the root cause of the issue. It is investigating whether the problem originated with the router installation, the equipment itself or another network fault.
The FAA has said it found no indication of a cyberattack or external malicious actor based on the evidence available.
Impacted Flights
Although the ground stop ended on Friday evening, the disruption continued throughout the weekend. The FAA reported approximately 12,462 flight cancellations on Friday 13 November.
According to FlightAware figures, more than 6,400 flights were cancelled and approximately 8,000 delayed on Saturday. A further 2,100 cancellations and 9,400 delays were recorded on Sunday, bringing the disruption into its third day.
The consequences extended beyond the immediate suspension of departures. Aircraft and crews were left out of position, forcing airlines to reorganise schedules, arrange replacement services and rebook passengers.
Modernising Air Traffic Control
The investigation raises questions about how routine maintenance and upgrades at remote facilities can result in instability across such a substantial proportion of the national air traffic control network.
Replacing ageing equipment is of course necessary, but the transition must be carefully managed. The FAA will need to establish how the network responded to the new equipment, whether existing safeguards were sufficient and why the resulting data traffic was able to affect so many facilities. The agency has said it will reconsider the timing of maintenance and replacement work following the incident.
Meanwhile, the incident has also renewed attention on the need to replace ageing infrastructure within the FAA. Duffy has repeatedly called for substantial investment in modernising the country’s air traffic control system, arguing that its existing telecommunications and other supporting infrastructure are no longer adequate for the demands placed upon them.
Following Friday’s disruption, he reiterated the administration’s call for 50 billion USD in funding towards a comprehensive modernisation programme.
U.S. Transportation Secretary Sean P. Duffy said:One of the biggest problems we continue to see is our network, and the architecture of our network is from 1980. We need modern technology and architecture. I have AT&T, Verizon, and Lumen all ready to go. We have the architecture ready to build a state of the art telecom system that will give us resiliency. All I need is the money to finish it. My hope is if they give me money today, I’ll be going tomorrow to build it and this telecom system would be ready by the end of 2028, the first part of 2029.
Notably, the FAA has also stressed the distinction between replacing individual components and undertaking wider system modernisation. Its investigation into Friday’s incident concerns instability involving its legacy telecommunications network during equipment replacement work. The agency has specifically said that its wider modernisation programme did not cause the disruption.
Nevertheless, the incident highlights the challenges of maintaining critical infrastructure while transitioning to newer technology.
Could America’s Aviation Network Face Further Disruption?
The FAA’s handling of Friday’s incident demonstrates how safety procedures continue to take precedence over maintaining flight schedules. However, the speed and scale of the resulting disruption exposed the dependence of the wider aviation industry on infrastructure that passengers rarely see.
The weekend’s disruption does not mean further failures are inevitable, but it does expose the risks of operating critical aviation infrastructure that depends on ageing technology while undergoing extensive upgrades.
As flights return to normal on Monday, the focus undoubtedly shifts from recovery to prevention. The investigation arguably needs to produce more than another commitment to modernisation by the end of the decade. It must establish what failed, why existing safeguards did not prevent the disruption from spreading and what practical changes will make the system more resilient.