Why It Matters

The Air Force is projected to spend an estimated $21 billion modernizing the B-52. The bomber, introduced in 1955, is expected to remain operational through 2050, but 10 of its 13 modernization programs are experiencing cost, schedule or performance challenges.

The most expensive effort, the Commercial Engine Replacement Program, has increased in cost by about $3 billion since 2023, while its initial operational capability target has slipped by more than 15 months. Despite those setbacks, the Air Force plans to begin production with little to no developmental flight testing.

Department of Defense policy states that cost estimates should account for risk and evaluate alternative courses of action that could reduce costs and other risks. Although the Air Force assessed and accepted the program's production risks in 2023, it has not reevaluated that decision in light of the subsequent cost growth and schedule delays.

The Big Picture

The consequences extend beyond the modernization program itself. The Air Force conducts planned B-52 maintenance at a repair depot roughly every four years. Current plans assume the Commercial Engine Replacement Program and new engine installations will remain on schedule, but they do not account for the possibility of further delays.

The service is already struggling to obtain sufficient spare parts for the B-52's current engines. Without updated contingency planning, the Government Accountability Office warned, the Air Force risks falling behind on scheduled maintenance, potentially affecting aircraft readiness.

GAO conducted the review in response to a provision in a Senate report directing the agency to assess B-52 modernization. Investigators reviewed Air Force acquisition and sustainment documents, visited the B-52 program office, repair depot and logistics center, analyzed data on depot performance, spare parts, support equipment requirements and aircraft availability, and interviewed Air Force officials.

Political Stakes

The report, published July 31, is the public version of a sensitive report issued earlier that month. The Department of Defense determined that some schedule and mission-capable information was sensitive, and GAO omitted that material from the public version.

GAO issued six recommendations to the Department of the Air Force. The Air Force partially agreed with the first recommendation, which calls for delaying the Commercial Engine Replacement Program production decision until the program office evaluates the risks and benefits associated with recent cost growth and schedule delays. The service fully agreed with the remaining five recommendations.

The recommendations also call for the Air Force to assess the practicality, benefits and affordability of digital engineering across current modernization programs, update the B-52 Modernization Platform Integration Plan to prioritize all modernization efforts, better align that plan with strategic goals, identify measures to mitigate the risks of maintaining multiple aircraft configurations, update repair plans to account for potential modernization delays, and clarify responsibility for managing B-52-specific support equipment throughout its life cycle.

What's Next

The Air Force will determine whether and how to implement GAO's recommendations as the B-52 modernization effort continues. The most immediate issue is whether the service reevaluates its production strategy for the Commercial Engine Replacement Program before moving further into production.

GAO will continue monitoring the Air Force's progress in addressing the recommendations through its ongoing oversight process.

The Bottom Line

GAO concluded that the Air Force's largest B-52 modernization effort is becoming more expensive and falling further behind schedule while maintenance risks continue to grow. Without reassessing production decisions and updating long-term sustainment planning, the Air Force could face increased costs, maintenance disruptions and reduced readiness as it works to keep the B-52 in service through 2050.

Spot something wrong? Report an issue with this article