FAA Network Extensions Added $1.5 Billion as Aging Routers Remained in Service
Fifty-seven months and $1.5 billion: That is what 11 contract extensions added to the FAA’s air-traffic communications backbone, according to a 2024 Transportation Department inspector general audit. Ten of those extensions were improperly authorized and one was properly authorized. Meanwhile, the network remained dependent on routers manufactured from 2001 through 2006, and federal auditors accumulated warnings about schedules, reliability and oversight across roughly two decades.

The consequences became visible on November 13, 2026, when instability in the FAA Telecommunications Infrastructure network prompted a nationwide ground stop. The FAA said the disruption affected 17 of its 22 Air Route Traffic Control Centers and spread into several terminal-control facilities. The agency reported that approximately 3,500 aircraft landed safely and that some radio frequencies and radar feeds remained available. The network stabilized after the suspected originating locations were isolated, allowing air traffic to resume later that day.
FAA Telecommunications Infrastructure, commonly called FTI inside the industry, is not one router or a single communications line. It is a contractor-managed service connecting air traffic control centers and other FAA facilities. That scope makes its condition a systems-integration issue: hardware age matters, but so do network configuration, maintenance controls, transition planning, contractor performance and the FAA’s ability to supervise the complete service.
A long-running schedule and oversight problem
The FAA awarded Harris Corp., now part of L3Harris, the contract to modernize, operate and manage FTI in July 2002. By 2006, an inspector general audit was already warning that the transition was behind schedule and might miss its planned completion date. The review called for a realistic master schedule, better coordination and stronger performance information. It also found that more than 90% of the contract’s value consisted of fixed-price components for which the contract did not require earned-value management data.
That early control gap was consequential. The FAA was paying for incremental hardware installations rather than successful service activation, while also retaining legacy telecommunications services during the delayed transition. The 2006 audit account said each additional year beyond the expected transition date could raise telecommunications costs by $100 million.
A 2008 follow-up identified continuing reliability problems that disrupted air traffic control operations. In 2009, a telecommunications outage delayed more than 800 flights. An FAA-commissioned safety review then described FTI as obsolete in November 2023, including its dependence on time-division multiplexing, a legacy method of carrying multiple communications streams over shared links.
The 2024 audit moved the issue beyond technical aging and into procurement governance. In addition to counting the extensions, the inspector general found that the FAA had not adequately overseen Harris and lacked sufficient safeguards for privately operated systems. The $1.5 billion therefore represents more than a large contract figure: it measures how long the government prolonged an arrangement while documented control and obsolescence concerns remained.
It does not follow that all extension spending was wasted. A national air-traffic network cannot simply be switched off while its replacement is built. Extensions can preserve continuity, staffing, maintenance and safe operations during a transition. The public-cost problem is whether the FAA had reliable schedules, properly authorized decisions and enough performance data to determine whether each added month purchased necessary continuity or prolonged avoidable dependence on aging infrastructure.
Why aging hardware is only part of the risk
Senior government sources identified the recently affected equipment as Cisco 600 series routers manufactured between 2001 and 2006. Officials said L3Harris technicians were replacing aging copper lines with fiber at a remote facility in El Dorado, Arkansas. Transportation Secretary Sean Duffy said the work produced a flood of data that overloaded other routers. The FAA also examined inconsistencies associated with a facility in Amarillo, Texas.
The FAA said the network received about 1,000 connection attempts every four to five seconds. It disabled the relevant broadcasting function on approximately 60 similar routers as a precaution. Investigators are still determining the root cause, including whether faulty equipment or user error was responsible; the record does not identify an individual as the cause or establish that a router reportedly marked for replacement in 2006 was the device that failed.
From a systems perspective, the incident illustrates the exposure created when modernization must proceed through a live, interconnected network. Replacing copper with fiber may improve capacity and reliability, but installation work also changes interfaces between new and legacy equipment. A disturbance originating at one facility can propagate through shared infrastructure if traffic controls, configurations or older devices cannot absorb the resulting load.
That tradeoff reaches well beyond the FAA and its contractor. Controllers require dependable communications and radar feeds; airlines need predictable network availability to position aircraft and crews; passengers face cancellations and delays; and taxpayers fund both continued legacy operations and the transition to replacement systems. The immediate safety response a ground stop while controllers and pilots used established procedures reduced operational risk, but it shifted the disruption into the transportation system.
The unresolved engineering-policy task is not merely replacing old routers. It is completing the transition without introducing new instability, while giving the FAA enough schedule, authorization and performance control to know what each extension buys. After 57 added months and $1.5 billion, the age of the hardware and the duration of the warnings show why contract governance is part of network reliability, not an administrative issue separate from it.
| More aerospace and engineering stories, right in your MSN feed. Follow AMI on MSN |
By Thomas Caldwell — AMI’s senior editor for mechanical and mobility engineering, covering vehicle electronics, systems integration, electrification, chassis systems, propulsion, and safety policy.
