IN Brief:
- GA-ASI, the F-35 enterprise, US Air Force test units, Lockheed Martin, and Autonodyne demonstrated F-35-to-MQ-20 teaming.
- The MQ-20 used TacACE autonomy software, BLOS communications, and a tactical proliferated LEO data link.
- The test highlights how future CCA production depends on autonomy, interfaces, communications, software standards, and repeatable integration.
An F-35 has directed an MQ-20 Avenger during a manned-unmanned teaming demonstration, moving the US Collaborative Combat Aircraft model further into practical integration.
The test brought together General Atomics Aeronautical Systems, the F-35 Joint Program Office, 309th Software Engineering Group, 461st Flight Test Squadron, 370th Flight Test Squadron, Lockheed Martin, and Autonodyne. The MQ-20 Avenger acted as a Collaborative Combat Aircraft surrogate, fitted with GA-ASI’s TacACE Tactical Autonomy Ecosystem software and linked to the F-35 through beyond-line-of-sight communications.
A tactical proliferated low Earth orbit data link connected an airborne MQ-20 with an F-35 on the ground. A pilot in the F-35 cockpit sent tactical autonomy commands through a tablet-based pilot vehicle interface, directing the MQ-20 to execute tactical manoeuvres, adjust waypoints, and send track data back to the fighter.
Crewed-uncrewed air combat is now moving beyond broad concept language and into the more difficult work of integration. The aircraft is only one element. The operating model requires autonomy software, resilient communications, pilot interfaces, mission planning, data standards, test aircraft, safety cases, cybersecurity, and a support structure capable of handling rapid software evolution without undermining airworthiness.
The MQ-20 has served as a surrogate CCA for more than five years, giving the US Air Force and GA-ASI a testbed for autonomy behaviours, interfaces, tactics, communications, and mission concepts. That surrogate role gives engineers a way to mature the digital and operational architecture before purpose-built aircraft such as GA-ASI’s YFQ-42A enter the production and fielding pipeline.
TacACE also shows the growing importance of reference autonomy architectures. CCA programmes cannot afford a future in which every aircraft, sensor, command interface, and autonomy module is locked into a bespoke proprietary stack. Integration speed depends on common interfaces, modular software, and the ability to update behaviours without rebuilding the whole system.
Pilot workload will shape whether CCA concepts scale. A crewed fighter cannot become a full-time remote-control station in the middle of combat. Any interface must allow the pilot to direct intent, change priorities, receive useful data, and maintain tactical awareness without being overloaded. Tablet-based interaction helps define how much control is necessary, how commands should be presented, and how autonomous aircraft should report back to support decision-making.
Communications remain one of the hardest constraints. Beyond-line-of-sight links and pLEO networks can extend coordination, but contested airspace will place pressure on bandwidth, latency, jamming resistance, interception risk, emissions control, and cyber resilience. CCAs are often described as aircraft, although their combat value depends heavily on the network around them. An uncrewed aircraft that cannot receive instructions, share data, or operate safely when links degrade will have limited usefulness.
Manufacturing implications extend across the aerospace supply chain. Future CCAs are expected to be produced at lower cost and higher volume than crewed fighters, but they will still need sophisticated avionics, sensors, propulsion, autonomy processors, datalinks, low-observable features in some cases, and maintainable structures. Affordability will rely on design discipline, modularity, manufacturing automation, and controlled requirements. If every CCA becomes a smaller version of a high-end crewed fighter, the force-mass argument weakens.
The F-35’s role gives the test additional significance. The aircraft is already a sensor-rich platform used across allied air forces, and its ability to coordinate uncrewed teammates could extend reach without placing another pilot in a cockpit. That does not reduce the need for combat aircraft production. It changes the mix, with fighter manufacturing, autonomy development, mission software, data-link equipment, and uncrewed aircraft production beginning to converge.
The same industrial logic appears in allied unmanned-systems standardisation, including the US–South Korea framework for interoperable unmanned systems. At different levels of sophistication, the common themes are interoperability, supportability, standards, software assurance, and supply-chain access.
Aerospace manufacturers are therefore being pulled towards software cadence. Airframes still take years to design, qualify, and manufacture. Autonomy behaviours, interfaces, and data links change faster. Companies that can align certified aircraft hardware with adaptable software will have a stronger position as CCA procurement moves from experiment to fleet planning.
The F-35/MQ-20 demonstration does not make autonomous air combat routine, but it does show the work becoming more practical and more closely tied to production decisions. Future CCA fleets will be judged by whether industry can manufacture affordable aircraft, update them safely, connect them securely, and give pilots enough control to trust them in combat.
