The U.S. Air Force crossed a major programmatic threshold in June 2026, awarding production contracts to both General Atomics for its FQ-42 Collaborative Combat Aircraft and Anduril Industries for its FQ-44 — a dual-award rather than the winner-take-all downselect many observers had expected★. The decision marks the first time the CCA program has cleared development and moved into manufacturing, setting the stage for a complex ramp-up involving two separate airframe production lines, an externally developed autonomy stack, and eventual integration into operational force structure alongside crewed combat aircraft.
The dual-award structure is the lead story, but the program's architecture — particularly its deliberate separation of airframe and autonomy contracting — and the concurrent buildout of the Pentagon's proliferated LEO communications infrastructure make this a development with ramifications across several segments of the defense industry.
The Dual-Award Decision
The Air Force's choice to advance both designs simultaneously, rather than narrowing to a single winner, reflects deliberate risk management on a program the service has acknowledged carries significant technical uncertainty.
General Atomics, a long-established name in unmanned aerial systems, brings the FQ-42. Anduril Industries, a defense technology company that has built a reputation on software-centric autonomous systems, brings the FQ-44. The two designs will proceed on parallel production tracks, creating what is effectively a competitive production base at a stage in the program when the Air Force still retains flexibility to adjust mix ratios based on cost, performance, and operational test results★.
This is not the acquisition structure of a typical major defense program. The Air Force is explicitly not treating CCA as a single-prime program in which one contractor owns the full vertical. Instead, the airframe and the autonomy systems are being developed on separate contracting tracks — a structural choice with direct consequences for how the program will be managed, integrated, and eventually sustained.
Autonomy Stack Architecture
According to RealClearDefense, Anduril, Shield AI, and Collins have been selected to develop the autonomy system — the AI-driven software layer governing how CCAs coordinate with crewed aircraft and execute missions★. This team-of-three arrangement means the Air Force is managing a two-tier supply chain: airframe manufacturers on one track, an autonomy stack development consortium on another.
The separation introduces sequencing dependencies that program managers will need to track carefully. Airframes in production require software that can be qualified for airworthiness, but the autonomy stack — particularly the AI-driven teaming and coordination logic — is itself still maturing. The Air Force will need to align integration milestones to avoid a scenario in which production-ready airframes await software that has not yet been certified for operational use. This is not unusual in complex defense programs, but it is a documented risk in parallel development structures.
The autonomy contractor team draws on a mix of established defense integrators and newer autonomous systems specialists, which the Air Force appears to have selected deliberately rather than concentrating development with a single vendor. That mirrors the dual-track approach at the airframe level: multiple parallel bets, competitive pressure, and optionality preserved as the technology matures. Notably, Anduril appears on both tracks — as an FQ-44 airframe producer and as a member of the autonomy development team — a position that will require careful management of organizational interfaces on the government side.
For defense supply chain professionals, the CCA production ramp will generate demand across composites, propulsion, avionics, electronic warfare payloads, and mission systems. The autonomy stack contracting will draw on AI/ML engineering capacity and software airworthiness expertise — disciplines where military certification frameworks are still being developed and standardized. The program's two-tier industrial structure means that different segments of the supply chain will feel its impact on different timelines and through different contracting channels.
Satcom and Space Connectivity Context
For satcom and space professionals tracking defense sector demand, the CCA program's industrial launch coincides with continued buildout of the Pentagon's tactical satellite communications infrastructure. In July 2026, SpaceX successfully launched the Tranche 1 Transport Layer E mission on a Falcon 9 from Space Launch Complex 4E at Vandenberg Space Force Base — one of six missions the Space Development Agency is executing for the Proliferated Warfighter Space Architecture Tranche 1 Transport Layer, delivered to polar orbit. The mission carries government payload classified at the Top Secret level.
For autonomous platforms like CCAs, which require reliable, high-throughput data links for teaming coordination, sensor relay, and command interfaces with crewed wingmen, resilient tactical connectivity is a foundational operational requirement.
The sources for this briefing do not establish a formal, contract-level programmatic connection between CCA and PWSA — the production contract announcements do not address CCA communications architecture specifically. The strategic dependency is nonetheless real: the distributed autonomous combat air operations the CCA concept envisions will require the kind of low-latency, survivable connectivity PWSA is being built to deliver. The SDA's Tranche 1 launch cadence — with Transport Layer E now on orbit — provides a measurable indicator of how quickly that infrastructure is being fielded. Satcom professionals should monitor both programs on parallel timelines, since their operational convergence is a timing question rather than a conditional one.
What Comes Next
The production awards are a starting line, not a delivery milestone. Early lot production will be used to establish tooling, verify manufacturing processes, and build the first tranche of articles that will enter developmental and operational testing★ — not to deliver operationally configured aircraft ready for squadron service. The Air Force must simultaneously manage airframe production across two manufacturers, autonomy stack development across three software contractors, and eventual integration testing before any operational employment becomes feasible. These parallel workstreams will require integration milestone management that is more complex than a single-prime program structure would demand.
Key indicators for the industry to monitor include: disclosed production contract values and lot sizes as they emerge, which will signal the pace the Air Force intends to hold; integration testing milestones as FQ-42 and FQ-44 airframes begin flying with the autonomy stack installed; and any announcements connecting CCA platforms to specific crewed aircraft programs that will define the operational teaming concept at the tactical level. On the space connectivity side, the remaining SDA Tranche 1 Transport Layer missions will mark continued infrastructure buildout, and any future Air Force or SDA announcements addressing communications architecture for autonomous platforms would be a significant development connecting these two major program lines. The dual-award structure gives the Air Force flexibility well-suited to a high-risk program — and will generate sustained industrial demand across the defense sector through the remainder of the decade.
★ AI inference: One or more analytical conclusions in this article were drawn by the AI from cited facts and are not directly stated in the cited sources.