The United States Federal Aviation Administration (FAA) has issued a Request for Information (RFI) that reveals both the scale of its modernisation ambitions and the magnitude of challenges ahead. The initiative seeks to replace two critical automation systems with a unified Common Automation Platform (CAP), a goal that, if achieved, would represent the most significant air traffic control transformation in a generation.
The stakes are considerable and the technical challenges are formidable. The FAA currently operates separate systems for different airspace domains: the En Route Automation Modernisation (ERAM) platform manages high-altitude flights at 20 control centres, while the Standard Terminal Automation Replacement System (STARS) coordinates aircraft at 145 approach facilities and more than 400 towers. Together, these systems process data for roughly 45,000 daily flights.
Unifying these platforms promises operational benefits: streamlined maintenance, consistent controller interfaces and reduced lifecycle costs. However, ERAM and STARS evolved from different technological generations and serve fundamentally different operational requirements. Building a system that serves both domains without compromising the strengths of either represents a significant engineering challenge. A unified platform that proves clunky for terminal work or loses critical en route functionality would make operations worse rather than better.
Safety validation cannot be rushed
Beyond technical integration lies the rigorous safety certification process that governs all air traffic control systems. Every software component must achieve Development Assurance Level certification under DO-178C standards, examining not merely whether code functions correctly but whether development processes meet exacting quality requirements.
When STARS replaced older terminal automation, facilities operated both systems simultaneously for up to two years, comparing outputs and validating edge cases before controllers relied exclusively on new technology. That parallel operation period couldn’t be abbreviated through additional funding or political pressure. Multiplying such validation requirements across hundreds of facilities while maintaining operations creates what experts call exponential complexity.
The organisational challenges match the technical ones. The FAA’s Air Traffic Organisation employs approximately 14,000 controllers across more than 300 facilities. Deploying new automation requires extensive training without reducing operational capacity. Facilities already operating below target staffing levels face particularly acute challenges.
The National Air Traffic Controllers Association has expressed support for modernisation while emphasising the importance of controller involvement. “Modernisation efforts succeed when they’re built with controllers, not merely for controllers,” the association’s president Nick Daniels has stated. That distinction matters given recent workforce pressures from retirements, training bottlenecks, and recruitment difficulties.
The vendor lock-in problem
Perhaps most revealing is the FAA’s unprecedented emphasis on preventing vendor lock-in. An entire section of the RFI demands detailed explanations of how contractors will ensure the agency “always retains practical, technical and legal freedom to integrate, transition and interoperate” with other systems.
The specificity reflects institutional memory of proprietary platforms where sole-source suppliers controlled intellectual property, data formats, and interface specifications. Once deployed, such systems became de facto monopolies where competition vanished and costs escalated. The FAA now seeks data portability guarantees, source code escrow arrangements and periodic “portability fire drills” to validate that theoretical escape clauses remain viable.
Features that make platforms unified and integrated are often precisely those creating vendor dependency. Seamless operation requires proprietary optimisation, which subsequently locks agencies into single suppliers.
Political timelines meet engineering reality
Underlying all challenges is tension between political timelines and engineering reality. Transportation Secretary Sean Duffy’s announcement implied delivery within the current administration’s tenure, a timeframe measured in years, not decades.
Historical precedent suggests caution. NextGen, launched in 2003, consumed 22 years and more than $15bn (€13bn) while delivering approximately 16% of promised benefits. The ERAM deployment itself consumed nearly a decade. STARS required similar timescales. Globally, Nav Canada’s evolution towards digital platforms occurred over more than 15 years with careful stakeholder consultation. Australia pursued phased modernisation, deploying capabilities at individual facilities and expanding only after proving success.
Notably, the CAP RFI avoids stating explicit timelines.
The choice ahead
As the FAA evaluates responses (due 19 December), the fundamental choice is whether to embrace incremental modernisation delivering measurable benefits over extended timelines or pursue comprehensive transformation risking NextGen’s pattern of partial delivery.
DataComm, the FAA’s digital controller-pilot communication system, succeeded precisely because it was deployed incrementally, whereas programmes promising comprehensive transformation may generate compelling announcements but frequently deliver partial results after extended delays.
For controllers, the salient question is whether new systems will genuinely improve their ability to manage aircraft safely. For the flying public, whether modernisation will enhance safety and reduce delays. For taxpayers, whether billions in investment will produce commensurate returns.
The FAA has learned some lessons, hence the RFI’s emphasis on vendor independence and operational effectiveness. Whether those lessons translate into different outcomes depends on whether US political culture can accommodate the extended timelines that successful modernisation requires, or whether pressure to demonstrate rapid results will compromise the careful, methodical approach that safety-critical systems demand.
Industry responses over coming weeks will provide the first indication of which path forward is likely to prevail, and whether this initiative represents genuine transformation or merely the latest chapter in a familiar story of aviation modernisation ambitions exceeding realistic delivery capabilities.
