What the FY2027 request buys
Verbatim from the R-2A exhibit for project 676039 of PE 0101113F. 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.
Airspace Compliance plans to continue B-52/R-EGI software development, with delivery of B-52/R-EGI software load (May 2027); program to award B-52 M-Code EMD contract and initiate EMD activities (May 2027)
The FY2026 increase is due to the program's transition from the TMRR Phase to the EMD.
FY2026: the year under way
Prior-year accomplishments and current-year plans from the same exhibit. Context for the FY2027 plan, not a series — an activity partitions its project exactly in the request year, but can under-cover it in earlier years.
Airspace Compliance issued sole-source RFP to Boeing for the B-52 M-Code EMD program (Jan 2026); Airspace Compliance to fund B-52-specific R-EGI software development (May 2026) required for successful integration; program to complete Milestone B requirements to award EMD contract (Nov 2026)
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 | 1.7 |
| FY2026 | Enacted | 12.8 |
| FY2027 | Request | 17.9 |
This activity is 100% of project 676039's FY2027 request and 1.2% of PE 0101113F'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 676039
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.