The U.S. Navy’s Littoral Combat Ship program has absorbed billions of dollars and years of criticism over mechanical failures, incomplete mission systems, and shifting sustainment plans. Yet the fleet of small, fast warships designed for shallow coastal waters continues to draw defenders who argue the ships fill a gap no other vessel in the Navy’s inventory can cover. The tension between the LCS program’s well-documented shortcomings and its potential utility in contested littoral zones defines one of the most contentious debates in American naval planning.
A Federal Audit Lays Out the Problems
The clearest accounting of what went wrong with the LCS comes from the U.S. Government Accountability Office, which published an independent audit examining the ships’ performance and support structure. The GAO review documents a series of reliability and availability challenges that have plagued both variants of the ship, the Freedom class and the Independence class, since they entered service.
Among the most damaging findings, the audit describes how the ships have struggled to meet readiness targets, with persistent gaps between planned and actual availability for operations. Mechanical casualties, design flaws, and maintenance delays have all contributed to lower-than-expected time on station. For a platform sold to Congress as a flexible, rapidly deployable asset, that shortfall in readiness undercuts a core element of the program’s rationale.
The GAO also flagged significant problems in cost reporting, noting that the Navy lacked consistent, reliable data on how much it was actually spending to keep the ships operational. Different offices tracked sustainment and modernization expenses in incompatible ways, and some costs were not captured at all. Without accurate figures, oversight bodies and lawmakers have had difficulty assessing whether the program delivers value relative to its expense or deciding how aggressively to retire, upgrade, or repurpose individual hulls.
The sustainment model itself has been a moving target. The Navy originally designed the LCS around a contractor-heavy maintenance approach that differed sharply from how it supports the rest of the fleet, with small crews and shore-based support teams handling most repairs. The GAO audit documented the service’s decision to shift toward a more traditional, Navy-led maintenance structure. That transition has introduced its own friction, leaving some ships without clear maintenance pipelines or fully staffed support arrangements during the shift and further complicating efforts to raise readiness.
Mission Modules That Never Matured
The original selling point of the LCS was modularity. The Navy envisioned swapping mission packages in and out of the ships like cartridges, allowing a single hull to handle anti-submarine warfare one week and mine countermeasures the next. That vision has not materialized as planned. The GAO audit documented mission-module maturity issues, including repeated delays in testing, integration challenges, and slippage in reaching Initial Operational Capability for key packages.
The most significant casualty has been the Anti-Submarine Warfare mission package, which the Navy discontinued entirely after years of development. ASW was supposed to be one of the LCS program’s signature contributions to fleet capability, particularly as the submarine threat from China and Russia has grown. Losing that package strips away a major justification for the program and narrows the range of missions the ships can credibly perform, especially in blue-water environments where submarine hunting remains a central task.
The mine countermeasures package has followed a similarly rocky path. Bryan Clark, a senior fellow at the Hudson Institute, noted in prepared testimony before the House Oversight and Accountability Subcommittee that the Navy only resolved key issues with the mine clearing module in 2023, years after the ships began deploying. The surface warfare package has progressed further than the others and has seen operational use, but the broader modular concept that justified the LCS procurement strategy remains largely unfulfilled. Instead of a single hull seamlessly shifting roles, the Navy has effectively fielded lightly armed surface combatants with limited specialization.
Leadership Gaps and Institutional Drift
The problems with the LCS are not purely technical. Clark’s testimony pointed to a structural issue in how the Navy manages acquisition programs, arguing that rapid turnover among program managers and diffuse lines of authority leave few leaders in place long enough to shepherd complex efforts from concept through deployment. He described a pattern in which officers rotate through key billets every few years, gaining breadth of experience but sacrificing the deep expertise and continuity that ambitious programs require.
That observation cuts to the heart of why the LCS struggled even when individual engineering problems were solvable. A ship class that depends on novel maintenance concepts, new propulsion systems, and modular technology needs consistent, empowered leadership to push through inevitable setbacks and enforce hard choices about requirements, testing, and fielding. When that leadership rotates frequently, institutional knowledge bleeds away and problems compound. The LCS program became a case study in how acquisition bureaucracy can undermine even well-funded defense efforts.
This dynamic also helps explain why cost reporting gaps persisted for so long. Without a single leader or office maintaining long-term ownership of the sustainment data, the Navy’s ability to track spending against outcomes deteriorated. The GAO’s recommendations specifically called for actions to close those reporting gaps, standardize data collection, and clarify who is responsible for long-term sustainment planning. Implementing those fixes, however, requires the kind of sustained institutional attention that Clark described as chronically absent.
Why the Ships Still Matter
Given all of these failures, the natural question is why the Navy does not simply retire the entire LCS fleet and redirect resources to more proven platforms. The answer lies in geography and fleet composition. The Navy faces growing demands in shallow, congested waters from the South China Sea to the Persian Gulf, and it does not have enough ships to cover all of its commitments. Larger surface combatants like destroyers and cruisers are expensive to operate, limited in number, and poorly suited to the kind of close-in coastal work that defines littoral operations.
The LCS, for all its flaws, is fast, relatively cheap to deploy compared to an Arleigh Burke-class destroyer, and designed specifically for the contested coastal zones where future conflicts are most likely to play out. Even with reduced mission-module capability, the ships can perform presence missions, escort duties, maritime security patrols, and limited surface warfare tasks that free up higher-end warships for open-ocean operations. In peacetime, they can show the flag and build partnerships with smaller navies; in crisis, they can provide additional hulls in the water for surveillance and deterrence.
Clark’s testimony reflected a view shared by several defense analysts: the Navy’s original vision for the LCS was sound in concept, even if execution fell short. The ships were meant to operate in environments too dangerous for unarmed auxiliaries but not demanding enough to justify risking a billion-dollar destroyer, particularly in chokepoints and archipelagic waters. That operational niche has not disappeared. If anything, rising tensions in littoral zones and the proliferation of anti-ship missiles, mines, and fast attack craft have made it more relevant.
The Path Forward Requires Honest Accounting
The most common critique of the LCS misses a key distinction. The ships are not useless; they are underperforming relative to their original promise. That gap between expectation and reality is significant, but it does not erase the platform’s residual value. The Navy has already built the hulls and invested in training crews. The question now is whether it can extract meaningful capability from them at a sustainable cost and without crowding out higher-priority modernization efforts.
Doing so requires three things the GAO audit identified as missing: reliable data on sustainment costs, a stable maintenance model, and clear accountability for long-term performance. First, the Navy must complete and maintain a comprehensive picture of what it spends to keep each LCS operational, including contractor support, spare parts, upgrades, and unplanned repairs. That accounting should inform hard decisions about which hulls to retain, which to retire early, and where incremental investments (such as improved sensors or weapons) offer the best return.
Second, the service needs to lock in a sustainment approach that crews, shipyards, and budget planners can rely on. Constantly shifting between contractor-led and Navy-led models has disrupted maintenance schedules and confused lines of responsibility. A stable framework, even if imperfect, would allow incremental improvements rather than repeated reinvention.
Third, senior leaders must designate an office with enduring responsibility for the LCS portfolio, empowered to implement GAO recommendations, oversee mission-module maturation, and coordinate with fleet commanders on how the ships are actually used. That office should treat the LCS less as a failed experiment and more as a constrained asset (limited in some roles, still useful in others) and requiring disciplined management to avoid repeating past mistakes.
If the Navy can meet those conditions, the LCS could still provide valuable capacity in precisely the environments for which it was built, while offering hard-earned lessons for future shipbuilding programs. If it cannot, the ships risk becoming a cautionary tale of how ambition, bureaucracy, and incomplete oversight can combine to produce an expensive fleet that never fully finds its place at sea.
More from Morning Overview
*This article was researched with the help of AI, with human editors creating the final content.
