IN Brief:
- Boeing’s MQ-28 Ghost Bat is joining Exercise Valiant Shield 2026 in the Pacific.
- The uncrewed aircraft will operate with crewed combat aircraft in a complex allied exercise environment.
- Collaborative combat aircraft programmes are now being judged on integration, supportability, software assurance, and scalable production.
Boeing’s MQ-28 Ghost Bat is moving into a more demanding operating environment as the uncrewed aircraft joins Exercise Valiant Shield 2026, extending collaborative combat aircraft testing from development activity into a multinational Pacific exercise.
The aircraft is operating from Rota in the Northern Mariana Islands, where it is expected to fly in proximity to crewed combat aircraft during a large-force exercise involving air, maritime, land, space, and cyber elements. For a platform designed to support crewed fighters and widen combat mass, the setting brings together many of the pressures that cannot be fully replicated in a controlled test range.
Although flight performance remains central, the larger industrial test now sits around integration. A collaborative combat aircraft must carry useful payloads, communicate securely, respond predictably to command inputs, and fit into a force package without creating excessive workload for pilots, maintainers, or commanders. Autonomy alone is not a capability unless the aircraft can be deployed, updated, repaired, and trusted in operational tempo.
The MQ-28 has been developed as a modular uncrewed aircraft with a range of more than 2,000 nautical miles, a length of 11.7 metres, and an architecture intended to support different payloads and mission roles. Its design is closely tied to Australia’s ambition to remain part of the next combat-air production cycle, rather than simply buying mature systems once the main technology decisions have already been made elsewhere.
As allied air forces push toward crewed-uncrewed teaming, programmes such as Ghost Bat are beginning to expose the manufacturing realities behind the concept. Repeatable airframe production, qualified suppliers, propulsion integration, mission computer availability, payload-bay flexibility, and electromagnetic compatibility all become part of the same problem. The aircraft has to be flexible enough to evolve, but controlled enough to be manufactured and supported at scale.
That balance is difficult. Too much bespoke integration raises cost and slows production; too little flexibility risks leaving the platform behind as sensors, weapons, autonomy software, and communications architectures change. In practice, the companies that succeed in this market will be those able to treat autonomy, airframe design, payload engineering, and sustainment as one production system.
The same industrial pressure is visible across allied combat-air development, from European work on fighter-based drone control to Poland’s interest in autonomous combat air workshare. Air forces want the operational benefit of extra combat mass, but defence ministries increasingly want local support, sovereign software access, exportable production roles, and upgrade paths that do not trap them inside a single vendor’s release schedule.
Valiant Shield also places the aircraft into the geography that drives much of the collaborative combat aircraft debate. Indo-Pacific operations involve distance, dispersed basing, weather, limited infrastructure, and contested communications. An aircraft that looks attractive on paper still needs a deployable maintenance model, spares discipline, secure data handling, and ground support equipment that can operate away from a mature home base.
Software release cycles will be especially important. An uncrewed combat aircraft is not frozen at delivery, and mission-system updates could become as decisive as structural production rates. Secure coding, validation, cyber accreditation, simulation, and flight-test capacity will all affect whether upgrades can move quickly enough to keep pace with threats. Manufacturers that treat software as an aftermarket complication will struggle against programmes built around a digital engineering spine from the start.
Cost discipline remains the hardest unresolved question. Removing the pilot does not automatically create a cheap aircraft. Sensors, propulsion, datalinks, survivability features, mission computers, actuation, certification, and secure autonomy still carry considerable cost. The case for collaborative combat aircraft depends on lowering the cost of useful combat mass without allowing every unit to become a smaller version of a crewed fighter procurement programme.
For Boeing Defence Australia, Ghost Bat’s Pacific exercise work offers more than another demonstration point. It places an Australian-developed aircraft inside the operating environment most likely to shape allied requirements for the next decade. That gives industry a sharper view of what customers will actually demand: production-rate credibility, modular payloads, allied interoperability, field support, and software resilience.
The concept of collaborative combat aircraft is now mature enough to face a tougher question. The challenge is no longer whether uncrewed aircraft can fly alongside crewed platforms. It is whether manufacturers can build enough of them, update them quickly, support them across dispersed locations, and integrate them into a combat force without turning each aircraft into a fragile engineering experiment.
