IN Brief:
- Boeing has received a $12.68 million MQ-25 modification covering updated RF blanking, encrypted storage, and embedded data-transfer equipment.
- The award also covers deficiency analysis and corrections associated with security assessments of the Mission Management System Computer.
- MQ-25 received Milestone C approval in May 2026, so electronics integration is continuing as the programme moves towards low-rate production.
Boeing has received a $12.68 million US Navy contract modification covering electronics integration and security-related engineering on the MQ-25 Stingray programme. The work includes an updated Radio Frequency Blanker Unit, encrypted mass-storage equipment with an embedded Data Transfer System, and deficiency analysis and corrections supporting security assessments of the Mission Management System Computer.
The modification adds non-recurring engineering and integration scope to Boeing’s existing MQ-25 contract. Around 85% of the work will take place in St Louis, Missouri, with the remaining 15% in Fairborn, Ohio, and completion is expected by November 2029. Fiscal 2026 Navy research, development, test, and evaluation funding covers the full value of the action.
The award arrives while MQ-25 is crossing from engineering development towards production. The US Navy approved Milestone C for the Stingray on 19 May 2026 following the aircraft’s first flight in April, clearing the programme to proceed towards low-rate initial production. Boeing subsequently completed a second test flight in July using updated software intended to support further flight-envelope expansion.
That acquisition milestone does not mean engineering work has stopped. Production approval establishes sufficient maturity to begin moving towards deliverable aircraft, while flight testing, carrier integration, cybersecurity assessment, software development, and correction of deficiencies continue alongside the manufacturing programme.
The RF blanker is one example of equipment whose importance lies in electromagnetic compatibility rather than the aircraft’s visible mission. A platform carrying transmitters, receivers, navigation systems, data links, and sensors has to manage the interactions between those systems so that one transmission does not interfere unacceptably with another piece of equipment.
Encrypted mass storage and embedded data transfer address another part of the architecture. An uncrewed aircraft generates and consumes mission, maintenance, configuration, and system information without an onboard pilot handling data in the same way as a conventional cockpit. Secure storage and controlled movement of that information therefore form part of both operational functionality and information assurance.
The Navy’s inclusion of deficiency analysis and corrections for the Mission Management System Computer illustrates how closely cybersecurity and conventional avionics engineering now overlap. Finding a vulnerability or undesirable behaviour is only the beginning. Engineers have to introduce a correction, demonstrate that it resolves the issue, and establish that the modification has not created unacceptable effects elsewhere in the software or aircraft architecture.
MQ-25 is unusually dependent on that integration because it is intended to become the Navy’s first operational carrier-based uncrewed aircraft, with aerial refuelling as its primary mission. The aircraft is commanded through the Unmanned Carrier Aviation Mission Control System rather than an onboard cockpit, creating a distributed architecture connecting the air vehicle, mission computers, communications, shipboard or ground control, and carrier infrastructure.
During the aircraft’s first flight in April, Navy and Boeing air-vehicle pilots sent commands from the MD-5 ground-control station while the aircraft executed its flight functions. Boeing’s July second-flight report said a new software load introduced vehicle-management and mission-computer improvements before further envelope-expansion testing.
Changes to the Mission Management System Computer therefore have consequences beyond an isolated processor. Software and electronic interfaces need to remain compatible with flight controls, communications, mission planning, data transfer, ground control, maintenance, and the wider carrier-based system into which MQ-25 is being integrated.
Production increases the incentive to settle such changes early. A modification introduced while only development and early production aircraft exist can be incorporated through controlled manufacturing changes. The same issue discovered after a larger fleet has been delivered can require access, rewiring, software rework, retrofit kits, repeated testing, and disruption to operational aircraft.
The $12.68 million action is small beside the overall MQ-25 programme, but that does not make its scope trivial. Encrypted storage, electromagnetic compatibility, data transfer, and mission-computer security rarely produce the imagery associated with a first flight, yet unresolved problems in any of them can delay an aircraft whose usefulness depends on secure and predictable autonomous operation.
Work under the modification runs to November 2029, overlapping the period in which MQ-25 is expected to move further into production and carrier integration. The engineering objective is therefore straightforward: resolve electronics and security issues early enough that the Navy does not inherit avoidable retrofit work as the Stingray moves from a development fleet towards an operational system.
