The United States Air Force decision to award initial production contracts for the first increment of the Collaborative Combat Aircraft (CCA) program establishes a fundamental structural shift in military procurement. By ordering at least 150 semi-autonomous uncrewed fighter aircraft from General Atomics (the FQ-42A) and Anduril Industries (the FQ-44A) to be built by the end of the decade, the military is transitioning from a capital-intensive platform model to a software-defined mass-production framework. The strategic objective is explicit: rebuild airborne combat mass to counter high-end threats on an operationally relevant timeline.
Traditional military aviation procurement operates on decades-long design-to-fielding cycles, producing highly complex, multi-million-dollar crewed assets in low quantities. This model creates a critical structural vulnerability when facing a peer adversary capable of scaling industrial production. The CCA program alters this economic equation by decoupling physical manufacturing from the underlying software intelligence, forcing a new industrial reality where hardware is standardized and software is continuously iterated.
The Unit Economics of Attritable Mass
To understand the strategic rationale of the CCA program, one must examine its strict cost function. Air Force leadership has dictated that the unit cost of an Increment 1 air vehicle must not exceed one-third of the price of an F-35A Joint Strike Fighter. This places the cost target at roughly less than $30 million per tail.
This financial constraint is not merely an exercise in budgetary discipline; it is an operational requirement for attritability. An asset is attritable when its unit cost is low enough that its destruction in combat does not cripple the overall force structure or bankrupt the state, yet its capability is sophisticated enough to achieve tactical objectives. The unit economics dictate a clear cause-and-effect relationship:
- Lower unit costs enable geometric scaling of production lines.
- Increased production volume delivers the mass required to saturate adversary integrated air defense systems (IADS).
- Saturating adversary defenses protects the high-cost, low-density crewed assets, such as the F-35A or the F-22A Raptor, which act as the airborne command nodes.
The Air Force aims to field a baseline fleet of approximately 1,000 CCAs. Operating within a $30 million per unit limit allows the military to scale its fighter capacity without facing the geometric cost inflation that has characterized tactical aviation since the third generation of fighter aircraft.
Structural Asymmetry in Air Vehicle Design
The selection of both General Atomics and Anduril Industries for the Increment 1 physical platforms introduces structural and design diversification into the fleet. The two platforms represent differing industrial heritages and architectural philosophies, reducing overall program execution risk.
General Atomics developed the FQ-42A (formerly the YFQ-42A prototype) using its "genus/species" design methodology, validated alongside the Air Force Research Laboratory via the XQ-67A Off-Board Sensing Station. This approach relies on a common core chassis or "genus" that shares primary structural, landing gear, and baseline subsystem components. Specialized mission variants—the "species"—are then built on top of this standardized core. This methodology shortens the timeline from initial concept to first flight, which General Atomics executed in 15 months. The FQ-42A design prioritizes long-endurance sensing and modular integration of existing aerospace supply chains.
Conversely, Anduril Industries optimized the FQ-44A (formerly the YFQ-44A prototype) for rapid serial manufacturing outside traditional aerospace assembly lines. The FQ-44A features a combat radius exceeding 700 nautical miles, ferry range for global self-deployment, and the ability to operate from short, austere airfields. In field exercises with the Air Force Experimental Operations Unit, the FQ-44A demonstrated it could be launched, recovered, and turned around by a minimal crew with days of training and no heavy base infrastructure. This addresses the logistics bottleneck of forward-area operations.
The dual-source selection ensures that the Air Force avoids a single point of failure in manufacturing supply chains while exploiting two distinct aerodynamic and operational concepts.
Uncoupling Hardware and Software: The A-GRA Framework
The architectural breakthrough of the CCA program lies in the complete separation of the hardware platform from the mission autonomy software. Historically, military aircraft were delivered as monolithic systems where the hardware manufacturer locked the government into proprietary software ecosystems. The CCA acquisition model breaks this paradigm through the implementation of the government-owned Autonomy Government Reference Architecture (A-GRA).
A-GRA provides a standardized software interface layer that functions similarly to an open operating system. Any mission autonomy software built to A-GRA compliance can be ported onto either the General Atomics FQ-42A or the Anduril FQ-44A without redesigning the aircraft flight control computers. This separation creates a dual-track competitive marketplace.
+-----------------------------------------------------------+
| Mission Autonomy Software Pool |
| (Anduril Lattice, Shield AI Hivemind, Collins Aerospace) |
+-----------------------------------------------------------+
|
v [Open A-GRA Interfaces]
+-----------------------------------------------------------+
| Standardized Government Reference Layer |
+-----------------------------------------------------------+
|
+----------------------+----------------------+
| |
v v
+-----------------------------+ +-----------------------------+
| General Atomics FQ-42A | | Anduril FQ-44A |
| Physical Platform | | Physical Platform |
+-----------------------------+ +-----------------------------+
While General Atomics and Anduril secured the production contracts for the physical airframes, the software environment remains a continuous multi-vendor competition. Six companies hold baseline contract vehicles for mission autonomy: Anduril, General Atomics, Lockheed Martin, Northrop Grumman, RTX Collins Aerospace, and Shield AI.
The Air Force has funded the first of two six-month competitive phases to accelerate operational software deployment. To incentivize performance, the service is utilizing a first-of-its-kind award fee exposure strategy. Under this mechanism, the full software licensing fee is tied directly to combat performance in simulation and user feedback from operational pilots. The government retains the right to swap software licenses across the six-vendor pool at any time during the six-year contract vehicle.
Operational Limitations and Risk Profiles
Despite the accelerated timeline—moving from prototype contracts in April 2024 to production contracts in June 2026, four months ahead of schedule—the CCA ecosystem faces significant technical and structural limits.
The primary technical bottleneck is the maturity of the edge-compute processing units required to run advanced machine-learning algorithms in contested environments. When a CCA encounters electronic warfare or heavy jamming, communications with its crewed flight lead will be disrupted. The platform must transition from a semi-autonomous wingman to an entirely autonomous actor capable of executing complex mission logic—such as air-to-air targeting or electronic attack—without human intervention. If the local processing architecture cannot handle the algorithmic load under high thermal stress, the tactical utility of the platform drops significantly.
The second limitation involves flight-safety software validation. While Anduril successfully demonstrated mid-flight swapping of two distinct mission autonomy software suites on the FQ-44A, a software failure during autonomous taxi, takeoff, or close-formation flight presents catastrophic risk to crewed aircraft. This risk was underscored earlier in the development cycle when General Atomics paused testing of its prototype following a crash caused by an autopilot software configuration error. Flight testing has resumed, but the incident highlights the volatility of compressing software validation cycles.
Finally, industrial scale remains unproven. Designing a low-cost uncrewed fighter is distinct from manufacturing hundreds of them annually. The traditional defense industrial base is optimized for low-volume, high-margin production. Scaling to meet the demand of 150 aircraft by the end of the decade, and eventually 1,000, requires a rapid overhaul of manufacturing processes, raw material sourcing, and specialized component assembly.
Strategic Allocation Recommendations
To maximize the defensive capability of this new procurement model, defense acquisition executives must enforce three specific operational mandates.
First, the Air Force must resist the institutional temptation to add mission requirements to Increment 1 air vehicles. The primary risk to a low-cost program is "requirement creep," where additional sensors, redundant defensive systems, and specialized coatings are added over time. This drives the unit cost past the attritability threshold. Increment 1 must remain a simple, mass-producible missile carrier and sensor node. Complex multi-mission capabilities must be deferred to Increment 2.
Second, software licensing must favor vendors that demonstrate the highest rate of algorithmic adaptation during electronic warfare simulations. Because hardware configurations are fixed once serial production begins, tactical advantages will be gained exclusively through software optimization. The award fee exposure model must be ruthlessly applied to penalize vendors whose software fails to adapt dynamically to simulated adversary jamming profiles.
Third, manufacturing capital must be allocated to establish non-traditional assembly facilities. If the FQ-44A and FQ-42A are built using the identical tooling and labor pipelines as crewed stealth fighters, the production rate will plateau, and cost targets will be breached. Manufacturing processes must exploit automotive-style automation, commercial-grade subcomponents where permissible, and modular structures that can be assembled across distributed regional footprints. Mass is only achievable if the underlying assembly line is as scalable as the software it hosts.
