IN Brief:
- Boeing and Rheinmetall are positioning MQ-28 as a mature platform for Germany’s planned collaborative combat aircraft capability.
- Rheinmetall is establishing German systems-integration capability covering mission software, sensors, weapons, and national intellectual property.
- Rohde & Schwarz, Diehl Defence, and HENSOLDT are joining the industrial ecosystem around the proposed aircraft.
Boeing and Rheinmetall are deepening their proposal to use the MQ-28 Ghost Bat as the basis for Germany’s planned collaborative combat aircraft capability, placing increasing emphasis on sovereign systems integration rather than simply offering an Australian-developed uncrewed aircraft. The latest industrial model would give German companies responsibility for sensors, weapons, mission software, and intellectual property around a platform that has already accumulated a substantial flight-test record.
The proposal does not represent a German selection of MQ-28. Instead, Rheinmetall and Boeing are arguing that a mature flying platform could allow the Bundeswehr and national industry to begin developing operational capability without first spending years producing another clean-sheet air vehicle. Germany could concentrate earlier on the mission equipment, software, integration authority, tactics, and training that ultimately determine how a collaborative aircraft operates alongside crewed fighters.
Rheinmetall is now establishing what it describes as independent systems-integration capability for MQ-28 in Germany. Under the proposed model, software development, mission integration, and associated intellectual property would remain within the German industrial ecosystem, while national sensors and weapons could be developed, tested, and incorporated onto the aircraft.
Boeing and Rheinmetall are building that ecosystem alongside Rohde & Schwarz, Diehl Defence, and HENSOLDT. Their involvement highlights the range of disciplines required around the air vehicle itself. Secure communications, electronic systems, radar and other sensors, weapons, mission computing, autonomy, and software interfaces all have to work inside one architecture if an uncrewed aircraft is to provide useful additional combat mass rather than operate as an isolated platform.
MQ-28 was developed in Australia in partnership with the Royal Australian Air Force and has completed more than 150 test flights. It has also participated in multinational exercise activity, giving Boeing and Rheinmetall a comparatively mature hardware base from which to make their German case. The aircraft was designed around a modular architecture that allows mission equipment to change without redesigning the complete vehicle.
That maturity is central to the proposition because Germany has indicated that it wants to begin fielding collaborative combat aircraft capability from 2029. A timetable of that kind leaves limited space for designing an entirely new airframe, developing flight controls, integrating propulsion, qualifying the vehicle, establishing autonomy, introducing weapons, and then conducting enough operational testing to understand how the system should be used.
Starting with existing flight hardware does not remove the engineering burden. German sensors still need appropriate power, cooling, data interfaces, physical accommodation, and fields of view. Weapons require mechanical and software integration alongside carriage, separation, and safety work, while national mission software has to communicate with the aircraft’s flight and autonomy systems without compromising the integrity of either.
Electronic warfare and communications equipment add further constraints because antenna placement and electromagnetic compatibility can affect the wider vehicle. Every additional payload changes weight, balance, electrical demand, thermal load, and potentially the aircraft’s signature. The industrial advantage therefore lies in avoiding recreation of the underlying aircraft, not in making integration itself trivial.
Rheinmetall’s emphasis on intellectual property is equally important. Collaborative combat aircraft will depend heavily on software changes throughout their operating lives as sensors, weapons, autonomy, and electronic warfare evolve. A customer unable to alter those interfaces without returning to a foreign original equipment manufacturer can find that apparently sovereign hardware remains dependent on external engineering authority.
The German proposal is intended to prevent that dependency from extending across the entire mission architecture. Rheinmetall would act as national systems integrator, while Boeing continued development of the aircraft itself using flight-test data, experience from Australia, and a digital twin. National capabilities could then be tested on the current platform and, according to Rheinmetall, provide experience applicable to future CCA programmes as well.
That creates a useful distinction between platform sovereignty and capability sovereignty. Germany would not own the underlying MQ-28 design, but it could retain greater control over the sensors, weapons, software, and integration work that determine how the aircraft performs in Luftwaffe service. Whether that balance is sufficient will ultimately depend on the procurement requirements and the degree of access agreed between the companies and government.
The model reflects a wider European defence-industrial problem. Governments increasingly want fielded or near-fielded allied technology quickly, but they also want domestic engineering authority, secure supply, and the ability to modify systems without lengthy overseas approval. Those objectives are easier to reconcile when platform architecture is deliberately open enough for national industry to control substantial portions of the mission system.
MQ-28 remains a proposal rather than Germany’s selected collaborative combat aircraft. Rheinmetall and Boeing still have to convert their industrial architecture into a procurement decision and demonstrate that the promised national integration model can operate within the technical boundaries of Boeing’s air vehicle.
The latest step nevertheless makes the offer more specific. Boeing is contributing a flying platform, test experience, and an established autonomy programme; Rheinmetall and its German partners are attempting to build the sovereign mission architecture around it. Germany’s eventual decision will show whether that division of responsibility provides enough independence to justify adopting an aircraft designed elsewhere.
