Independent newsroom

Monday, November 16, 2026

The File

Every claim traces to a primary source. Uncertainty is labeled. Corrections are public.

Safety · Monday, November 16, 2026

FAA names two possible sites behind Friday's nationwide ground stop

The File desk · Nov. 16, 2026, 6:24 a.m. ET

Partially confirmed1 primary sourcesUpdated 6:24 a.m. ET, Nov. 16

Status

Partially confirmed. What the FAA states on its questions-and-answers page dated Sunday, November 15, 2026, is confirmed; this desk opened that page. The root cause is partially confirmed: the page calls Amarillo and El Dorado potential locations and says the investigation continues.
  • Confirmed
    The FAA page dated November 15, 2026, gives the two sites, the El Dorado router work, the flood rate, the 17 of 22 centers, the cancellation counts, the roughly 60 routers, the 3:30 p.m. start, and the 8:15 p.m. resumption.
  • Partially confirmed
    The root cause is the FAA's initial investigation. It names two potential locations and says the FAA and L3Harris are still investigating.
The problem began "at approximately 3:30 p.m. ET" on Friday, November 13, 2026, and it ended in a nationwide ground stop, which holds flights on the ground.1 Where did the data flood behind it come from? The Federal Aviation Administration now points to two possible places: a radar site in Amarillo, Texas, and a radio communications site in El Dorado, Arkansas.1
That account is on the agency's questions-and-answers page dated Sunday, November 15, 2026.1 The page calls both sites "potential" locations.1
The flood hit what the page calls the FAA FTI network, which it also calls the FAA's telecommunications network, and it never spells out the letters FTI.1 The data came "at a rate of 1,000 connection attempts every 4 to 5 seconds."1
The trouble did not stay in one place. "We began experiencing instability at 17 of our 22 Air Route Traffic Control Centers, and it spread into several Terminal Radar Approach Controls," the page says.1 The first are the centers that watch planes on the long routes between airports. The second watch planes nearer the airports.
It was not a total collapse, either. The page says "this was not a full outage. Some frequencies and radar feeds remained reliable."1 And it explains how the flood stopped: "When these inconsistencies in the data happened, L3 Harris blocked those two locations and the network stabilized."1 Air traffic resumed "as of 8:15 p.m."1
On Friday, November 13, "operators canceled approximately 12,462 flights, including 9,082 cancellations by major airlines."1 The FAA adds that "not all cancellations were directly caused by the nationwide ground stop."1
Put the two sites side by side. One is a radar site in Amarillo. The other is a radio communications site in El Dorado, where L3 Harris, "the FAA's current network service provider, had been doing work at the El Dorado site, including deployment of a new router."1
But notice what the FAA did not say. The page does not say which of the two sites started the flood.1 It does say this: "Based on all available evidence, we have no indication that this was a cyberattack or an outside nefarious actor."1
On cause, the agency offers a position and an open question. The FAA says the failure "is due to the legacy TDM system."1 That is the agency's position on cause. Yet the same page says, "The FAA and L3Harris continue to investigate the root cause."1
To limit a repeat, the FAA "disabled the same functionality on approximately 60 similar routers in the system."1 That is the broadcasting function. On work done in the daytime, the page says that "based on what happened Friday, we will reevaluate when we do replacement/maintenance work."1
Why it matters (Estimate). Estimate. This is our reading of the FAA's page. The Sunday page moves the account from one unnamed remote site to two named ones, and it says those locations were blocked. But travelers still do not have a finished cause, and the page does not say whether Monday's schedule is back to ordinary.
Two named sites, both blocked, and a root cause the FAA and L3 Harris are still investigating — and that is where things stand.
How we know

Notes

  1. 1.Federal Aviation Administration, "Nationwide Ground Stop: Questions and Answers," dated Sunday, November 15, 2026. The page says the problem began at approximately 3:30 p.m. ET and that air traffic resumed as of 8:15 p.m. It says approximately 3,500 aircraft landed safely. It says the broadcasting function was disabled on the new routers as a precaution, and the same functionality on approximately 60 similar routers. It says none of the upgraded towers that received modifications went down, and that "this is due to the legacy TDM system." This update uses this page only. It does not use television remarks. The page spells the contractor both "L3 Harris" and "L3Harris." Retrieved by this desk Nov. 16. The FAA's statements are confirmed. The root cause is partially confirmed. Source 1. https://www.faa.gov/newsroom/nationwide-ground-stop-questions-and-answers

What is still unknown or disputed

  • The root cause. The FAA says it and L3Harris are still investigating.
  • Which of the two sites started the flood. The page calls both potential locations.
  • Whether flights on Monday, November 16, 2026, are back to a normal day. The page gives no figure.
  • L3Harris's own account. This page is the FAA's.

Primary sources

Every claim in this story is drawn from the documents below. If a fetch failed, that is recorded on the card.

  1. Source 1

    Nationwide Ground Stop: Questions and Answers

    Federal Aviation Administration · November 15, 2026

    The initial investigation indicates that two potential locations as the reason for the excessive data flooding the systems: a radar site in Amarillo, Texas and a radio communications site in El Dorado, Arkansas.

    https://www.faa.gov/newsroom/nationwide-ground-stop-questions-and-answers