HighDisruptionCause not confirmedOngoing

FAA nationwide ground stop halts US flights, cause not confirmed

SecurityWeek and The420.in report an FAA nationwide ground stop on Nov 13, 2026; cause not confirmed, so check airline status before travelling.

Published
Updated
Exploitation
No, not confirmed as an attack; The420.in reports officials found no signs of intrusion in initial inquiries, SecurityWeek says federal officials have not said whether a cyberattack is being investigated

What happened

According to SecurityWeek, the Federal Aviation Administration (FAA) issued a nationwide ground stop for all U.S. airports on Friday afternoon, 13 November 2026, citing “extraordinary circumstances” for safety. SecurityWeek reports that the FAA directed departing flights to remain on the ground until further notice and said it would handle inbound international flights case by case. It also reports that the agency had already halted traffic in Chicago over air traffic control communications problems before the nationwide order. The cause is not confirmed.

The420.in reports further detail, in an article last updated on 14 November 2026:

  • More than 15,000 flights were affected and airlines cancelled over 2,000 services.
  • More than 3,500 aircraft were in US airspace when the disruption began, and The420.in says all of them landed safely.
  • Medical emergency and law enforcement flights were permitted to continue.
  • The FAA Command Center lifted the nationwide ground stop at 8:19 p.m. on Friday, but normal schedules did not return immediately.
  • The420.in says FlightAware reported around 15,000 total disruptions, with more than 2,000 cancellations extending into Saturday.
  • Airlines including Air India urged passengers to verify their flight status before heading to airports.

Bank Info Security carried the story under the headline “US Flights Halted as FAA Communications Systems Fail”. The article text was not available to us beyond that headline, so we do not draw further facts from it.

What has been said

  • 13 November 2026, FAA (via SecurityWeek): SecurityWeek reports that the FAA issued the ground stop citing “extraordinary circumstances” for safety. The FAA’s own cause statement is not quoted in the sources, so what caused the problem is not confirmed from the FAA.
  • 13 November 2026, Sean Duffy, US Secretary of Transportation (post on X, as reported by SecurityWeek): SecurityWeek says Duffy posted that the FAA issued a nationwide ground stop for all U.S. airports following a “communication issue impacting all Air Route Traffic Control Centers”. He also posted: “FAA technicians are investigating the issue. We will provide immediate updates as we have them.” SecurityWeek adds that federal officials had yet to publicly identify what triggered the problem.
  • Reported 14 November 2026, Duffy at official briefings (as reported by The420.in, which gives no direct quotes): The420.in says Duffy stated the technical issue began around 3:36 p.m. Eastern Time on Friday, when radar and communication data feeding into air traffic control centers and terminal radar approach control facilities became unstable. This is a single-outlet account and is not independently confirmed here.
  • Reported 14 November 2026, officials as reported by The420.in only: The420.in says officials attributed the instability to legacy analog equipment, particularly older switches and routers, failing to handle a sudden surge in data load. It says Duffy noted that the problem was not caused by any recent FAA software patch or technical modification. It also says authorities could not yet confirm what caused the spike in data load, and that Duffy said investigators want to avoid releasing inaccurate information before reaching a definitive conclusion. No other source we hold repeats this account, so treat it as unconfirmed.
  • Reported 14 November 2026, Duffy on funding (as reported by The420.in): The420.in says Duffy requested 50 billion dollars in additional congressional funding for system modernization, noting that the previously approved 12.5 billion dollars is insufficient.

Is it a cyberattack?

Confirmed: no source we hold reports an official finding that the disruption was a cyberattack, and none reports an official finding that it was not. SecurityWeek says federal officials had yet to say whether they were investigating a possible cyberattack, and that it was unclear if the incident was linked to one.

Reported, single outlet: The420.in says Homeland Security Secretary Markwayne Mullin confirmed that initial inquiries revealed no signs of suspicious online activity, unauthorized intrusion, or claims of responsibility from any group. It also says he described the disruption as unrelated to any Microsoft technical glitch or outage, and that officials had not completely ruled out any possibility until the investigation concludes.

Not confirmed: the root cause, and any final conclusion on a cyber cause either way. These sources do not show a cyber cause being investigated or ruled in. We therefore list the cause as unconfirmed. A statement from the FAA, the Department of Transportation or the Department of Homeland Security naming a cause, or the conclusion of the investigation, would change this assessment.

What to do now

  1. Check your flight status with your airline before travelling to the airport. The420.in reports that airlines including Air India issued advisories urging this, and that crew scheduling challenges slowed recovery.
  2. Expect delays and cancellations to continue. The420.in reports cancellations extending into Saturday.
  3. Follow the FAA’s and your airline’s official channels for updates. Duffy said on X that updates would be provided as available, according to SecurityWeek.
  4. Do not click links in unexpected emails, calls or texts about the outage, and do not give payment or personal details to anyone who contacts you unprompted. This is general site guidance, not drawn from the sources: scammers exploit outages.

Sources