The fast-attack submarine USS Connecticut, sidelined since a collision with an undersea mountain in the South China Sea sent it limping to port in late 2021, is expected to rejoin the fleet in September 2026. The Seawolf-class boat has spent more than four years at Puget Sound Naval Shipyard, where structural and systems repairs stretched well beyond early projections. Under the Navy’s May 2026 shipbuilding plan, the Connecticut faces a 2031 retirement date, giving it roughly five years of operational life to justify the enormous investment in its recovery.
A narrow operational window after four years in dry dock
The Connecticut entered its shipyard period at Puget Sound in December 2021, according to state-level reporting that tracks the boat’s status. That same source notes the submarine is expected to resume service this September and that the May 2026 Navy Shipbuilding Plan sets a 2031 retirement date. The arithmetic is stark: even if the submarine meets its September target, it will have spent nearly half a decade in repair only to return with about five years left before decommissioning.
For the Navy, those five years carry outsized weight. The Seawolf class consists of just three hulls, each designed for deep-water, high-threat missions that no other platform in the fleet can replicate at the same performance level. Losing one boat to a prolonged repair cycle did not just reduce the number of available submarines. It consumed shipyard capacity that could have gone toward maintaining other attack boats on tighter schedules. With the Connecticut’s return, planners face a compressed timeline to extract maximum value from an asset that cost billions to build and hundreds of millions more to fix.
The collision itself happened in October 2021, when the Connecticut struck an uncharted seamount while operating submerged in the South China Sea. Eleven sailors were injured. The boat surfaced and made its way to Guam under its own power before eventually transiting to Puget Sound. What followed was a repair effort that ballooned in duration as shipyard workers addressed hull damage, replaced sonar equipment, and worked through systems affected by the impact. Each additional discovery of damage or wear added complexity and time, stretching a difficult but finite job into a multi-year overhaul.
By the time the submarine leaves Puget Sound, it will have missed an entire operational cycle in the Indo-Pacific, where attack submarines are in constant demand for surveillance, deterrence patrols, and potential crisis response. That lost time cannot be recovered. Instead, the Navy will try to compress the Connecticut’s remaining service into a tempo that delivers as many deployments as possible before the 2031 retirement date arrives.
Shipyard bottlenecks that shaped the Connecticut’s timeline
The Connecticut’s extended absence is not an isolated case. The Government Accountability Office has documented a pattern of maintenance overruns across the Navy’s public shipyards that predates the collision. A GAO testimony identified persistent maintenance delays affecting both ships and submarines, concluding that these overruns directly hinder efforts to rebuild fleet readiness. The problems are structural: aging infrastructure, workforce shortages, and planning shortfalls combine to push scheduled availabilities past their original completion dates by months or even years.
A separate GAO report examined the main causes of delays at the four public shipyards that service aircraft carriers and submarines. That analysis found that capacity constraints, inadequate planning, and workforce gaps were the primary drivers of schedule slippage. While those findings predate the Connecticut’s collision, they describe the same environment in which the boat’s repairs took place. Puget Sound Naval Shipyard handles both submarine and carrier work, and any unplanned project of the Connecticut’s scale competes for the same dry docks, cranes, and skilled tradespeople that routine overhauls require.
The result is a cascading effect. When one submarine’s repair stretches longer than expected, it delays the start of the next boat’s scheduled maintenance. That next boat then operates longer without an overhaul, increasing the risk of material problems and further unplanned work. The Connecticut’s collision turned what would have been a routine deployment cycle into a years-long drain on one of only four public shipyards capable of performing deep submarine work. The Navy has attempted to mitigate this by shifting some tasks to private yards and by adjusting deployment schedules, but the underlying bottlenecks at public facilities remain a central constraint.
In that sense, the Connecticut’s experience is a case study in how unexpected damage interacts with a fragile maintenance ecosystem. The boat did not enter a modern, surplus-capacity yard able to absorb a surprise project without consequence. It entered a system already running behind, where every additional month in dry dock rippled through the attack submarine force.
What the 2031 retirement date means for Seawolf-class planning
The May 2026 Navy Shipbuilding Plan’s 2031 retirement target for the Connecticut raises a question the available record does not fully answer: how will the Navy manage follow-on maintenance for the remaining Seawolf-class boats, USS Seawolf and USS Jimmy Carter, while also keeping the Connecticut operational through the end of the decade?
Each of those submarines will need its own scheduled maintenance periods before 2031. If the Connecticut’s experience is any guide, even routine availabilities at public shipyards carry a high risk of delay. The GAO’s findings on workforce shortages and infrastructure limits have not been resolved in the years since those reports were published, and the Navy’s submarine construction program at Electric Boat in Groton, Connecticut, and Newport News Shipbuilding in Virginia competes for some of the same skilled labor pool. Any slippage in new construction or maintenance feeds directly into how many attack submarines are available on any given day.
The compressed timeline also affects how the Navy assigns the Connecticut to missions once it returns. Five years is enough time for several deployments, but it is not enough to justify a mid-life overhaul or major systems upgrade. The boat will likely operate in a “use it before you lose it” posture, filling gaps in the attack submarine rotation while the Navy waits for Virginia-class boats to come off the production line in greater numbers. That approach favors shorter, more frequent deployments and minimizes time in port for anything beyond essential repairs.
Strategically, the planned 2031 retirement underscores a broader transition. The Seawolf class was conceived during the Cold War as a high-end undersea hunter, optimized for deep, quiet operations against peer adversaries. The Virginia class that followed trades some of that extreme performance for versatility, cost control, and larger production runs. As the Connecticut nears the end of its service, the Navy will have to decide how much unique capability it can afford to lose before new technologies-such as unmanned undersea vehicles or advanced sensors on other platforms-fill the gap.
For now, the Connecticut’s path is clear but narrow. It must leave Puget Sound on time, complete sea trials without major setbacks, and quickly integrate back into the operational fleet. Any further delay would eat into the already short window before retirement, raising difficult questions about whether the years-long repair effort delivered enough usable service in return. The answer will depend less on the submarine’s technical performance than on whether the broader maintenance system can keep it, and the rest of the attack submarine force, reliably at sea.
More from Morning Overview
*This article was researched with the help of AI, with human editors creating the final content.
