The U.S. Air Force initiates a critical phase to arm its Collaborative Combat Aircraft (CCA). Behind the announcement lies a central issue: demonstrating integration, software openness, and industrial speed.
Summary
The U.S. Air Force has reached a significant milestone in its Collaborative Combat Aircraft program. This announcement does not mean that these autonomous drones are currently firing missiles in operational settings. However, it confirms that the program has entered a phase where arming is no longer theoretical. The tests focus on integrating external payloads, ensuring safety, compatibility with mission systems, and safe munitions separation. This step is essential before any actual firing can occur. Concurrently, the Air Force is validating its approach to an open architecture via the Autonomy Government Reference Architecture (A-GRA). The clear objective is to decouple the drone, the autonomy software, and the onboard sensors or effects to prevent a manufacturer from locking down the entire ecosystem. For industry players, the stakes are enormous. The winners will not only be aircraft manufacturers but also software providers, integration specialists, sensor makers, data link suppliers, and compatible armament producers.
The True Meaning of This New Testing Phase
It’s important to contextualize the announcement appropriately. In official U.S. communications, the phase underway is focused on weapons integration testing, involving trials of weapon mounting and safety validation using inert munitions. This signifies a considerable shift. We are moving away from conceptual discussions and into the physical verification of what a CCA can carry, support, and eventually drop or fire without compromising its structure, aerodynamic behavior, or flight safety.
Specifically, the U.S. Air Force notes that this phase aims to achieve three objectives. The first is navigability. A collaborative combat drone must demonstrate that it can carry external payloads without degrading its flight envelope to the point of becoming unstable or dangerous. The second objective is system compatibility. It’s not enough to simply attach a missile beneath the wing; it must be proven that the mechanical, electrical, and software interfaces operate correctly with the aircraft and its mission system. The third objective is safe separation, meaning that munitions must detach from the aircraft without striking the airframe or traversing an unstable aerodynamic flow.
This clarification is crucial, as many commentators may rush to conclusions. No, the Air Force has not publicly announced that its CCAs are already firing missiles in full tactical cooperation with a F-35 or a future F-47 in an operational environment. Yes, it has crossed a critical threshold: where armament becomes a tested, measured, and qualified subsystem, no longer just a marketing promise.
The Logic of Testing Phases Before Real Firing
In an air combat program, the integration of armaments follows a very rigorous sequence. The CCAs are no exception. They adhere to this pattern in a very conventional manner, which the Air Force openly acknowledges.
Ground Testing Phase
Before flight, everything begins on the ground. Engineers verify mechanical interfaces, electrical compatibility, data flows between the vehicle, mission computer, and military payload, as well as the responses of control systems. For the CCA program, this phase began in 2025 with the first two demonstrators, the YFQ-42A from General Atomics and the YFQ-44A from Anduril. The tests focused on propulsion, avionics, autonomy integration, and ground control interfaces.
Initial Flight Phase
Once the initial risks are mitigated, the aircraft proceed to fly without active weapons. The objective is to assess the platform’s behavior, the reliability of controls, the performance of autonomy algorithms, and the quality of mission integration. The YFQ-42A flew for the first time in 2025, less than two years after the program’s launch, which is remarkably fast for a combat system of this caliber.
Captive Carry Phase
This is the central phase currently taking place. The drone flies with an inert munition or dummy payload attached. Observations focus on vibrations, drag, structural stresses, stability effects, and performance impacts. This is a challenging but essential step. An aircraft may fly smoothly without load and become significantly less stable once payloads are added.
Safe Separation Phase
Following captive carry, it’s necessary to verify that the munitions can exit the aircraft without striking the structure or traversing through unstable aerodynamic flows. This is where modeling, instrumentation, and dedicated test outputs come into play. For a CCA, this phase is even more critical, as the aircraft must simultaneously manage mission autonomy, communication with the piloted control system, and the final human decision regarding weapon employment.
Live Firing or Advanced Simulated Employment Phase
Only after these validations can a program proceed to real firing tests or more advanced tactical scenarios. To date, the U.S. Air Force explicitly states that a human retains authority over the firing decision. The CCA is therefore not positioned as an autonomous machine allowed to fire on its own. It is a supervised armed system, integrated into a conventional command chain.
Open Architecture at the Core of the Program
This point may seem technical, but it is likely the most crucial aspect of the entire initiative. The Air Force is not merely looking to purchase a drone; it aims to build an open government architecture that allows for rapid changes in software, sensors, payloads, or suppliers without reconstructing the entire system.
The name of this central element is Autonomy Government Reference Architecture (A-GRA). The concept is straightforward on paper and daunting in its industrial implications: the U.S. government owns the architectural reference serving as a common language among platforms and autonomy software. This enables the decoupling of hardware from software.
To put it more plainly, the Air Force seeks to break the old habit of a single prime contractor locking down the platform, code, interfaces, and maintenance. With A-GRA, it aims to prevent an aircraft manufacturer from claiming: my drone only works with my autonomy, my interfaces, my integrators, and my updates. This is a strategic move against vendor lock.
In practice, the Air Force has already demonstrated this approach with several industrial partnerships. RTX Collins has integrated its Sidekick Collaborative Mission Autonomy with General Atomics on the YFQ-42A. Shield AI is working with Anduril on the YFQ-44A. The message conveyed to the market is clear: autonomy should not remain confined within the exclusive ecosystem of the airframe manufacturer.
What an Open Architecture Truly Is
An open architecture does not imply that everything is interchangeable without cost or limitation. The term is sometimes misused. In the case of the CCA, it should be understood as a modular structure with standardized interfaces, governed by the state, to facilitate the addition or replacement of components.
This involves at least five layers.
Vehicle Layer
This includes the airframe, propulsion, control surfaces, onboard energy, flight computer, and physical interfaces.
Autonomy Layer
This is the software brain responsible for navigation, avoidance, formation, task execution, and semi-autonomous behavior.
Mission Layer
This aggregates sensors, effect management, tactical priorities, data fusion, and cooperation with the piloted aircraft.
Communication Layer
This encompasses data links, resistance to jamming, cybersecurity, and the transmission of orders or constraints.
Effect Layer
This includes everything that produces a military effect: missiles, jamming systems, decoys, ISR sensors, communication relays, and even electronic warfare payloads.
The major advantage is the speed of integration. The Air Force can theoretically introduce a new player rapidly on a single component without restarting an entire program. The significant challenge, however, is mastering integration. The more modular the system, the more it requires robust governance, rigorous standards, and intensive testing to avoid incompatibilities.
The Link to the F-35 and Future NGAD
The role of the CCA is not to replace a F-35 or the future F-47 from the NGAD program. Its purpose is to enhance the mass, range, and survivability of the overall system. The Air Force refers to it as a system of systems. The concept is clear: a piloted aircraft retains decision-making, orchestration, and overall tactical understanding, while multiple drones take over functions like advanced sensing, escort, deception, jamming, or striking.
This is where armament alters the nature of the program. An unarmed CCA can already serve as a sensor or decoy. An armed CCA becomes a fire multiplier. It enables the positioning of missiles closer to the threat without immediately exposing the pilot of the crewed fighter. It also allows for saturating enemy defenses, distributing the payloads, and complicating the adversary’s tactical assessment.
The Air Force still aims for a fleet of at least 1,000 CCAs. This is substantial. The logic is not only technological; it is also economic. Public estimates suggest unit costs significantly lower than those of modern crewed fighters, with figures cited ranging from approximately $5 million to $30 million depending on versions and assumptions, while some officials have indicated that the pricing goal remains under control. It is this promise of affordable mass that renders the concept credible at scale.
The Industrial Shock for Suppliers
The most profound effect of the CCA program may not be tactical; it is industrial.
In a closed model, the prime contractor captures the bulk of the value. In an open model, the chain fragments. This opens doors for smaller, more specialized, and faster suppliers. One actor may focus on autonomy, another on data links, another on electronic warfare modules, and another on specific payloads.
For larger groups, the risk is evident: losing part of the historical control over the entire architecture. For mid-sized companies and those emerging from software or AI backgrounds, the opportunity is immense. The Pentagon sends them a rare message: you can enter through one component without necessarily producing the entire aircraft.
However, this openness comes with severe trade-offs. Suppliers will need to demonstrate their ability to integrate quickly, adhere to common standards, deliver robust code, maintain cybersecurity, and accept continuous competition. The open architecture broadens the market but intensifies the selection process. It rewards speed of execution over established position.
The Future Will Reveal Whether the American Bet Holds
The CCA program is beginning to emerge beyond sketches and slogans. The weapons integration tests indicate that the Air Force is now working on the most sensitive aspect: transforming a collaborative drone into a credible force carrier while maintaining control over safety, authorization for use, and tactical integration.
The true test now will not just be to make these devices fly or to attach inert munitions. It will be to demonstrate three things simultaneously: safe separation, robust coordination with the crewed fighter, and an architecture sufficiently open to enable competition without compromising operational coherence. This is where the distinction will be made between impressive innovation on PowerPoint and a military capability that genuinely shifts the balance of power.
Sources
U.S. Air Force, “Collaborative Combat Aircraft program progresses through deliberate weapons integration testing”, February 23, 2026.
U.S. Air Force, “Air Force validates open architecture, expands Collaborative Combat Aircraft ecosystem”, February 12, 2026.
U.S. Air Force, “Experimental Operations Unit accelerates Collaborative Combat Aircraft program”, April 16, 2026.
U.S. Air Force, “DAF begins ground testing for Collaborative Combat Aircraft, selects Beale AFB as the preferred location for aircraft readiness unit”, May 1, 2025.
Defense News, “US Air Force’s CCA program advances with auto-flying software integration”, February 12, 2026.
Defense News, “First flight tests begin for Air Force’s drone wingmen”, August 28, 2025.
Air & Space Forces Magazine, “Air Force wants nearly $1 billion to start buying CCAs in 2027”, April 6, 2026.
Air & Space Forces Magazine, “Air Force revisiting production goals for CCA with eye on Increment 2”, March 17, 2026.
U.S. Air Force, “Air Force Awards Contract for Next Generation Air Dominance Platform, F-47”, March 21, 2025.
Avion-Chasse.fr is an independent information site.
The post United States: CCAs Enter Armament Testing first appeared on AVION DE CHASSE.




