FAA nationwide ground stop after air traffic network failure
The FAA halted departures across the US for more than four hours after its telecommunications network became unstable. Officials point to routers but say the root cause is not known yet.
- Started
- Nov 13, 2026, 20:54 UTC
- Ground stop lifted
- Nov 14, 2026, 01:15 UTC
- Duration
- 4 h 21 min
- Full recovery
- Not yet complete
- Geographic scope
- United States
- Last verified
- 12 sources
What happened
- Systems and services affected
- FAA Telecommunications Infrastructure (FTI)Air Route Traffic Control CentersAir traffic control communications
- Kind of failure
- Network equipment
- Sector
- Aviation
- Provider report
- Not yet published
- Status and recovery
- Recovering (last confirmed Nov 15, 2026). The ground stop ended at 01:15 UTC on November 14, and airspace was operating normally by 7:30 a.m. ET that day. Airline schedules had not recovered: FlightAware counted thousands more US cancellations on November 14. Bedford said on November 14 that carriers expected to return to full schedules by the night of November 15.[7][6][11]
Start is the issue time of the FAA's national ground stop advisory (ATCSCC 111). The advisory's effective window ran to 04:30 UTC, but the ground stop was lifted at 8:15 p.m. ET (01:15 UTC). Radio problems were reportedly noticed hours earlier.
What caused it?
Root cause: UnknownOfficials say routers in the FAA's telecommunications network overloaded other routers. FAA Administrator Bryan Bedford says a definitive root cause has not been established.[2][6][5]
Provider report: Not yet published. No FAA root-cause report yet. The FAA Administrator says a definitive cause has not been established.[2]
How the failure happened
The root cause has not been established, so no diagram is shown.
Explanation
Both versions summarize the sourced claims on this page. Our own interpretation appears only under Independent analysis.
Plain language: what happened and why people were affected.
Air traffic controllers depend on a nationwide communications network to talk to each other and to planes. On November 13 that network became unstable, and the FAA stopped all departures across the country for more than four hours to keep flights safe.
Officials say a router began flooding other routers with connection attempts. The router was part of work to replace old copper lines with fiber. Thousands of flights were canceled over the following days.
Officials say they have no evidence of a cyberattack. The exact cause is still being investigated.
Independent analysis
Our interpretation of the sourced facts. Not a statement by the provider or officials.
Duffy describes one router sending over 1,000 connection attempts every four to five seconds to other routers. A flood like that can exhaust the routers' processing capacity so they drop connections, which would fit the instability the FAA describes. This is consistent with the official account; it is not a finding.
Confirmed and unknown
Confirmed
- Confirmed
Stated or reported, not confirmed
- Preliminary
- Reported
- ReportedPreliminary findings point to Cisco 600 series routers made between 2001 and 2006, which became overloaded and sent out-of-sync data into the air traffic control system.[7]Said by: CBS News, citing preliminary findings · Evidence: News
- PreliminaryThe root cause has not been established.[2]Said by: FAA Administrator Bryan Bedford · Evidence: News
- ReportedIt was the longest halt of departures at US airports since 9/11.[2]Evidence: News
Sources disagree
- DisputedCancellations on November 13 are put at roughly 4,700 (Flightradar24) to nearly 8,000 (CBS News, BBC); FAA Administrator Bedford put them at more than 9,000. FlightAware counted more than 6,400 more on November 14; NBC News, citing FlightAware, reported 5,600 as of 6 p.m. ET that day.[8][12][6][11]Evidence: News, Secondary
Denied
Still unknown
- Whether the fault was installer error, a faulty router, or a network design weakness.
- Who performed the router work: officials name L3Harris; L3Harris has not said.
- How one router could destabilize a nationwide network, and why safeguards did not contain it.
Timeline
Times in UTC. Dates without a time mean the sources give no time. Only events a source documents are listed.
- First observedNot documented
- AcknowledgedNov 13, 2026, 20:54 UTC
- MitigationNov 14, 2026, 01:15 UTC
- RecoveryNov 14, 2026
- ResolvedNot documented
- Incident reportNot yet published
- FAA expands its SMART AI traffic management tool to all centers (later denied as a cause).[12]
- AcknowledgedFAA issues a national ground stop: "all airports are ground stopped" due to "extraordinary circumstances and for reasons of safety" (advisory ATCSCC 111).[1]
- At the FAA's request, US-bound departures from Eurocontrol member states are suspended until 05:00 UTC.[12]
- After the incident endedBedford projects 4,000 to 5,000 cancellations of about 41,000 flights scheduled that day and says carriers expect full schedules by the next night.[11]
- Start to: Ground stop lifted4 h 21 min
Related incidents
Links stated by providers or officials carry their evidence label. “Similar failure” is a comparison of documented causes, not a causal link.
- Not connected
A Microsoft spokesperson told NBC News there was "no indication that the FAA ground stop was related to the service disruption."[11]
- Similar failure (comparison)
The previous nationwide departure halt. Both involve contractor work on FAA systems; the 2026 cause is not yet established.[10][5]
Evidence and sources
Grouped by type of evidence. Numbers match the citations above.
Primary: provider and official sources
Published by the provider or agency itself: incident reports, status records, advisories, statements.
- 1.ATCSCC Advisory 111: National ground stop (opens in a new tab)FAA Air Traffic Control System Command Center · Official statement · Published · Accessed
Independent reporting
News organizations reporting statements, impact and their own findings.
- 2.'Root cause' of nationwide ground stop is unknown, FAA says (opens in a new tab)CNBC · News · Published · Accessed
- 3.FAA lifts ground stop after four hours, but flight cancellations will stretch into the weekend (opens in a new tab)CNBC · News · Published · Accessed
- 4.Nationwide ground stop followed contractor upgrade to L3Harris telecommunication system: DOT's Duffy (opens in a new tab)CNBC · News · Published · Accessed
- 5.US aviation shutdown blamed on L3 Harris installed router (opens in a new tab)Reuters (republished by bdnews24.com) · News · Published · AccessedRepublished copy of the Reuters report; the original is behind a paywall. Date is the republisher's (Dhaka time).
- 6.FAA ground stop latest updates: Duffy blames contractor L3Harris (opens in a new tab)Yahoo News · News · Publication date not recorded · AccessedLive page; read version updated Nov 15, 2026, 02:05 UTC.
- 7.FAA issues nationwide ground stop, White House says no indication of 'nefarious act' (opens in a new tab)CBS News · News · Publication date not recorded · AccessedNo publication time shown; read version updated Nov 14, 2026, 9:43 a.m. EST.
- 8.FAA ground stop lifted: Why were US flights grounded, and what's next? (opens in a new tab)Al Jazeera · News · Published · Accessed
- 9.'Not true': National Weather Service says tech issues regional, not widespread (opens in a new tab)WBTV · News · Published · Accessed
- 10.FAA says NOTAMs outage was caused by contractor deleting files (opens in a new tab)FedScoop · News · Published · Accessed
- 11.Flight chaos continues as air travel attempts to get back to normal after ground stop (live updates) (opens in a new tab)NBC News · News · Published · AccessedLive blog, updated November 15, 1:01 a.m. ET. Quotes FAA Administrator Bedford, FlightAware data and a Microsoft spokesperson.
Reference and third-party analysis
Encyclopedias, aggregators and outside analysis or measurement. Used for context, not as the only support for a confirmed claim.
- 12.2026 FAA nationwide ground stop (opens in a new tab)Wikipedia · Reference · Publication date not recorded · Accessed
Last verified against these sources on Nov 15, 2026.