Naval Air Systems Command Plans LRASM-B-52 Integration Contract with Lockheed; Bomber Could Carry 20 Anti-Ship Missiles
The B-52's 20-missile load per sortie is not a marginal improvement; it is a qualitative shift in maritime strike density. A carrier air wing generates roughly 40-60 sorties per day in surge; a B-52 generates one sortie per 24-48 hours, but that one sortie carries the equivalent strike package of a full day's carrier operations against area targets. The second-order effect lands on munitions procurement: if B-52 LRASM becomes the primary anti-ship platform, the Services will face pressure to accelerate LRASM production beyond the current Navy buy, which will compete with SM-3 Block IB (Raytheon's $6.3B multi-year contract awarded October 8) and AGM-158C inventory for the same industrial capacity.
INDOPACOM gains a second-platform anti-ship strike layer that operates from rear airbases and bypasses carrier-strike-group vulnerability to peer-state air defense.
A B-52 carrying 20 LRASMs can saturate a distributed naval target set—say, a PLA carrier battle group or an amphibious task force—faster than a single carrier air wing can generate sorties, and it does so without risking a $13B hull or the political cost of a carrier loss. The integration timeline matters: if LRASM-B-52 reaches IOC before Taiwan contingency planning cycles lock in (likely FY28 force-structure documents), the capability reshapes how INDOPACOM sizes carrier deployments and munitions surge requirements. If integration slips, the Navy's anti-ship gap widens at exactly the moment the Hormuz closure and Iranian escalation have already forced a rethink of forward-base logistics.
What is the LRASM-B-52 integration timeline—does Lockheed target FY27 or FY28 IOC—and is this contract sole-source or competitive?
Fault Lines
Strategic intelligence, synthesized daily — with a public track record. Every call graded against what actually happened.