GAO Bombshell: Air Traffic Runs On Dinosaurs

Airplane seen through terminal windows with empty gate seating
Photo: Dabarti CGI / Shutterstock

A single router rollout in Arkansas flooded the Federal Aviation Administration’s network and froze U.S. departures coast to coast, officials say.

Story Highlights

  • The Federal Aviation Administration linked the ground stop to a data surge tied to a router deployment, not a cyberattack.
  • Investigators focused on facilities in El Dorado, Arkansas, and Amarillo, Texas, after communications feeds destabilized.
  • Aging systems magnified a local failure into a national shutdown, underscoring long-delayed upgrades.
  • Government Accountability Office reviews show most core air traffic control systems are unsustainable or aging past 20 years.

What Triggered The Nationwide Ground Stop

The Federal Aviation Administration said a network failure forced a nationwide ground stop on November 13 at about 3:30 p.m. Eastern Time, with flights resuming after stability returned at 8:15 p.m. that evening. Officials reported that legacy equipment became unstable when data flooded the Federal Aviation Administration Telecommunications Infrastructure at roughly 1,000 connection attempts every four to five seconds. That surge disrupted voice and radar feeds that controllers use to guide pilots safely.

Transportation Secretary Sean Duffy said the event traced to overloaded routers tied to contractor maintenance. Investigators zeroed in on two sites: a radio facility in El Dorado, Arkansas, where a new router had been deployed, and a radar site in Amarillo, Texas. Network gear at those locations overloaded systems that thousands of controllers rely on to manage aircraft, according to reporting sourced to the inquiry. The Federal Aviation Administration emphasized the incident was not a cyberattack in its early findings.

How A Local Glitch Became A National Failure

The ground stop showed how a single fault can cascade when infrastructure lacks strong isolation. The Federal Aviation Administration described a measurable data-flooding event that spread across links that connect control centers. Legacy routing and switching gear struggled under the excessive traffic, which caused inconsistent or lost data across several facilities at once. Localized issues should be contained. But broad dependencies let a spike in one area ripple through the network, taking key tools offline.

Independent explainers and trade reporting described the backbone’s reliance on older technologies and complex interdependencies. They noted how the data surge created confusion across connected systems that handle voice and surveillance feeds. While these accounts echoed official signals on the technical pattern, the Federal Aviation Administration remains the authoritative source for what occurred and how stability returned the same evening. Officials said the initial probe tied the instability to equipment interactions, not malign activity.

Modernization Gaps And The Path Forward

Government Accountability Office reviews found that the Federal Aviation Administration depends on many unsustainable or aging systems. The agency’s assessment counted 51 of 138 systems as unsustainable and 54 as potentially unsustainable. Of the 105 in those two groups, 73 were deployed over 20 years ago, and 40 were over 30 years old. Six dated back more than 60 years. Many of these systems perform critical safety and efficiency functions every day.

These findings match what this outage exposed: old gear can fail loud, and weak isolation lets one site’s trouble spread. Conservative priorities point to a clear fix. Focus dollars on core safety systems, set tight milestones, and hold contractors to results. Replace the most fragile links first. Build guardrails so one router cannot swamp the nation’s airspace again. The Federal Aviation Administration’s own data shows where risk is highest, so accountability and steady upgrades can deliver quick wins.

Sources:

wsj.com, faa.gov, computeleap.com, airwaysmag.com