FAA Ground Stop Cause: Data Flood From Two Sites Halted Flights Nationwide, FAA Says
The FAA says a data flood from sites in Texas and Arkansas destabilized its telecom network Friday, canceling about 12,462 flights nationwide.
5 minute read
The facts, first. The Federal Aviation Administration has published its fuller account of the nationwide ground stop of Friday, November 13, 2026. The FAA says a technical problem hit at approximately 3:30 p.m. ET; the system was made stable and air traffic resumed as of 8:15 p.m. that evening. Legacy equipment became unstable when data flooded the FAA Telecommunications Infrastructure (FTI) network at a rate of about 1,000 connection attempts every 4 to 5 seconds. The initial investigation points to two potential locations for the excessive data: a radar site in Amarillo, Texas, and a radio communications site in El Dorado, Arkansas. Operators canceled approximately 12,462 flights on Friday, including 9,082 by major airlines. About 3,500 aircraft were in the air when the stop was imposed; all of them landed safely.
This is the follow-up this desk has been watching for since our first-day coverage of what happened at Orlando International Airport. It refines that account in one detail: the FAA’s question-and-answer page puts the technical problem at approximately 3:30 p.m., where the first-day advisories this desk reported were timed at 3:54 p.m. The fuller account below is the FAA’s own, and the investigation behind it is not finished.
What the FAA says happened inside the network
The flooding data disrupted the system and created instability with aircraft communications and radar feeds. The FAA says the instability began at 17 of its 22 Air Route Traffic Control Centers and spread into several Terminal Radar Approach Control facilities, which is why the response was a nationwide ground stop, issued, in the agency’s words, out of an abundance of caution.
At the El Dorado site, L3Harris — the FAA’s current network service provider — had been doing work that included deploying a new router. When the data inconsistencies appeared, L3Harris blocked both the Amarillo and El Dorado locations, and the network stabilized. The broadcasting function was also disabled on the new routers as a precaution.
The FAA is explicit about what this was not. It was not a full outage: some frequencies and radar feeds remained reliable throughout, and critical life-saving, law-enforcement and military flights were not affected. Based on all available evidence, the agency says, there is no indication it was a cyberattack or an outside nefarious actor. And the agency attributes the instability to its legacy TDM system — not to its broader modernization upgrades, and not to SMART, its traffic-planning data tool, which the FAA says does not feed information into the air traffic control system.
The cancellation number, with the FAA’s own caveat
The FAA puts Friday’s cancellations at approximately 12,462, including 9,082 by major airlines — and adds, in the same answer, that not all of those cancellations were directly caused by the nationwide ground stop. We are carrying the figure with that caveat attached, because the agency attached it.
What the FAA has still not published is any airport-by-airport breakdown. There is no official MCO cancellation total in this account, and this desk does not publish one it cannot trace to a published GOAA or FAA document — the same standard we applied on the first day, when local television totals for Orlando conflicted with each other and traced to no official document.
What has been done so the Friday before Thanksgiving is not a repeat
Thanksgiving is ten days out, and MCO is heading into one of its busiest stretches of the year — our Thanksgiving guide to the airport sets out the parking and timing picture for residents flying out or picking up. The relevant question from Friday’s failure is what has changed since, and the FAA’s account gives three answers.
First, the originating routers’ functionality was disabled immediately, and the same functionality has since been disabled on approximately 60 similar routers across the system as a precaution. Second, the router replacement that preceded the failure was, the FAA says, routine work at a remote facility of a kind done for decades without impact — maintenance at major facilities is typically done at night — but the agency says it will now reevaluate when replacement and maintenance work is done. Third, the root-cause investigation continues: the FAA and L3Harris are still investigating, and the agency describes its Amarillo and El Dorado findings as the initial investigation. Nothing in the account is presented as a final determination.
The FAA’s closing position is that the system is stable and operations are returning to normal. For Orlando, the practical read is narrower: the failure was in a legacy telecommunications network, not in Orlando’s airspace or airport, the fix applied so far is a precaution repeated across about 60 routers, and the fuller official explanation for any recurrence risk now sits with an investigation that has not yet reported finally. This desk will follow it the same way it followed the first account — when the FAA or the Greater Orlando Aviation Authority publishes the next document, it will be reported here.
More from this desk: the Tourist News hub carries all of Claire Donovan’s resident-side coverage of the visitor economy.
Sources & notes
Federal Aviation Administration, “Nationwide Ground Stop: Questions and Answers,” faa.gov/newsroom (read in full November 16, 2026) — every fact and figure in this story: the approximately 3:30 p.m. ET problem and 8:15 p.m. resumption; the FTI data flood at about 1,000 connection attempts every 4 to 5 seconds; the Amarillo radar site and El Dorado radio communications site; L3Harris’s work at El Dorado, including the new router deployment, and its blocking of both locations; instability at 17 of 22 Air Route Traffic Control Centers spreading into several TRACONs; approximately 3,500 aircraft in the air, all landed safely; approximately 12,462 cancellations on November 13 including 9,082 by major airlines, with the FAA’s caveat that not all were directly caused by the ground stop; no indication of a cyberattack; the legacy TDM attribution; the SMART clarification; the disabled broadcasting function on new routers and the same functionality disabled on approximately 60 similar routers; the reevaluation of maintenance timing; and the continuing FAA–L3Harris root-cause investigation. The November 13 events at MCO are as reported in this desk’s November 15 coverage, linked above. No MCO-specific cancellation total has been published by the FAA or GOAA, and none is claimed here.
Photo: featured image reused from this desk’s November 15 ground-stop coverage (Orlando International Airport, Creative Commons, as credited there).
Orlando Citizen by email
The weekly edition, in your inbox
One email, every Saturday: the week’s edition of Orlando Citizen — the week’s stories, rankings and winners, gathered in one place. Free, and you can unsubscribe at any time.
Spotted an error? Tell us — corrections · How we rank


