The Capacity Alibi, Fleet Edition
The Navy keeps solving a capacity problem by relocating it. Four submarine maintenance periods in Western Australia and a second shipyard on the Landing Ship Medium prove the fix is geography, not throughput.
MD Marine Electric | The Current Conversation
USS Colorado (SSN-788) tied up at HMAS Stirling, Western Australia, on Tuesday, Oct. 27, to begin a scheduled month-long maintenance period.¹ It is the fourth submarine maintenance period conducted there since the AUKUS agreement was established.¹ Four visits, one base, and not one additional dry dock stood up on American soil to make any of them unnecessary.
That same week, Hanwha Philly Shipyard won a $269 million contract to build a Marine Corps Landing Ship Medium, the vessel the Corps is counting on to disperse small units of Marines across islands and shorelines to fire anti-ship missiles at the fleet China would otherwise dominate.² TOTE Services, which holds the $2.2 billion contract to manage LSM construction, had already put Bollinger Shipyards on contract to build the first hull before putting the second one out to bid.² Two yards, one program, and the same question sitting underneath both stories: when the Navy needs more capacity, does it build more capacity, or does it just find more addresses?
Call it the Capacity Alibi: the habit of treating a wider map of job sites as proof that the underlying production problem has been solved, when it has only been distributed. This newsletter has used the term before for depot backlogs; this week the evidence shows the same reflex applied to submarine maintenance in Australia and to naval shipbuilding on two coasts.
Four Visits, No New Dry Dock
HMAS Stirling's fourth submarine maintenance period is not a footnote. It is the measure of how far the AUKUS plan has moved beyond pilot status. Colorado will return to Stirling as the first submarine assigned to Submarine Rotational Force-West when it stands up in 2027, a move the Australian government and Pentagon leadership called a "decisive step in strengthening collective deterrence in the Pacific."³ Under current plans SRF-West will eventually host four Virginia-class submarines and a U.K. nuclear attack boat.³
Each of those hulls needs certified nuclear-capable maintenance infrastructure, trained maintainers, and a supply chain that can produce the parts on the far side of the Pacific that a depot in Virginia or Hawaii would produce without a second thought. None of that appears in the reporting on Colorado's arrival, and that absence is the point. The story the Navy is telling is about submarines showing up. The story nobody is forcing it to tell is about whether Stirling's throughput, the actual number of maintenance-days it can absorb per year without queuing boats the way American yards already queue them, has grown to match the hulls now counting on it.
A month-long maintenance period is not a depot-level availability. It is a limited-scope visit, the kind that handles what can be handled without the full industrial footprint a major overhaul requires. Stacking four of those visits and calling it evidence of expanded capacity is the Capacity Alibi in its purest form: the schedule looks fuller, so the capacity must be real. The schedule is not the yard.
The Landing Ship Split
The LSM program tells the same story from the shipbuilding side. The Navy bought the LSM design package for $17 million, a modest number by shipbuilding standards, then split production across two yards before a single hull has delivered.⁴ Bollinger Shipyards on the Gulf Coast has the first vessel.² Hanwha Philly Shipyard now has the second, selected through a competitive process TOTE Services credited to "its competitive pricing and acceptance of TOTE Services' subcontract terms and conditions."² The contract carries options for three more vessels at Hanwha alone.²
Dual-sourcing a new ship class is not inherently a sign of dysfunction. It can be a legitimate hedge against single-yard risk, and this newsletter does not pretend to know TOTE's or NAVSEA's actual reasoning from a press release. What the public record does show is a program office solving a production-rate problem by adding a second address before it has proven the first one can hit its own schedule. That is the same move as sending a fourth submarine to Stirling: more locations standing in for more throughput. It reads as progress on a program tracker. It does not answer the harder question, which is whether either yard has the skilled trades, the electrical outfitting capacity, the cable-pulling and panel-wiring labor pool, to execute concurrent LSM builds without cannibalizing the workforce each yard already has committed to other hulls.
This is where the Capacity Alibi connects to a concept this newsletter named earlier in the Western Pacific buildup: the Concurrency Cascade, the chain reaction that starts when multiple programs compete for the same finite pool of certified trades at the same time. Splitting LSM production across Bollinger and Hanwha does not create new electricians, new pipefitters, or new nuclear-qualified technicians. It creates two bidding lines for the same labor market, and in a tight one, that is a tax on schedule, not a solution to it.
What the Press Release Does Not Say
Naval reporting on exercises and contract awards is built for a narrow purpose: confirm the event happened, cite the dollar figure, move to the next ship movement. USNI's Western Pacific Pulse format is explicit about this. It is a weekly summary of ship movements and exercises, not an industrial-base audit, and it should not be asked to do a GAO report's job.¹ But that is exactly why the Capacity Alibi survives: the only regular public reporting on fleet posture in the Pacific is movement reporting, and movement reporting cannot distinguish a yard with slack capacity from a yard running on fumes.
Nobody in the public record this week asked how many maintenance-days HMAS Stirling can sustain annually once SRF-West reaches its full complement of four Virginia-class boats plus a U.K. attack submarine.³ Nobody asked whether Hanwha Philly Shipyard's LSM award, with its own options for three additional hulls, was priced and scheduled assuming a labor pool that TOTE Services also needs for Bollinger's build.² The contract mechanics are public. The capacity math behind them is not, and that gap is where the alibi lives: the Navy gets to announce expansion without ever being forced to defend the production rate underneath it. [VERIFY: current certified maintenance-day capacity at HMAS Stirling and projected throughput once SRF-West reaches full complement, check NAVSEA and Australian Department of Defence public releases.]
The Trade-Level Tell
A month-long submarine maintenance period is not a mystery to anyone who has read a repair availability work package. It is long enough to handle preservation, limited machinery work, and the kind of electrical troubleshooting that does not require opening a reactor compartment or pulling shafts. It is not long enough for the depot-level work, the kind measured in dry-dock months rather than pier-side weeks, that a hull needs periodically regardless of where it is homeported. The length of the visit is itself a data point the press release does not editorialize on, and it should have been.
Likewise, a $269 million contract for one Landing Ship Medium, against a $2.2 billion vessel construction manager contract covering the class, tells a trade reader something the headline number does not.² That ratio implies a program still pricing early hulls at a premium before serial production drives cost down, the normal curve for any new class. Whether Hanwha's yard has the outfitting capacity to hit that curve on schedule, while also meeting whatever commercial and other Navy work already occupies its waterfront, is the question a $269 million headline cannot answer and was never built to answer.
The Challenge to NAVSEA Program Offices
This is addressed to NAVSEA program offices specifically, not to the yards and not to the allied navies hosting American submarines. The yards bid what the solicitations ask for. Stirling accepts what AUKUS commits it to accepting. The program offices are the only party positioned to ask, before the next contract award or the next maintenance period gets announced, whether the new location or the new subcontractor actually adds throughput or just adds a second place for the same bottleneck to reappear.
The alternative to the Capacity Alibi is not refusing to use Stirling or refusing to dual-source the LSM. It is publishing the capacity math alongside the announcement: maintenance-days per year at the new site, certified tradespeople available against the ones required, a schedule that shows the second yard's ramp-up against the labor pool it will actually draw from. That is not classified information. It is program management, the kind that turns a press release into a plan. Program offices that keep announcing locations instead of publishing throughput are not expanding capacity. They are relocating the day the shortage becomes visible.
The fleet does not need more addresses. It needs more capacity. Those are not the same announcement.
References
- USNI News Western Pacific Pulse: Oct. 30, 2026. https://news.usni.org/2026/10/30/usni-news-western-pacific-pulse-oct-30-2026
- Hanwha Philly Shipyard to Build Navy Landing Ship Mediums, USNI News, Oct. 30, 2026. https://news.usni.org/2026/10/30/hanwha-philly-shipyard-to-build-navy-landing-ship-mediums
- UPDATED: U.S. Navy Taps Attack Boat for 2027 Australian AUKUS Assignment, USNI News, Oct. 26, 2026. https://news.usni.org/2026/10/26/u-s-navy-taps-attack-boat-for-2027-australian-aukus-assignment
- Hanwha Philly Shipyard to Build Navy Landing Ship Mediums, USNI News, Oct. 30, 2026. https://news.usni.org/2026/10/30/hanwha-philly-shipyard-to-build-navy-landing-ship-mediums
