The Federal Aviation Administration says a flood of data destabilized its legacy network on 13 November and forced a nationwide ground stop. The agency’s questions and answers page, posted 15 November, says the initial investigation points to two potential locations: a radar site in Amarillo, Texas, and a radio communications site in El Dorado, Arkansas.
The ground stop began at approximately 3:30 p.m. ET. The FAA says the system “was made stable and air traffic resumed as of 8:15 p.m. that same day,” roughly five hours later. The agency does not present that as a finished return to normal. It says recovery to normal operations will be slow and steady.
The FAA says the instability hit 17 of 22 Air Route Traffic Control Centers, the facilities that handle high-altitude traffic between airports. The agency says it also spread into several Terminal Radar Approach Controls.
FTI is the FAA’s own shorthand for the network involved, spelled out by the Wall Street Journal as the FAA Telecommunications Infrastructure. It carries the communications and radar data that the en route centers depend on.
Two sites, a data flood, and a network that stabilized once they were blocked
The FAA says its “legacy equipment became unstable when data began flooding the FAA FTI network, at a rate of 1,000 connection attempts every 4 to 5 seconds.” The agency says that “disrupted the system and created instability with aircraft communications and radar feeds.”
L3Harris, described by the FAA as its current network service provider, had been doing work at the El Dorado site, including deployment of a new router. The agency says that when the inconsistencies in the data appeared, L3Harris blocked those two locations and the network stabilized.
Rebecca Guy, the FAA’s technology chief, described the same pattern at a Saturday press conference quoted by the Journal. “We saw two places that were actually pinging our network at a very high rate, a thousand connections over every four to five seconds,” Guy said. “We disabled both of those right away and were able to stabilize our network.”
A day before the FAA posted its Q&A, Andrew Tangel and Drew FitzGerald reported for the Journal that L3Harris had installed a new router made by HPE’s Juniper Networks at the Arkansas location, and that the machine began sending out a high volume of data on Friday afternoon. Data from that router and another at the Texas location overwhelmed the system, government and industry officials told the paper. The Journal reported that when the FAA cut off the routers in Arkansas and Texas from the broader network, the communication problems stopped.
The FAA’s own Q&A does not name a hardware vendor. It names the two potential locations and says “the broadcasting function was also disabled on all the new routers as a precaution.”
The agency says this was routine replacement work at a remote facility, and that it will reevaluate how and when it performs replacement and maintenance work. It also says the failure sat on the legacy TDM system rather than on recently upgraded towers.
Broadcasting disabled on about 60 similar routers while the root cause is open
The FAA says it believes it has addressed the initial cause by immediately disabling the functionality of the originating routers. “As a precaution, we disabled the same functionality on approximately 60 similar routers in the system,” the agency says.
That is a containment step, not a diagnosis. The FAA says it and L3Harris “continue to investigate the root cause and ensure this doesn’t happen again.”
The Q&A does not attach a vendor name to those roughly 60 machines. That detail comes from the Journal, which reported that a government official familiar with the system said about 60 Juniper routers are active and operating normally in the FAA’s air traffic network. The same official described a broadcasting feature that sent data more broadly than necessary, which the agency has since disabled on those routers.
Whether the equipment itself was at fault is unresolved. The Journal reported it was not clear if the problems resulted from a bad router or if L3Harris did not configure it properly.
FAA Administrator Bryan Bedford put the open questions plainly, as quoted by the Journal: “Was it a faulty installation? Was it a faulty configuration? Or was it just a bad piece of router technology that we put into this system that propagated these errors?” He said the FAA is still investigating.
An HPE spokesman told the Journal the Juniper devices “appeared to have been working as intended.” “They did not fail,” he said.
The FAA says the event was not a full outage, and that some frequencies and radar feeds remained reliable throughout. On the question of attack, the agency says that “based on all available evidence, we have no indication that this was a cyberattack or an outside nefarious actor.”
Cancellations, safe landings, and where travelers can check refund options
The FAA says approximately 3,500 aircraft landed safely during the disruption, and that every passenger arrived safely.
Operators canceled approximately 12,462 flights on 13 November, including 9,082 cancellations by major airlines, which the agency says were made out of an abundance of caution. The FAA adds a qualifier in the same breath: “While not all cancellations were directly caused by the nationwide ground stop, all flights landed safely.”
Travelers still sorting out disrupted itineraries can use Make Tech Easier’s earlier guide to tracking flight status and claiming refunds after the ground stop.
Make Tech Easier has also explained how airplane mode combines a 1991 FCC network rule with an FAA interference rule.
The FAA has not set a date for findings. The agency says the investigation with L3Harris is continuing.