IN Brief:
- Raytheon has received a $34.36 million V-22 Tactical Software Suite sustainment order.
- The Indianapolis-based work supports Air Force, Marine Corps, and Navy V-22 fleets through August 2028.
- The wider software sustainment process covers updates, problem resolution, qualification, aircraft integration, airworthiness work, and fleet release validation.
Raytheon has received a $34.36 million US Navy order to sustain the V-22 Tactical Software Suite, extending engineering support behind the software used across Air Force, Marine Corps, and Navy Osprey fleets.
Raytheon will perform the work in Indianapolis, Indiana, under a cost plus fixed fee order awarded by Naval Air Systems Command. The programme is expected to continue until August 2028 and draws funding from aircraft procurement, operations and maintenance, research and development, and wider defence procurement accounts.
The order is valued at $34,364,909 and provides engineering, management, technical, and acquisition support for the V-22 Tactical Software Suite. NAVAIR identifies the purpose as sustaining operational readiness across the three US services that operate the aircraft rather than introducing a separately identified new capability.
That distinction matters because software sustainment is easy to confuse with a discrete upgrade programme. The current contract notice does not identify individual software releases, aircraft quantities, specific modifications, or a new operational function. Its purpose is to maintain the engineering structure through which the existing tactical software baseline can continue to be supported.
An earlier NAVAIR requirement for the same FY2026 software sustainment activity shows what that process can involve. The work was described as including software product updates, resolution of V-22 Problem Reports, qualification testing, integration into the aircraft, airworthiness substantiation, flight test demonstration, and validation and verification of fleet software releases across MV-22, CMV-22, and CV-22 variants.
Those earlier requirements provide useful technical context for the sustainment process, although the current award notice does not specify which individual tasks will be carried out under each release. What is clear is that V-22 software support extends well beyond conventional information technology maintenance.
A software correction installed on an aircraft has to coexist with avionics, mission systems, displays, sensors, data buses, and other software already present on the approved configuration. A change that resolves one problem can introduce an unintended effect elsewhere unless it is tested against the representative aircraft baseline.
Qualification and airworthiness work therefore sit alongside coding and defect resolution. Ground laboratories can identify many faults, but software intended for operational aircraft may also require hardware integration, representative system testing, and flight activity before it can be released to the fleet.
The multi-service nature of the V-22 programme adds another layer. The Marine Corps operates the MV-22, the Navy uses the CMV-22 for carrier logistics, and the Air Force operates the CV-22 for special operations. They share the fundamental tiltrotor architecture but carry different mission equipment and operate under different service requirements.
A common software activity consequently has to account for configuration differences rather than assuming every Osprey is technically identical. The more variants diverge through mission equipment, hardware changes, and service-specific modifications, the more important disciplined configuration control becomes when software is tested and released.
The funding mix behind the latest order reflects the boundary between sustaining the current fleet and continuing engineering activity. Navy and Air Force aircraft procurement accounts sit alongside operations and maintenance funding, Navy research and development money, and Defense-Wide procurement funding. The published allocations account for essentially the full order value.
The award also arrives as the wider V-22 enterprise shifts towards long-term sustainment. Production activity is winding down, but the aircraft are expected to remain in service for years, leaving software support, component obsolescence, structural work, avionics modification, and fleet engineering increasingly important to availability.
Software does not become static when an aircraft leaves production. Operational use continues to generate fault reports, compatibility issues, cyber requirements, and new integration demands, while ageing hardware can require software changes to accommodate replacement components or altered interfaces.
That means the digital baseline has to be maintained with the same discipline applied to physical aircraft configuration. A fleet in which individual aircraft carry inconsistent hardware and software states creates additional maintenance and troubleshooting work, while making it more difficult to establish whether a reported problem has already been corrected elsewhere.
The latest Raytheon order keeps that sustainment process funded through August 2028. It does not announce a new V-22 mission or major hardware modernisation programme, but it maintains the engineering route through which software problems can be investigated, corrected, tested, and incorporated into approved fleet configurations.
As production declines, those recurring engineering processes become increasingly important. Keeping a mature aircraft operational is less about repeating the original manufacturing programme and more about controlling thousands of incremental technical decisions across hardware, software, maintenance, and support. The Tactical Software Suite order funds one of the systems needed to keep that process functioning across three different V-22 fleets.