What project 675056 buys
The B-52 Radar Modernization Program (RMP) supports nuclear and conventional operations by replacing the current AN/APQ-166 radar on the B-52 aircraft with the AN/APQ-188 radar. The APQ-166 system is increasingly difficult to sustain due to Diminishing Manufacturing Sources & obsolescent technologies, and the current failure rate places long-duration missions at risk. This modernization program will encompass the radar antenna array, 12 individual Line Replaceable Units (LRU), the radar control panel, and the Group A allocation that comprise the entire radar system. RMP will take advantage of advances in technology and on-going development efforts to acquire, to the maximum extent possible, previously developed radar systems and integrate them into the B-52. The use of new technology will increase both the overall reliability of the radar system and the capabilities for new missions. RMP will allow the operational command (AF Global Strike Command) to fully utilize the capabilities of the B-52 aircraft to employ an array of nuclear and conventional weapons and perform mission-essential navigation and weather avoidance functions. AF Global Strike Command approved the removal of the radome from the baseline program for considerations of cost control and satisfactory legacy radome performance. In addition, applicable training devices for the new radar subsystem must also be developed, modified, and/or upgraded in conjunction with the aircraft modifications. This modification includes the installation of Engineering and Manufacturing Development (EMD) kits on two B-52 test aircraft to support Developmental/Operational Test and Evaluation (DT/OT). This program upgrades one B-52 Software Integration Lab (SIL) with radar functionality and builds a new Radar Development Lab and a new Radar SIL. Additionally, this program will develop a desktop training tool.
- Product Development
- Support
- Test and Evaluation
- Management Services
Project 675056 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 | 200.0 |
| FY2026 | Enacted | 153.1 |
| FY2027 | Request | 106.9 |
| FY2028 | Outyear | 52.2 |
| FY2029 | Outyear | 13.1 |
| FY2030 | Outyear | 4.1 |
| FY2031 | Outyear | 0.2 |
1 accomplishment / planned program
The R-2A exhibit — the only level of the budget that describes work that has not happened yet. Activities carry the prior, current and budget year only, no five-year plan. Each describes FY2027 work in enough detail to have its own page; the rest are shown here in full. Coverage is partial across the corpus, so count activities, never total them.
Will continue Agile and incremental software code development for version 1.0; continue development flight testing; create, test, and deploy software fix releases to integration labs and development flight test aircraft; prepare for Initial Operational Test and Evaluation (IOT&E).
Read the FY2027 plan →Named performers on project 675056
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.