Roll-up of 2 projects. Projects are the summable leaves — the PE total is their sum, never added to it.
For fiscal year 2027, the U.S. Navy is requesting $513.3M for MQ-25 Stingray under RDT&E program element 0207255N, against nothing enacted in FY2026.
Funding profile, FY2025–FY2031
Prior years are actuals, the budget year is the request, and the outyears are the FYDP plan. Estimate types are colored and never summed into one figure.
| Fiscal Year | Estimate Type | Amount ($M) |
|---|---|---|
| FY2025 | Actual | 0.0 |
| FY2026 | Enacted | 0.0 |
| FY2027 | Request | 513.3 |
| FY2028 | Outyear | 1,212.0 |
| FY2029 | Outyear | 1,011.8 |
| FY2030 | Outyear | 767.6 |
| FY2031 | Outyear | 979.5 |
Acquisition lifecycle
This program is funded in RDT&E Budget Activity 7 — Operational System Development.
2 projects roll up into PE 0207255N
Projects are the summable leaves — the PE total is their sum, never added to it. Program elements and projects carry the full five-year plan; activities stop at the budget year.
Unmanned Carrier Aviation Mission Control System
Congressional marks
Committee marks on the FY2027 request. Adds and cuts are reconciled in conference before they become law.
Where the FY2027 request goes
Performers named in the R-3 exhibit, resolved into industry, government-lab, and unspecified shares. Budget-justification contract funding, not obligations.
| Where FY2027 funding flows | Share | $M |
|---|---|---|
| Industry primes | 87% | 447.9 |
| Government labs & warfare centers | 0.1% | 0.6 |
| Other / unspecified | 13% | 64.8 |
| FY2027 request | 100% | 513.3 |
Mission & acquisition strategy
The Unmanned Carrier Aviation (UCA) Mission Control System (UMCS) program develops, modifies, builds, integrates, and installs control systems, afloat and ashore, required to operate the MQ-25A, Collaborative Combat Aircraft (CCA) and future unmanned systems. UMCS will have to modify existing systems or develop new capabilities to support the control of different unmanned systems. With limited space on the aircraft carriers, the control station software will be modified to enable control of multiple aircraft from a single cockpit.
Based on the Government's acquisition strategy approved in April 2017, the MQ-25 program is an evolution from the previous Unmanned Carrier-Launched Airborne Surveillance and Strike (UCLASS) program and is an Acquisition Category (ACAT) IB program managed by Program Executive Office, Unmanned Aviation & Strike Weapons (PEO(U&W)), PMA-268 Unmanned Carrier Aviation (UCA) Program Office. Pursuant to 10 U.S.C. 2430(d)(1), the Milestone Decision Authority (MDA) is ASN(RDA). MQ-25 requirements are aligned with the UCLASS Initial Capabilities Document (ICD) and the Next Generation Air Dominance (NGAD) Family of Systems (FoS) Initial Capabilities Document, which highlight the need for carrier-based refueling and persistent ISR capabilities.
- Product Development
- Support
- Test and Evaluation
- Management Services
Ask this program element
Answers are generated from the figures on this page — the FY2027 justification exhibits and the marks tracked above — and nothing else is consulted. Confirm any figure against the cited exhibit before you use it externally.
This page carries the budget justification and the NDAA marks — nothing else. For what Boeing has actually been obligated, the ledger is at hitchintel.com/vendors; for live solicitations, hitchintel.com/opportunities. Both are member surfaces.
Cite this page
/programs/0207255N.md · MCP mcp.hitchintel.com → budget_get_program_element, budget_get_cong_marksMQ-25 Air System (AS) — one RDT&E project inside PE 0207255N. Congressional marks are recorded on the program element, not on a project.
Project 3278 — MQ-25 Air System (AS) — requests $440.3M in FY2027, 86% of the $513.3M requested for program element 0207255N. It is a new start — no prior-year or current-year money.
Project 3278 funding, FY2025–FY2031
Prior years are actuals, the budget year is the request, and the outyears are the FYDP plan. Estimate types are colored and never summed into one figure. Projects carry the full five-year plan; the activities inside them stop at the budget year.
| Fiscal Year | Estimate Type | Amount ($M) |
|---|---|---|
| FY2025 | Actual | 0.0 |
| FY2026 | Enacted | 0.0 |
| FY2027 | Request | 440.3 |
| FY2028 | Outyear | 1,121.8 |
| FY2029 | Outyear | 929.9 |
| FY2030 | Outyear | 689.7 |
| FY2031 | Outyear | 900.9 |
6 accomplishments / planned programs
The R-2A exhibit. Activities carry the prior, current and budget year only — no five-year plan — and they are descriptive: coverage is partial and they do not always add back to the project, so count them, never total them. Opening lines only here — the full year-by-year narrative is on the project page.
Continue developmental test and evaluation of EDM3 towards completion of first carrier suitability events. Continue development, design, software integration, and delivery of EDM1, EDM2, EDM4 and SDTA1 to the test program. Continue development of MD-5 integration software. Continue development and redesign of obsolete critical flight…
Read the FY2027 plan →Continue Air System and UMCS GCS development, design, and integration activities in support of flight test and carrier suitability certifications. Continue Cyber Security efforts to maintain Authority to Operate (ATO) certifications for the System Test and Integration Lab (STIL), Lab Revitalization Program and test facilities. Continue…
Read the FY2027 plan →Begin hardware and software development and integration efforts to incorporate Stingray to the Fight capabilities.
Continue oversight, coordination, and management of MQ-25 acquisition, system interface, and integration activities. Oversee contract activities, to include execution of the EMD contract, travel, and training. Conduct engineering and logistics management tasks. Maintain security and program office environments.
Continue to support development, implementation, and sustainment of test facilities, range, and lab test requirements. Support test execution to the Test and Evaluation Master Plan, support engineering events, and program management activities. Support activities in Modeling and Simulation development to include validation and…
Read the FY2027 plan →Continue to evaluate and track maintainability and obsolescence issues including their impact on supportability. Continue engine container testing and any additional follow-on training and courseware development. Complete the development of the MQ-25 Structure Repair Manual that provides guidelines, design and procedures for identifying…
Named performers on project 3278
Performers named in the R-3 exhibit under this project. Share is of the project's whole FY2027 R-3 total — the same denominator the program-element split uses, so the two read on one scale and will not sum to 100% when unnamed or government work is in the mix. Budget-justification contract funding, not obligations.
What project 3278 buys
The scope of the program includes, but is not limited to, system level requirements identification, allocation of requirements to segments and components, design, development, integration, fabrication, test, training, and support activities to provide the MQ-25 capabilities. To provide these capabilities, MQ-25 will transition technologies from other programs and adapt them into the carrier environment. MQ-25 will deliver the necessary air vehicles, command, control, connectivity, shipboard and land-based launch and recovery control systems, associated support systems, interfaces, and upgrades to other Navy systems (as required) to meet the required capabilities.
- Product Development
- Support
- Test and Evaluation
- Management Services
Unmanned Carrier Aviation Mission Control System — one RDT&E project inside PE 0207255N. Congressional marks are recorded on the program element, not on a project.
Project 3279 — Unmanned Carrier Aviation Mission Control System — requests $73.0M in FY2027, 14% of the $513.3M requested for program element 0207255N. It is a new start — no prior-year or current-year money.
Project 3279 funding, FY2025–FY2031
Prior years are actuals, the budget year is the request, and the outyears are the FYDP plan. Estimate types are colored and never summed into one figure. Projects carry the full five-year plan; the activities inside them stop at the budget year.
| Fiscal Year | Estimate Type | Amount ($M) |
|---|---|---|
| FY2025 | Actual | 0.0 |
| FY2026 | Enacted | 0.0 |
| FY2027 | Request | 73.0 |
| FY2028 | Outyear | 90.1 |
| FY2029 | Outyear | 81.9 |
| FY2030 | Outyear | 77.8 |
| FY2031 | Outyear | 78.7 |
1 accomplishment / planned program
The R-2A exhibit. Activities carry the prior, current and budget year only — no five-year plan — and they are descriptive: coverage is partial and they do not always add back to the project, so count them, never total them. Opening lines only here — the full year-by-year narrative is on the project page.
Includes Government and Lockheed Martin software development to enable MQ-25A to the fleet. These funds support: -Software Development: Continued software development essential for supporting all flight tests leading to first deployment -Software Licensing: Procure and maintain EMD software licenses -System Administrator: Continued…
Read the FY2027 plan →Named performers on project 3279
Performers named in the R-3 exhibit under this project. Share is of the project's whole FY2027 R-3 total — the same denominator the program-element split uses, so the two read on one scale and will not sum to 100% when unnamed or government work is in the mix. Budget-justification contract funding, not obligations.
What project 3279 buys
The Unmanned Carrier Aviation (UCA) Mission Control System (UMCS) program develops, modifies, builds, integrates, and installs control systems, afloat and ashore, required to operate the MQ-25A, Collaborative Combat Aircraft (CCA) and future unmanned systems. UMCS will have to modify existing systems or develop new capabilities to support the control of different unmanned systems. With limited space on the aircraft carriers, the control station software will be modified to enable control of multiple aircraft from a single cockpit. The Unmanned Carrier Aviation Mission Control System program includes what was previously identified as the Control System & Connectivity (CS&C) and Carrier Vessel, Nuclear (CVN) Integration (CVNI) Segments previously captured under the MQ-25 Development PU 3278. The UMCS program, PU 3279, is the system-of-systems required for MQ-25 vehicle and payload control both shipboard and shore based. UMCS consists of all ground and ship-based hardware, software, and networks associated with the planning and execution of flight operations and tactical missions. In addition to the Ground Control Station (GCS), consisting of Air Vehicle Pilot (AVP) workstations and servers, the UMCS program builds hardware to support line of sight (LOS) communications, beyond line of sight (BLOS) satellite communications (SATCOM), and integration with ship/shore-based systems. There are three variants of the GCS: MD-5C (CVN-based), MD-5D (Shore-based) and MD-5E (Embarkable system) for use on CVNs that do not yet have permanent GCS systems installed. UMCS leverages existing Programs of Record for network integration and LOS/BLOS communications and builds MQ-25 unique systems (e.g. an ARC-210 based LOS communication system and a Video Management System (VidMS) for AVO situational awareness). The GCS, with a dedicated manufacturer for the core component, allows for streamlined software development, supports multiple classification levels, and positions MQ-25A interoperability with other DoW systems. Hardware development and fabrication is one facet of the program. UMCS develops and integrates software and modifies several aircraft carrier spaces to install and integrate the GCS and communication systems, in support of MQ-25A test events and operations aboard select NIMITZ Class CVNs.
- Product Development