The facts

  1. FAA Advisory 005 cancelled the nationwide ground stop at 01:19 UTC on Nov. 14. [2]

  2. The FAA said its legacy network became unstable amid excessive data and that the disruption affected 17 of 22 air-route traffic control centers. The agency said some radio frequencies and radar feeds remained available, all aircraft landed safely and it had no indication of a cyberattack. [3]

  3. AP reported Nov. 17 that the FAA paused installing Juniper routers and disabled their relevant functions after technicians linked the issue to a newly installed router in El Dorado, Arkansas. Transportation Secretary Sean Duffy said the communications and radar instability reached 17 of 22 regional centers; the FAA has not identified the root cause. [5]

  4. The FAA Command Center status page last updated at 05:45:05 UTC Nov. 18 listed no national programs, ground stops or airport closures. It showed local weather-delay entries at Fort Lauderdale and Miami and Pittsburgh deicing. [4]

  5. The FAA reported approximately 12,462 cancellations on Nov. 13, including 9,082 by major airlines, and said not all were directly caused by the nationwide ground stop. [1][3]

Still unconfirmed

  • The final technical cause of the instability and the specific contribution of the El Dorado router remain under investigation.
  • The FAA status page does not establish whether every airline schedule had returned to baseline.
  • The FAA has not said when paused router installations will resume.

Corrections & updates

Substantive update, 13 November: added AP’s report that the communications issue affected 22 regional centers and that no restart timeline was available, plus the FAA advisory Axios quoted at 22:05 UTC, still directing departures to remain grounded until further notice. Cause and restart time remain unknown; the advisory and government accounts are attributed. Original URL and publication date are unchanged.

Substantive update, 14 November UTC: replaced the earlier projected stop horizon with AP and ABC reports that the FAA lifted the nationwide stop. Added their differently timed diversion and cancellation counts and airline warnings about continuing disruption. The figures are not final; Duffy’s technical explanation remains attributed and the cause is not independently established. Original URL and publication date remain unchanged.

Substantive update, 14 November: added ABC’s 02:37 UTC live update, which attributed nearly 800 Saturday cancellations and nearly 5,000 Friday cancellations to FlightAware. Counts remain time-specific and not final. The nationwide departure stop remains reported as lifted; the technical cause is not independently established. Original URL and publication date remain unchanged.

Substantive update, 14 November: added AP’s 07:11 UTC report that more than 2,500 Saturday flights were canceled and hundreds delayed after the FAA lifted its stop Friday evening. Its snapshot differs from ABC’s earlier FlightAware counts and is not final; the figures are kept time-specific and uncombined. The technical cause remains unestablished.

Substantive update, 14 November: refreshed restrictions using the FAA national-status page last updated at 08:57:01 UTC and the earlier operations-plan advisory. The status page listed no national program or ground-stop entry; the advisory's listed airline-requested local stops were scheduled to end by 03:15 UTC, hours before the snapshot. AP's time-specific Saturday cancellation snapshot remains the latest opened broad count. The nationwide departure halt is described as ended, not active.

Substantive update, 14 November: added the later FlightAware snapshot of 3,421 cancellations and 1,111 delays and FAA's 11:00 UTC plan listing no active terminal constraints. The FlightAware daily totals are not attributed to the FAA halt; its technical cause remains unestablished. Original URL and publication date remain unchanged.

Substantive status update, 14 November: refreshed the FAA Command Center snapshot at 13:11:25 UTC. It showed no national program and one local ORD stop for second-tier United and subsidiaries through 14:00 UTC, marked other/airline request. The local stop is not attributed to the Nov. 13 nationwide communications issue; the national halt remains lifted. FlightAware's 3,421 cancellations and 1,111 delays remain a U.S. daily aggregate, not an event-causal count.

Substantive update, 14 November UTC: refreshed FAA National Airspace System status. It showed no national programs and a United-only O'Hare stop through 15:00 UTC marked carrier request; the FAA page did not connect it with the previous day's nationwide communications disruption. The nationwide halt remains lifted.

Substantive update, 14 November UTC: refreshed FAA status at 15:40:09 UTC. The page showed no national programs, ground stops, delay information or airport closures; the earlier United-only ORD request stop had expired. The nationwide halt remains lifted, the technical cause is not established, and FlightAware’s daily U.S. totals are not attributed wholesale to the halt.

Updated Nov. 14, 2026: Added FAA status at 16:57 UTC and Advisory 083’s 17:00–23:59 UTC FCASD1 program for surface congestion; the advisory does not link it to the prior communications failure.

Substantive update, 14 November UTC: added Axios’s Saturday account that Duffy said FAA systems were back at full operations and Administrator Bryan Bedford expected schedules to normalize by Sunday. FlightAware totals were more than 4,700 cancellations and 13,500 delays and are not all attributed to Friday’s halt. Refreshed the 17:44 UTC FAA status: a national surface-congestion program and a separate Southwest-only SAN stop were listed; Advisory 090 says the latter was an airline request through 18:15 UTC. The contractor/router explanation remains under investigation, not an independent root-cause finding.

Substantive status update, 14 November UTC: added the FAA’s cancellation of the nationwide stop and its 21:00 UTC operations plan listing no active terminal constraints. The plan names separate localized weather/route programs, not a continuation of Friday’s communications-related restriction; full airline recovery remained forecast for Sunday.

Substantive status update, 14 November UTC: checked the latest FAA plan and advisory list. Advisory 102 shows a Delta-only LaGuardia stop through 22:30 UTC; Advisory 104 shows a volume-driven FCASD1 program through 04:00 UTC. Neither is attributed to the prior nationwide communications failure. The plan listed a possible SEA/BFI program after 22:00 UTC, but no SEA/BFI advisory appeared in the list through 21:37 UTC. No later nationwide stop is reported.

Substantive status update, 14 November UTC: the 22:27 FAA plan for 23:00 and later lists no active or planned terminal constraints or airspace-flow programs and confirms the two earlier programs were canceled. The advisory list records cancellation of the Delta-only LaGuardia stop at 22:29. Local weather, route, staffing and runway restrictions remain separate; no renewed nationwide communications-related halt is shown. Recovery cancellation totals remain unattributed beyond their source and time.

Substantive status update, 15 November UTC: the FAA status page last updated at 23:50:30 UTC Nov. 14 listed no national programs, ground stops or delay notices. Its latest plan showed no active/planned terminal constraints or flow programs, while separate localized restrictions remained. Added the attributed account of contractor copper-to-fiber work and repeated connection attempts; final technical cause remains under investigation. Saturday cancellation totals are not attributed wholly to the nationwide stop.

Substantive status update, 15 November UTC: refreshed FAA status at 00:51:08 UTC, showing no national programs, ground stops or delay notices. The latest operations plan lists no active terminal constraints or airspace-flow programs but retains two staffing-triggered ZTL routes; separate local conditions remain. Reuters reports officials suspect a potentially faulty L3Harris-installed router, but Duffy says the investigation has not determined fault. Cancellation and disruption aggregates do not isolate the nationwide halt’s share.

Substantive status update, 15 November UTC: refreshed the FAA status page at 11:31:36 UTC and the 11:00 UTC operations plan. No national program, ground stop, delay notice, active terminal constraint or active flow program was listed; possible local weather, staffing and volume restrictions remain separate. DOT reported fully operational air-traffic systems on Saturday, while airline schedule normalization was still forecast for late Sunday. Full schedule recovery and the technical root cause remain unconfirmed.

Substantive update, Nov. 15: refreshed the FAA national-status check at 13:52:26 UTC and added the Washington Post’s Sunday report citing FlightAware for more than 6,600 Saturday cancellations and at least 1,300 early Sunday. Delta and Alaska warned recovery could continue. The broad cancellation totals do not isolate the halt’s share; officials still had not confirmed full schedule normalization or the outage’s technical cause.

Substantive status update, Nov. 15 UTC: refreshed the FAA page at 16:33:27 UTC. It listed no ground stops, but its program table showed separate DJT runway/taxiway maintenance and a planned SAN volume program, alongside local delay notices. AP still reported full airline schedules were expected by Sunday’s end, not confirmed. Updated the cancellation figures and retained their time/source limits; the outage cause remains under investigation.

Substantive update, Nov. 15 UTC: added the FAA’s preliminary public Q&A on possible radar/communications locations, data flooding and its assessment that there is no indication of a cyberattack. Refreshed the status page at 17:54 UTC: no nationwide ground stop, with a scheduled weather-related AUS stop and separate SAN/SFO programs. AP still described full airline schedule recovery by Sunday’s end as an expectation; completion was not confirmed. No final independent cause finding is established.

Substantive status update, Nov. 15 UTC: refreshed FAA status to the 18:44:50 UTC page, which showed no nationwide ground stop but listed separate SAN/SFO programs, local weather stops at AUS/DAL/SFO and local delays. Added Delta’s 11:15 a.m. ET update that most flights were normal but residual delays and cancellations remained while it worked to fully restore operations. Full schedule recovery and the outage cause remain unconfirmed.

Substantive status update, 15 November UTC: the FAA status page at 22:49:16 UTC listed no ground stops, though MCO had a +45-minute disabled-aircraft delay and TEB a +60-minute volume delay. Advisory 083 says MCO’s local emergency stop had ended; separate weather, staffing and volume programs remained. Delta still reported residual disruption. No nationwide halt or confirmed full schedule normalization is asserted.

Substantive update, 16 November UTC: added the FAA's 23:30:29 UTC status showing no national ground stop and two airport delays, plus its stable-system statement and cancellation total. AP notes not all Friday cancellations were caused by the stop.

Substantive update, 16 November UTC: refreshed the FAA status snapshot to 00:59:47 UTC. It listed no ground stops and showed local Austin, San Francisco and Teterboro programs/delays; these are not a continuing national halt. The FAA says its system is stable while it and L3Harris continue investigating.

Substantive status update, 16 November UTC: refreshed the FAA live National Airspace System page at 04:17:22 UTC. It listed no nationwide or airport ground stop, no delay notice and no airport closure; the only program was a San Francisco low-ceiling program scheduled from 05:00 to 07:59 UTC. This is a local weather flow restriction, not continuation of the nationwide halt. The FAA still says the system is stable while it and L3Harris investigate; airline schedule recovery remains unconfirmed.

Substantive status update, 16 November UTC: refreshed the FAA homepage at about 06:22 UTC and opened the 00:22 UTC Command Center plan. No ground stoppage was listed; one SFO low-ceiling delay and four separately scoped airport notices remained. These local conditions do not mean the nationwide halt returned; airline recovery and the technical cause remain unresolved.

Status refresh, Nov. 16: FAA’s 06:55 UTC homepage snapshot still showed no nationwide ground stoppage; the remaining SFO delay was weather-related and local. Airline schedule recovery remains a separate question.

Substantive status update, Nov. 16 UTC: refreshed the live FAA Command Center page to its 08:07:55 UTC snapshot, which showed no national programs, ground stops, delay information or airport closures. This supersedes the earlier 06:55 snapshot that showed a local SFO weather program and four local notices. The nationwide stop remains lifted; Delta had reported most flights normal on Nov. 15 but residual disruption was still possible, so full airline schedule recovery remains unconfirmed.

Substantive status update, 16 November UTC: refreshed the FAA Command Center page to its 12:22:51 UTC snapshot, which showed no national programs, ground stops, delay information or airport closures. Added American Airlines’ Nov. 14 forecast of a largely normal Monday schedule, clearly labeled as a forecast. Delta’s latest opened report still allowed for residual disruption; full carrier recovery and the technical cause remain unconfirmed.

Substantive update: refreshed the FAA status snapshot to 13:28:56 UTC, which showed no national restrictions and only local deicing notices; airline recovery and the root-cause investigation remain unresolved.

Status refresh, Nov. 16 UTC: refreshed the FAA Command Center status page to its 15:10:51 UTC snapshot. It showed no ground stops, delay information or airport closures, while listing separate SAN volume and SFO low-ceilings programs plus local deicing at ABQ and PIT. Airline schedule recovery and the root-cause investigation remain unconfirmed.

Substantive update, Nov. 16 UTC: refreshed the Command Center status and added AP’s report that officials and the SMART vendor deny a connection. Rollout timing has prompted questions, but the technical cause remains unresolved. The nationwide restriction remains lifted; local programs are distinct.

Status refresh, Nov. 16 UTC: the FAA Command Center page updated at 18:12:12 UTC showed no ground stops or airport closures. Local SAN volume and SFO low-ceiling programs, PIT deicing and a +15-minute LAS weather delay remained. These do not indicate a renewed nationwide halt; full airline recovery and the technical cause remain unresolved.

Substantive update, Nov. 16: added the FAA Command Center's 19:59:54 UTC status snapshot, which showed no national stop but a separate TEB stop scheduled through 20:45 UTC and local SAN, SFO and PIT programs. Added WaPo/FlightAware's Monday cancellation and delay counts, clearly separated from Sunday and not attributed wholly to the FAA stop. Recovery and technical causation remain qualified.

Status refresh, 16 November UTC: the FAA Command Center live status at 20:58:43 UTC showed no nationwide ground stop or airport closure; a local TEB stop was listed through 21:45 UTC and SFO, DCA, SAN and PIT had separate local programs. This does not indicate a renewed national halt; airline normalization remains unconfirmed.

Status refresh, 16 November UTC: the 21:47:30 FAA live status listed no active national or airport ground stops or airport closures. The earlier Teterboro stop had expired; SFO and San Diego still had local delay programs in the latest operations plan. No renewed nationwide halt or completed airline recovery is inferred.

Status refresh, Nov. 16 UTC: the 23:56:11 FAA Command Center snapshot showed no national program or airport closure, but a separate LGA volume stop through 00:45 UTC Nov. 17 and an SFO low-ceilings delay program through 06:59 UTC. These local restrictions are not a renewed national halt. The airline recovery and technical investigation remain unresolved.

Status update, Nov. 17 UTC: refreshed the FAA Command Center page to its 01:43:34 UTC snapshot. It showed no national programs, ground stops, delay notices or airport closures; SAN volume and SFO low-ceilings programs and PIT deicing were local. The previously scheduled LGA stop was no longer listed. No nationwide halt or full airline schedule recovery is inferred.

Substantive status refresh, 17 November UTC: updated the latest FAA Command Center snapshot to 04:06:06 UTC. No national program, ground stop or airport closure was listed; SAN/SFO programs, one SAN delay and PIT deicing were local. Updated the recovery summary and homepage reason; airline normalization and technical cause remain unresolved.

Substantive status and source update, 17 November UTC: clarified the FAA’s preliminary data-flooding account, possible sites and router safeguards while preserving that the investigation continues. Refreshed the Command Center record to its latest available 05:01:57 UTC snapshot, which showed a local SFO weather ground stop and local SAN/SFO programs but no national restriction or airport closure. The snapshot does not establish airline schedule normalization.

Updated Nov. 17 with the FAA’s 09:07:37 UTC Command Center snapshot showing no active national programs, ground stops, delay entries or airport closures; Pittsburgh deicing remained listed, and airline schedule normalization remains unconfirmed.

Update: Nov. 17 UTC - the 11:02:25 UTC FAA Command Center snapshot lists no national programs, ground stops, delay entries or airport closures; Pittsburgh deicing remains. Airline schedule normalization is still unconfirmed.

Status update, Nov. 17 UTC: refreshed the Command Center snapshot to 12:32:13 UTC; it lists no national programs, stops, delay entries or closures, with only Pittsburgh deicing. The stop remains lifted; airline-wide normalization and the FAA’s final cause remain unresolved.

Status update, Nov. 17 UTC: replaced the 12:32:13 UTC Command Center snapshot with the latest retrievable page timestamp, 15:41:42 UTC. It listed no ground stops or airport closures, while showing a PHX low-ceilings program, an LGA wind-delay entry and PIT deicing. These are time-specific/local flow conditions, not evidence that the nationwide stop returned. Airline-wide normalization and the final cause remain unconfirmed.

Status update, 17 November UTC: the FAA’s 19:05:03 UTC Command Center snapshot showed a local Teterboro ground stop for volume/compacted demand, no national programs, Phoenix weather delay and Pittsburgh deicing. This is separate from the cancelled Nov. 13 nationwide halt; current restrictions can change after the snapshot.

Substantive update, Nov. 18: added AP's Nov. 17 report that FAA paused Juniper-router installations and disabled relevant functions after a router installation was linked to instability across 17 of 22 centers; root cause remains unresolved. Refreshed FAA Command Center status at 05:45:05 UTC Nov. 18: no national program, ground stop or closure; FLL/MIA weather delays and PIT deicing were local. The nationwide halt remains lifted.

Sources

References support the numbered facts above. Source checks: 18 Nov 2026, 06:00 UTC.

The FAA Command Center status page was opened at 05:45:05 UTC Nov. 18 and showed no national program, ground stop or airport closure; FLL and MIA weather delays and PIT deicing were local. The FAA's Q&A and the Nov. 17 AP report support the 17-of-22-centers scope, router action and safety qualifications. The FAA and AP both leave final root cause unresolved.

  1. What to know about flights after the US nationwide ground stop

    Associated Press · Reporting · 15 Nov 2026

    AP relays the FAA cancellation total and expressly says not all cancellations were directly caused by the nationwide stop.

  2. ATCSCC Advisory 005 — cancellation of nationwide ground stop

    Federal Aviation Administration · Primary source · 14 Nov 2026

    The FAA Command Center advisory signed at 01:19 UTC Nov. 14 cancelled the nationwide ground stop.

  3. Nationwide Ground Stop: Questions and Answers

    Federal Aviation Administration · Primary source · 15 Nov 2026

    The FAA says its legacy system was unstable, 17 of 22 centers were affected, some feeds remained available, all aircraft landed safely, and it had no indication of a cyberattack. These are the agency's account and assessment, not an independent cause finding.

  4. National Airspace System Status, 18 November 2026 05:45:05 UTC

    Federal Aviation Administration · Primary source · 18 Nov 2026

    Live Command Center status at 05:45:05 UTC showed no national programs, ground stops or airport closures; FLL and MIA had local weather delays and PIT listed deicing.

  5. Congress skeptical as Trump officials seek $50B for air travel system

    Associated Press · Reporting · 17 Nov 2026

    AP reports the FAA disabled Juniper-router functionality and paused installations; Duffy said a new El Dorado router led to intermittent communications and radar signals at 17 of 22 centers, while the agency still lacked root-cause clarity. HPE said the router worked as configured by the installer.

Report a factual error