Live coverage of the FAA nationwide ground stop, 13 November 2026Last checked: Monday 16 November 2026, about 05:30 ET
Home › Is It Safe to Fly After the FAA Ground Stop?
FAA Ground Stop · 13 Nov 2026

Is It Safe to Fly After the FAA Ground Stop?

The question every traveller asked after the ground stop was whether flying was safe. The FAA's answer is that safety was not compromised: about 3,500 aircraft were in the air when the stop was ordered, and every one landed safely. This page gives the FAA's safety case in full, and the limits of what it proves.

In short

The FAA says safety was not compromised. About 3,500 aircraft were airborne when the nationwide ground stop was ordered at 3:54pm ET on Friday 13 November, and approximately 3,500 landed safely, with every passenger arriving safely. The failure was not a complete loss of communications: some radio frequencies and radar feeds remained reliable throughout. Critical operations — life-saving, law-enforcement and military flights — continued during the stop. The FAA says it took measures before resuming operations, including disabling the broadcast function on the routers involved, and checked the system before traffic was allowed to move again. The agency's position is that the stop itself was the safety measure: it held aircraft on the ground rather than letting them fly into a degrading system.

What the FAA says about safety

The FAA's questions-and-answers document, published Sunday 15 November, addresses safety directly. Asked whether safety was compromised, the agency's account is that the stop was ordered for reasons of safety before the degradation could become dangerous, and that the aircraft in the air were not at risk. Asked how many flights were in the air, the FAA says approximately 3,500 aircraft safely landed and every passenger arrived safely. Asked whether radio and radar communications with aircraft were lost, the FAA says no: this was not a full outage, and some frequencies and radar feeds remained reliable. Asked whether critical operations continued, the FAA says yes — life-saving, law-enforcement and military flights continued. Asked what measures were taken before resuming operations, the FAA describes disabling the broadcast function on the routers involved and checking the system before traffic resumed. The through-line is that the ground stop was a precaution taken while the system was still partly working, not a response to a system that had already failed completely.

Why the stop was itself the safety measure

The distinction matters. A ground stop is not what happens when flying becomes unsafe; it is what happens to keep flying safe. Controllers need reliable voice contact with pilots and reliable radar pictures of where aircraft are. When 17 of 22 control centres became unstable, the FAA could not guarantee that reliability for departing aircraft. Holding departures on the ground removed the exposure. Aircraft already airborne were in a different position: they were already talking to controllers on frequencies that remained reliable, and they were allowed to continue and land rather than being ordered down immediately. That is standard practice in a ground stop, and it is why the 3,500 airborne aircraft landed without incident. The risk the FAA was managing was the risk of launching more aircraft into a system whose communications were degrading, not a risk to the aircraft already flying.

What the safety case does not prove

The FAA's safety account is strong on Friday's outcome and thinner on the future. It proves that no aircraft was lost and no passenger was harmed during the stop. It does not prove the underlying vulnerability is fixed. The root cause — faulty equipment, installation error or configuration — is still under investigation, and the two suspect routers are under diagnostic testing in Florida. The precaution taken so far is disabling the broadcast function on the routers involved and on approximately 60 similar routers, or 69 by Secretary Duffy's count. Whether that precaution is enough, and whether the same failure could happen at another site, are questions the investigation has not yet answered. Secretary Duffy has warned that without a new air traffic control system, more failures of this kind will happen. That warning is itself a reason to read the safety case as a statement about Friday, not a guarantee about the system.

Should you fly on Monday?

Nothing in the official record suggests Monday flying is unsafe. The FAA resumed traffic on Friday evening after checking the system, and the agency's position is that operations are safe. The practical risks on Monday are disruption, not safety: knock-on cancellations from aircraft and crews still out of position, and delays if the network is running with no slack. The advice from every outlet, and from the FAA itself, is the same: check your flight status before leaving for the airport, on the airline app or FlightAware or the FAA's National Airspace System status page. If your flight is operating, the safety question has been answered by the FAA. If it is cancelled, the question becomes a refund question, and our refunds page covers it.

Frequently asked questions

The FAA says safety was not compromised. About 3,500 aircraft landed safely during the stop, some frequencies and radar feeds stayed reliable, and critical flights continued.

The FAA says no. The stop was ordered as a safety measure, before the communications degradation could become dangerous, and no aircraft was lost.

Yes. Approximately 3,500 aircraft were airborne when the stop was ordered, and the FAA says every passenger arrived safely.

No. The FAA says this was not a full outage — some frequencies and radar feeds remained reliable throughout.

Yes. Life-saving, law-enforcement and military flights continued, according to the FAA.

The FAA says it took measures before resuming operations, including disabling the broadcast function on the routers involved, and checked the system before traffic was allowed to move again.

Sources & check time. FAA, Nationwide Ground Stop: Questions and Answers (15 Nov 2026). 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.