Live coverage of the FAA nationwide ground stop, 13 November 2026Last checked: Monday 16 November 2026, about 05:30 ET
Home › Why Were Flights Grounded on 13 November 2026?
FAA Ground Stop · 13 Nov 2026

Why Were Flights Grounded on 13 November 2026?

Every departing flight in the United States was grounded on Friday 13 November 2026 because the communications network that air traffic controllers rely on began to fail. The FAA ordered the stop as a safety measure, before the degradation could put aircraft at risk. This page explains the reason in plain language, and separates it from the two stories it is most often confused with: the government shutdown flight cuts, and a cyberattack.

In short

Flights were grounded because the FAA's air traffic control communications network became unstable. Router work at El Dorado, Arkansas, and Amarillo, Texas, during a copper-to-fibre upgrade flooded the network with about 1,000 connection attempts every 4 to 5 seconds, destabilising 17 of the FAA's 22 Air Route Traffic Control Centers. With controllers losing reliable contact with aircraft, the FAA halted all departures at 3:54pm ET as a safety measure. It was not a cyberattack, and it was not the same thing as the shutdown-era flight cuts at 40 airports.

The short answer

Air traffic control depends on controllers being able to talk to pilots and see aircraft on radar. On Friday afternoon, the network that carries those voice and data links — the FAA Telecommunications Infrastructure network, or FTI — began to fail. Legacy equipment became unstable as data flooded the network. The instability reached 17 of the FAA's 22 Air Route Traffic Control Centers and spread into several Terminal Radar Approach Control facilities. The FAA did not wait for the failure to become a loss of separation between aircraft. It ordered a nationwide ground stop at 3:54pm ET, holding every departure on the ground while aircraft already airborne were allowed to land. The stop is the reason flights were grounded; the router failure is the reason the stop was ordered.

What actually failed

The failure was in the ground network, not in the sky. The FAA says some radio frequencies and radar feeds remained reliable throughout, and about 3,500 aircraft landed safely during the stop. What failed was the system that links control centres together. Contractor L3Harris had been working at a radio communications site in El Dorado, Arkansas, replacing copper connections with fibre optic cable and deploying a new router. When that router was switched on, it began flooding the FTI network with about 1,000 connection attempts every 4 to 5 seconds. A router installed about three weeks earlier at a radar site in Amarillo, Texas, also began flooding the system, according to Secretary Duffy. The flood overwhelmed legacy equipment that was never designed for that volume of connection attempts, and the instability spread from centre to centre. The FAA's account is preliminary: whether the cause was faulty equipment, an installation error or a configuration mistake is still under investigation.

Why ground everything, rather than slow things down?

The FAA has gentler tools. A ground delay programme slows departures to one airport by assigning later departure times. An airspace flow programme manages traffic through a congested area. A ground stop is the bluntest tool: nobody departs. The FAA chose it because the failure was not local and not predictable. Seventeen of 22 control centres were unstable, and the instability was spreading. Controllers in one centre could not be sure which frequencies and feeds they could rely on, and the centres hand aircraft to each other as flights cross the country. Slowing departures would still have put aircraft into a system whose communications were degrading. Holding them on the ground removed the risk while the FAA isolated the faulty equipment. The stop was lifted at 8:15pm ET, after the broadcast function on the routers involved had been disabled and the system had been checked.

Why flights stayed cancelled after the stop was lifted

The stop lasted 4 hours 21 minutes. The cancellations lasted the weekend. That is not a contradiction; it is how airline networks work. An aircraft that should have flown from Chicago to Dallas on Friday afternoon was still in Chicago on Friday evening, and the crew that should have flown it had run out of legal duty hours. Saturday's flights from Dallas needed that aircraft and that crew. Airlines spent the weekend repositioning aircraft and crews city by city, which is why Saturday still saw about 6,400 to 6,700 cancellations and Sunday roughly 1,960 to 2,300. The same pattern explains the diversions: at least 827 flights were diverted on Friday, 670 of them back to their departure airport. Passengers booked on connecting flights were hit hardest, because a missed first leg breaks the whole itinerary.

Not the shutdown flight cuts

A common confusion is worth clearing up. Before the ground stop, the FAA had ordered airlines to cut flights at 40 airports because of the government shutdown — 4 percent from 7 November, raised to 6 percent on 10 November, then eased to 3 percent on 15 November. Those cuts were a planned, scheduled reduction to ease pressure on unpaid controllers. The ground stop was a different event: an emergency halt of all departures, ordered without warning on Friday afternoon because the communications network was failing. The two overlapped in time and both disrupted travel, but they had different causes, different mechanisms and different remedies. The shutdown cuts were eased as the shutdown ended; the ground stop ended when the faulty routers were isolated.

Not a cyberattack

The other confusion is a cyberattack. The FAA's position is that, based on all available evidence, there is no indication this was a cyberattack or an outside nefarious actor. FAA Administrator Bryan Bedford said there was zero evidence of anything nefarious and zero evidence of anything AI-related. The FBI does not believe a cyberattack or criminal activity was involved, according to Bloomberg, although the FBI is still partnering on the router review. The FAA's SMART system, an AI-assisted data tool, was not involved: the agency says SMART is a data aggregator that does not feed information into the air traffic control system. The full evidence is on our cyberattack page.

Frequently asked questions

Because the FAA's air traffic control communications network became unstable after router work at El Dorado, Arkansas, and Amarillo, Texas, flooded it with about 1,000 connection attempts every 4 to 5 seconds. The FAA halted departures as a safety measure.

The failure affected 17 of 22 control centres and was spreading. With controllers unable to rely on their communications, slowing departures would still have put aircraft into a degrading system. Holding departures on the ground removed the risk.

No. The shutdown led to planned flight cuts at 40 airports, a separate measure. The ground stop was an emergency response to a communications failure.

No evidence indicates so. The FAA, the FAA Administrator and the FBI have all said there is no indication of a cyberattack or outside nefarious actor.

Aircraft and crews were out of position after Friday's stop, and crews had run out of legal duty hours. Airlines needed the weekend to reposition them, which is why cancellations continued after the stop was lifted.

No. Aircraft already airborne were allowed to continue and land. About 3,500 landed safely during the stop.

Sources & check time. FAA, Nationwide Ground Stop: Questions and Answers (15 Nov 2026); Reuters via BusinessWorld; Bloomberg via PMN/eNews Malaysia; FlightAware; Cirium via JohnnyJet. Last checked about 05:00 ET, Mon 16 Nov 2026.
Figures are given with their snapshot time and source. Developing items are marked as developing. Last checked Monday 16 November 2026, about 05:30 ET.