Yesterday’s Nationwide Ground Stop Was Only the Second Since 9/11: America Has an Infrastructure Problem
By Easton Martin
The Federal Aviation Administration (FAA) issued a nationwide ground stop yesterday, November 13, halting departing flights across the United States after a telecommunications failure disrupted air traffic control operations.
The widespread disruption was only the second nationwide grounding of all departing flights since the September 11, 2001, terrorist attacks, raising more questions regarding the reliability of America’s aging aviation infrastructure.
The ground stop began Friday afternoon after communication problems affected the FAA’s 22 Air Route Traffic Control Centers. These facilities coordinate aircraft traveling between airports, including planes flying at altitudes above 18,000 feet. The agency halted departures as a precaution to prevent aircraft from entering an airspace where controllers could not reliably maintain normal operations.
Transportation Secretary Sean Duffy later explained that the problem involved an aging telecommunications network.
A contractor, L3Harris, had been performing routine maintenance to replace outdated copper wiring with fiber-optic connections. During that process, a router apparently began flooding other routers across the network with excessive connection attempts. The resulting instability affected communications with aircraft and disrupted some radar feeds.
Despite theories, the incident was unrelated to the recently introduced SMART artificial intelligence system. Homeland Security Secretary Markwayne Mullin also said there was no indication of a cyberattack, although investigators were examining the circumstances surrounding the failure.
The immediate problem was eventually resolved, allowing the FAA to lift the ground stop Friday evening after more than four hours. The disruption nevertheless left thousands of flights canceled and delayed, with airlines facing additional complications as they repositioned aircraft and crews.
America has an aging infrastructure problem, and based on an incident of this scale, it seems we can no longer afford to ignore it or push it off.