What the FY2027 request buys
Verbatim from the R-2A exhibit for project 3279 of PE 0207255N. This is the budget justification's own description of work that has not happened yet — the one thing no other level of the budget carries.
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 support for all MDCX test systems -On-Site Engineer: Dedicated Flight Test Engineer support for all test events -Correction of Deficiency (CoD): Builds essential for supporting all flight tests and system design leading to the first deployment -Technical Data Package (TDP): Continue development of logistics product updates for multiple shore (MD-5D) and mobile (MD-5E) systems -Conduct CVN risk reduction flight on CVN J -Development of Health and Monitoring (HeMo) software to include network configuration -Support the integration of JPALS with the MQ-25A Aircraft -Analyze requirements and continue MD-5 ancillary system design upgrades to support multi-level security -Develop mobile communications and network test kit -Address obsolescence of test assets to include form-fit-function replacements, qualification of new parts and lifetime buys
Increase from FY26 values (under PE 0605414N) to FY27 is due to continued software development required to deliver the MQ-25A capability directly to the fleet. This includes the continued development and integration of essential software, such as Relative Navigation (RELNAV), which enables the MQ-25A to reliably recover on a CVN. Furthermore, the increased funding supports the expansion of Technical Data Package (TDP) development for shipboard systems and begins to address the obsolescence of test assets, ensuring the program remains on track for its Engineering and Manufacturing Development (EMD) phase and successful fleet deployment.
Three years, and no five-year plan
An R-2A activity publishes the prior year, the current year and the budget year. The FYDP outyears exist at project and program-element level and are deliberately absent here rather than inferred. 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 | 73.0 |
This activity is 100% of project 3279's FY2027 request and 14% of PE 0207255N's. In the request year the activities under a project sum to it exactly; in the current year they under-cover it in about 9% of cases, so an activity's delta can legitimately exceed its parent's and the two must not be compared row to row.
1 activity in project 3279
Every R-2A line of this project, largest FY2027 request first. Linked where the activity has enough of its own narrative to carry a page; the rest are shown in full on the project page.