Nationwide ground stop
17 of 22 en route centers unstable, per the FAA. It has not said which.
Gray: nationwide ground stop
Pick a failure to see how far it reached.
- Where it started
- Two possible sourcesEl Dorado, Ark. and Amarillo, Texas, the FAA’s initial investigation says
- How far it reached
- Nationwide ground stopAbout 3,500 aircraft landed safely, the FAA says
- Duration
- About 3:30 to 8:15 p.m. ETFAA account; approximate
- Flights affected
- About 12,462 canceledFAA count; not all directly caused by the stop. FlightAware counted 9,067 within, into or out of the U.S.
What failed, per the FAA
- Data began flooding the FAA’s FTI telecom network at 1,000 connection attempts every 4 to 5 seconds.
- Legacy equipment became unstable at 17 of 22 en route centers (the FAA facilities that guide planes between airports), and the problem spread into several approach facilities. About 3,500 aircraft in the air landed safely.
- The initial investigation points to El Dorado, where L3Harris, the FAA’s network contractor, was installing a new router, and Amarillo, where Transportation Secretary Sean Duffy said work had happened weeks earlier. The FAA says L3Harris blocked both sites and the network stabilized.
- Air traffic resumed as of 8:15 p.m. and broadcasting was disabled on all new routers as a precaution.
The FAA calls the work a routine replacement at a remote facility. Duffy said the El Dorado copper line had become unusable and the phone company required the switch to fiber.
Work to retire 5,170 copper lines
The FAA says this kind of work has gone on for years to move off copper lines being disconnected as obsolete, and that the instability came from its legacy TDM system, not its upgrades. GAO says the FAA had replaced 2,560 of 5,170 copper lines as of May 2026.
GAO’s Sept. 2026 report found no reliable lifecycle cost estimate or integrated master schedule for the program. The nationwide stop before this one, Jan. 11, 2023, was traced in the FAA’s preliminary review to contract staff who deleted files by mistake.
Three days of cancellations
FlightAware counts canceled flights within, into or out of the U.S.; the FAA does not say how its count is scoped.
- Friday, Nov. 139,067
- Saturday, Nov. 146,700
- Sunday, Nov. 152,325
Sunday’s count was about a quarter of Friday’s.
The FAA separately counts about 12,462 cancellations on Nov. 13, including 9,082 by major airlines (a different count from FlightAware’s). It says the ground stop did not directly cause every cancellation. FlightAware’s counts are from pages saved Nov. 14 and 16, 2026.
What can happen next
The cause
The FAA and L3Harris are investigating. Duffy said he will make the root cause public. As an example, the FAA’s preliminary review on Jan. 19, 2023, came 8 days after the Jan. 11 outage.
The White House
CBS News reported that the Homeland Security Council invited officials and outside stakeholders to a meeting on Monday, Nov. 16, on next steps.
The money
- Enacted July 2025$12.5 billion
- Duffy’s ask to Congress$50 billion
The ask is four times the enacted amount.
Duffy said the enacted funds are already committed. AvBrief reported that his $50 billion ask is $20 billion above an earlier request in 2026. Congress decides on the ask. Rep. Jim Himes said it is “not immediately a spending problem” but “a prioritization problem,” according to CBS News.
Undecided: the root cause, and whether Congress adds money.
How to read this
Dots are placed at city positions. The map shows no network routes. The FAA has not named the affected centers. FlightAware’s pages roll daily; counts are as saved.
Sources
- FAA Q&A (Nov. 15, 2026)
- FAA facility list (Jan. 13, 2026)
- FAA NOTAM statements (Jan. 11 and 19, 2023)
- GAO-26-107992 (Sept. 14, 2026)
- CBS News (Nov. 14 and 15, 2026)
- CBS News, Duffy (Nov. 15, 2026)
- Nextgov (April 2026)
- AvBrief (Nov. 15, 2026)
- FlightAware, cancellations for Fri. Nov. 13 (page saved Nov. 14)
- FlightAware, cancellations for Sat. Nov. 14 (saved Nov. 16, 2026)
- FlightAware, cancellations for Sun. Nov. 15 (saved Nov. 16, 2026)
- U.S. Census Bureau boundaries via us-atlas