On a busy Friday afternoon, a communications failure hit the centers that control America's high-altitude traffic. The FAA had only one safe option: to keep every departing airplane on the ground.
The nationwide ground stop began at about 3:54 p.m. ET on Friday, Nov. 13, 2026. It stopped departures at every US airport. Transportation Secretary Sean Duffy said that there was a communication problem at all Air Route Traffic Control Centers. The FAA later called it "a temporary telecommunications outage."
The two earlier orders came on very different days. On Sept. 11, 2001, the FAA's Command Center ordered a nationwide ground stop at 9:25 a.m. during the hijackings. On Jan. 11, 2023, a failure of the NOTAM system held departures across the country from 7:30 a.m. until about 9 a.m. ET. News sources count these orders differently, and the authors found no official FAA count.
Why one network failure stops the whole country
The US has 22 Air Route Traffic Control Centers, and they handle every flight above 18,000 feet. An Embraer 175 on a short regional flight and a Boeing 777-300ER flying to Asia both climb into and cruise through their airspace.
Controllers cannot work without their link to pilots. When that link fails, the FAA does not add more aircraft to a system that may not be able to contact them. It stops traffic at the source with a ground stop and lets the aircraft that are already flying land.
That is what the Command Center's advisory did. It said that "all airports are ground stopped" and that all departing traffic would stay on the ground "until further notice." Inbound international flights would be handled case by case, and flights in the air continued to their destinations.
What went wrong
The most detailed explanation came from sources who spoke to CBS News. They said that an update to the private communications network of the air traffic control system made the network reboot, and the reboot crashed it. CBS said that L3Harris operates the network. An internal Alaska Airlines message seen by CNBC also pointed to communications and radar problems.
Homeland Security Secretary Markwayne Mullin told reporters there was no sign of an attack by anyone trying to cause harm. "It's just a telecommunications outage as of now," he said. "This isn't another 9/11." Officials told NBC News that there was no sign of a cyberattack either.
3,100 airplanes in the air and 11,000 waiting to leave
It was almost the worst possible time. According to Cirium, about 11,000 flights were planned to leave US airports after 4 p.m. ET that Friday. Flightradar24 counted about 3,100 aircraft in the air and flying to US airports when the stop began. Soon after the order, FlightAware showed more than 10,000 delays and over 2,000 cancellations.
Arriving flights kept landing, but nothing left, so the ramps filled up. A source told NBC News that by about 5:30 p.m. ET, Reagan Washington National was full and O'Hare was nearly full.
For comparison, the 2023 NOTAM failure delayed more than 10,000 US flights, but departures were moving again within about 90 minutes. On Sept. 11, 2001, the FAA went further. At 9:42 a.m., after the Pentagon was hit, national operations manager Ben Sliney ordered every aircraft to land at the nearest airport. According to the 9/11 Commission, about 4,500 commercial and general aviation aircraft landed without incident.
Three orders, three causes
Sept. 11, 2001: a terrorist attack.
Jan. 11, 2023: damaged files in the NOTAM database.
Nov. 13, 2026: a telecommunications outage across the en route centers.
The weak point is the network
The 2023 stop started when a contractor deleted files by mistake, the FAA later said. Friday's stop seems to have started in the network itself.
This network is more important than most travelers realize. According to The Register, the FAA Telecommunications Infrastructure, managed by L3Harris, carries secure communication between more than 4,400 FAA facilities. It is already being replaced. In August 2026, the FAA gave AT&T a $74.3 million initial task order to lead the rebuild. The FAA wants to finish the work by the end of 2028.
Friday's failure was also the largest in a series of communications outages. In the months before it, failed circuits and cut lines stopped traffic at single facilities. In August, for example, a failure at the Minneapolis center grounded flights across nine states.
The difference on Nov. 13 was how far the problem reached. When one center stops working, traffic in one region slows down. When a fault affects every center at once, the FAA cannot send traffic through another region. That is why the order covered every airport in the country.
The restart and the open questions
Flights restarted step by step. A Lufthansa flight from Boston to Frankfurt left at 5:21 p.m. ET. Around 6 p.m. ET, the FAA said flights could depart as the en route facilities recovered. By 6:50 p.m. ET, cargo and passenger flights were leaving the West Coast for Asia and Hawaii.
On the morning of Nov. 14, the reports gave no single time for the full end of the ground stop and no final number of cancellations. The FAA had not named the equipment that failed. It had not confirmed the explanation about the update and the reboot either.
That explanation will decide what this story becomes. A bad software update is a process problem, and a process can be fixed by the next maintenance window. But if one update can take down the network across the whole country, that is a design problem. This is the question that the FAA's rebuild now has to answer.
