Dr. Philip D. Mann shares his opinion on the Peraton win and next steps for implementation
The Federal Aviation Administration’s (FAA) decision to name Peraton as prime integrator for the United States’ Brand New Air Traffic Control System (BNATCS) is the most consequential US airspace infrastructure move since the early NextGen era. Washington has bet on a single prime integrator to rationalise a fragmented, brittle automation landscape. The harder question is whether this structure, the funding behind it, and the chosen contractor can deliver what the National Airspace System (NAS) actually needs.
Why the integrator model matters
For nearly two decades, FAA modernisation has been defined by distributed responsibility. NextGen spread capabilities across multiple programme offices, overlapping vendor footprints, with an acquisition structure that made “who owns the outcome?” a surprisingly difficult question to answer. Oversight reports have been blunt: the FAA achieved only a fraction of the operational benefits initially projected despite tens of billions committed over multiple administrations.
BNATCS is an explicit attempt to correct that pattern. Rather than continue with programme-by-programme incrementalism, the US Department of Transportation (DOT) and the FAA have placed one integrator at the centre of a multi-billion-dollar transformation. This creates a clearer accountability chain when integration failures occur, but the same centralisation that simplifies governance also concentrates operational, technical, and schedule risk in a single enterprise relationship.
The ‘neutral integrator’ argument
The competition came down to Peraton versus a rival team led by Parsons and IBM, with several major incumbents sidelined by organisational conflict-of-interest (OCI) constraints. In response to concerns that vendors were shaping architectures around their installed bases, the solicitation barred firms from serving both as major systems suppliers and as the prime integrator.
Peraton framed itself as a non-legacy FAA automation vendor, arguing it can evaluate options across the market without the gravitational pull of its own deployed systems. The company pointed to Peraton Labs’ work for the Department of Defense, Department of Homeland Security and the National Aeronautics and Space Administration to argue its management credentials and present its experience of other programmes with comparable complexity to the NAS.
For radar and surveillance professionals, the key question is whether a “neutral integrator” translates into better decisions about consolidating surveillance inputs and balancing reuse of proven systems versus the introduction of new platforms. Peraton’s lack of deep legacy FAA platform ownership removes one set of biases, but it does not eliminate competitive pressures or political forces.
Physics versus politics
On paper, BNATCS carries a $12.5bn allocation. US Transportation Secretary Sean Duffy and DOT officials have made clear, however, that the full modernisation vision is closer to $31.5bn, with substantial gaps for key elements like the Common Automation Platform. At the same time, the administration continues to message a three-to-four-year modernisation horizon.
For practitioners, that combination should trigger immediate concern. When the difference between authorised funding and estimated need is nearly $19bn, the system does not modernise; it reprioritises, defers and descopes. NextGen’s experience showed that large-scale NAS changes often slipped by years due to integration complexity, certification hurdles and workforce factors. Unlike defence or space programmes, air traffic control modernisation must occur without downtime: every rushed milestone will be taken under live-traffic conditions.
Where the integrator will be tested
Peraton’s real test will not be in vision documents but in navigating technical and operational chokepoints that have stalled previous efforts. Consolidating ERAM (en route) and STARS (terminal) into a Common Automation Platform is the lynchpin of BNATCS. The integrator must maintain backwards compatibility with diverse radar, ADS-B and multilateration feeds while ensuring latency and track quality meet current baselines. Any degradation in correlation or tracking stability during transition will be immediately visible to controllers.
Meanwhile, modernisation proceeds against the backdrop of a nationwide air traffic controller shortage and high operational tempo. Any deployment plan that assumes unlimited capacity for training on new tools or rapid adoption of new human-machine interfaces will collide with operational reality.
What this means for the surveillance community
Firms providing radar processing, ADS-B, multilateration and data fusion tools will now have to navigate both FAA channels and Peraton’s integration roadmap. Alignment with Peraton’s interface and data model standards will become a prerequisite for long-term relevance. A truly data-centric architecture will favour modular, service-oriented components; closed, stovepiped systems will be at a disadvantage.
Designating Peraton as prime integrator was an inevitable evolution. But the decision does not resolve the structural issues that have hobbled previous efforts: the funding gap remains, the timeline is at odds with safety-critical integration physics, and workforce constraints are as tight as ever. What changes now is that success or failure will be far easier to trace, and that clarity is an opportunity for the radar and surveillance sector to demand more realistic planning and genuinely open architectures.
