Technology

FAA Says Network Flood Reached 17 of 22 Air-Traffic Centers During Friday Ground Stop

The agency has identified two potential source sites, but investigators have not settled what triggered the fault. A Sunday flight snapshot shows cancellations without establishing their cause.

Federal Aviation Administration headquarters building and sign in Washington, D.C.
File photo: The Federal Aviation Administration headquarters in Washington, D.C., pictured in a file photo. The image does not show the November ground stop.Runner1928Photo sourceLicense

The Federal Aviation Administration said November 15 that a surge of network connection attempts destabilized legacy equipment and affected 17 of its 22 air-route traffic control centers during Friday’s nationwide ground stop. Flights resumed that evening, but investigators have not determined what triggered the fault.

For travelers, the immediate picture is different from Friday’s shutdown. Air traffic resumed at 8:15 p.m. Eastern on November 13, the FAA said. At 3:56 p.m. Denver time Sunday, FlightAware showed 1,969 cancellations within, into or out of the United States for the day. That snapshot does not establish how many resulted from Friday’s problem. United listed a nationwide air-traffic-control travel waiver for November 13–15 travel; eligibility depends on the ticket and the waiver’s terms.

What the FAA has isolated

The agency said its network received approximately 1,000 connection attempts every four to five seconds. It identified a radar site in Amarillo, Texas, and a radio site in El Dorado, Arkansas, as potential sources. Blocking the two locations stabilized the network, according to the FAA, which also disabled the implicated function on roughly 60 similar routers as a precaution.

Transportation Secretary Sean Duffy said in a November 15 interview that investigators had not determined whether installation or equipment caused the fault. The FAA and service provider L3Harris are continuing their investigation.

The other disruptions are separate stories

The Microsoft incident began November 12. A University of Pennsylvania archive of Microsoft’s service notices marks the affected Microsoft 365 and Exchange incidents as “serviceRestored” and relays a preliminary explanation involving a network-capacity change and a latent connection-handling bug.

NVIDIA announced separately on November 12 that Jensen Huang had resigned as CEO and Colette Kress had become interim CEO. Neither that announcement nor the Microsoft incident record links those events to the FAA network failure. The FAA’s unresolved question is narrower: what caused the surge at the potential source sites.

Read the source material

Sources & references

How we work with sources ↗

Continue reading

More in Technology

Search the publication

Search the articles published on this site.