Showing posts with label LCS Concept. Show all posts
Showing posts with label LCS Concept. Show all posts

Sunday, March 29, 2026

What Could the LCS Do in the Middle East?

Currently, two of the three LCS supposedly based in the Middle East have been moved (evacuated?) to Singapore.[1]  The whereabouts of the third is unknown.  Why aren’t they in the Middle East, perhaps ensuring the safe passage of shipping through the Strait of Hormuz?  Isn’t this kind of mission exactly what they were designed for?  As you recall, the original LCS concept was that they would boldly enter littoral (hence, the ship’s name) waters and neutralize mines, subs, surface, and land threats so that larger, more expensive ships could operate in the area with less risk.
 
So, why aren’t they there?  Well, we all know the answer.  The originally envisioned modules were just flights of fantasy and never materialized.  But, what if the original modules had become available as fully functioning equipment?  Would such LCSes be useful in the Middle East today?
 
Let’s briefly recall the intended functionality of the original modules.
 
MCM – The LCS was intended to stop well outside a minefield and use remote, unmanned assets to clear the area of mines.
 
ASuW - This was, perhaps, the key to the entire LCS concept.  The NLOS (not to be confused with the current Spike NLOS missile) system of loitering, smart, networked munitions would address all threats out to a range of 20+ miles.  By removing all visible threats, it would allow fellow LCSes to deal with mines and submarines.
 
ASW – The LCS was intended to basically stop and throw out an ASW barrier of remote vehicles that would track down and destroy enemy submarines while the LCS remained safely out of reach.
 
 
Thus, a mixed group of LCS would enter an area and the ASuW equipped vessels would eliminate all visible land and surface threats while ASW and MCM equipped vessels eliminated the subsurface threats.  Such a group in the strait, today, would eliminate all missile, rocket, artillery, and speed boat threats to shipping across the width of the strait and twenty miles inland.  UAVs would provide continuous surveillance with NLOS munitions on-call, moments away.  Hidden enemy launchers would be destroyed moments after they emerged from hiding.  The MCM-LCS would search for the rumored, but not yet confirmed, mines.
 
Highly effective, indeed!
 
Of course, the LCS modules were never realized (that’s why it’s called fantasy!) and the LCS proved useless as demonstrated by the Navy’s removal of the ships from the very mission they were designed for.  The concept was okay but it was dependent on non-existent technology coupled with unbelievably inept execution.
 
Since we don’t have fantasy modules but the conceptual need still exists, what do we have that could do the job?  Well, there’s always air power that could, for enormous cost and effort, provide the continuous surveillance and quick response strike that’s needed to deal with emergent threats.  We have Burkes with their single 5” gun that could provide persistent, on-call, fire support if some other asset can provide targeting.  We could land Army/Marines in various locations to search and destroy or provide counterbattery fire.using G/ATOR or similar systems.
 
We have the theoretical capability for ships to do counterbattery fire since the radars are fully capable, lacking only the software to do so.  Why hasn’t the Navy ever bothered to implement counterbattery capability?  Because it doesn’t put big, new, shiny hulls in the water which is how large budget slices are ensured.
 
 
The original LCS concept was valid and the need was legitimate but the actual design was based on non-existent technology and wishful thinking.  We didn’t need the LCS.  The need could have been met with existing assets by implementing counterbattery capability on Burkes, adding much more small UAV capability to ships, and incorporating air power and land forces.  The cost would have been minimal – free compared to what the LCS program has cost us.
 
That we didn’t take the approach of using existing assets simply highlights the Navy’s focus on budget over mission accomplishment.  The LCS gained the Navy large budget share as opposed to simple software modifications or buying some more small UAVs.
 
Until we stop viewing the Navy as a business organization trying to turn a profit (budget slice) and start viewing it as a tool for mission accomplishment, nothing will improve.
 
Where are the LCSes?  The past Navy CNOs need to be brought out of retirement and forced to take responsibility for their dereliction of duty.
 
 
 
_______________________________
 
[1]The War Zone website, “U.S. Navy Minesweepers Stationed In Middle East Are Now In Singapore”, Joseph Trevithick, 18-Mar-2026,
https://www.twz.com/sea/u-s-navy-minesweepers-stationed-in-middle-east-are-now-in-singapore

Thursday, May 2, 2024

LCS and Speed

Recent posts have seen some speculation on what the LCS speed was intended for.  As many pointed out, speed is not a useful feature in and around mines.  So, what was the LCS speed intended to do?  Why was it such a major design requirement?  One could make a good argument that speed was the number one design requirement … but why?
 
I have no idea.
 
Well, that was a short post.
 
Actually, the purpose of the post is to, yet again, emphasize the purpose and importance of a concept of operations (CONOPS) prior to committing to a finalized design and, ultimately, production.
 
The Navy has publicly acknowledged that it never developed a CONOPS for the LCS.  Thus, we have no idea what purpose the LCS speed was to have served.
 
The best speculation I’ve seen is that the speed was intended to move the ship as quickly as possible between the operational/combat area and the nearest module swapping port which, logically, would be quite a long distance from the combat area.  Of course, the Navy abandoned the module swapping concept fairly early on thus rendering the speed feature moot.
 
In addition, the intra-theater speed concept was highly questionable to begin with.  The LCS had short range to begin with and the DOT&E reports and trials quickly reported that the range capability was nowhere near the design spec and they significantly downgraded the range.  Further, high speed consumes fuel at a prodigious rate, further reducing the effective range.  An LCS that made a sustained, high speed, long distance dash from a module swapping port to an operational area would have a useful loiter time in the operational area of just a few hours or days, having consumed its fuel in the dash to get there.  That’s not a combat-useful feature.  A well thought out CONOPS would have revealed that prior to final design and production … assuming that was even the reason for the speed requirement.  This is why you do CONOPS.
 
The LCS provides an object lesson in the need for a CONOPS.
 
CONOPS, CONOPS, CONOPS!
 

Thursday, September 21, 2023

LCS Organization Update

As you know, the LCS program has been in a state of disarray – to put it politely and mildly! – for quite some time.  LCS vessels – the Freedom variant, in particular – are being slated for retirement almost as fast as they’re being built.  Further, the Navy has cancelled the anti-submarine (ASW) module and eliminated that function from the LCS mission (to the extent the LCS has a mission!).
 
You may recall that the Navy had organized the LCS into two groups, one on each coast, with four ships dedicated to each mission (ASW, ASuW, MCM).  Each group of four were to consist of one dedicated training ship and three deployable ships.  Thus, in total, there were to be six dedicated ASW ships, six dedicated ASuW ships, and six MCM ships.
 
The elimination of the ASW mission and the [very] early retirement of a dozen or more LCS has thrown that organization out the window.  Now, the 2023 GAO annual report offers some partial clarity on the new plan for task organization of the LCS.
 
.. 24 MCM packages will support 15 MCM-assigned LCS and nine will deploy from shore and other ships. Ten SUW packages will support eight SUW-assigned LCS and two MCM-assigned LCS.[1]
 
This raises some interesting points:
 
- It appears that the Navy will have only 15 MCM vessels as the total fleet mine countermeasures capability as the current Avengers and MH-53E helos retire shortly.  That’s a pitifully small number against the hundreds of thousands of mines in the Chinese (and NKorean, Iranian, and Russian) inventory.
 
- It appears that the Navy will have only 8 dedicated ASuW LCS which is surprising since anti-swarm was, arguably, the main function of the LCS.
 
- There is some confusion about the meaning of the statement that two of the ASuW packages will support two MCM LCS.  Does this mean the Navy will attempt to double up on modules on two ships?  Given the critical weight limits, that seems not to be feasible.  Perhaps it means that those two LCS will be ‘swappers’ even though the Navy officially abandoned the module swapping concept?
 
- It appears that the Navy will be left with 25 active LCS out of the original 38 that have been built with 5 already retired and around a dozen more slated for retirement over the next two years.
 
 
 
A program in disarray has become even more confused!
 
 
 
__________________________________
 
[1]U.S. Government Accountability Office, “Weapon Systems Annual Assessment”, Jun 2023, GAO-23-106059, p.148

Monday, January 2, 2023

What Happened To Streetfighter?

Let’s start the new year with a post that may ruffle a few feathers and contradict some dearly held beliefs..

 

The LCS is an abject failure.  Even its staunchest supporters have been reduced to talking not about what LCS is but what it might have been.  Yes, the LCS failed but, oh, Streetfighter!  The Mighty Streetfighter!  If only the LCS had remained true to the Streetfighter concept, what a magnificent combat vessel we would have had!

 

Streetfighter … it has assumed the status of myth and legend;  capable of total domination of the seas and able to defeat vast fleets of the most powerful ships.  It would have ensured world peace, solved global hunger, and established democracy throughout the known universe!     And now we have the LCS.  What happened?  Where did Streetfighter go?  Why was its self-evident superiority not developed? 

 

Streetfighter?

Let’s take a look and see if we can figure out what happened.

 

Here’s a timeline to help keep track and make sense of the various events that led from the origin of Streetfighter to the LCS we have today … or was it the reverse?

 

 

 

Streetfighter / LCS Development Timeline

 

1987

SC-21 (Surface Combatant for the 21st Century) predecessor studies begin

Jan

1991

End of the Cold War

 

1992

DD-21 / SC-21 officially begins

 

1993

Navy begins to focus on small combatant ships (approx. time period)

 

1995

LCS foundational design wargames (Joint Multi-Warfare Analytical Game) take place in mid-1990’s

Nov

1999

Cebrowski and Hughes publish “Rebalancing the Fleet” which is the first mention of Streetfighter

Jul

2001

Cebrowski unveils Streetfighter ship in Wall Street Journal article by Greg Jaffe

Oct

2001

Cebrowski appointed to head Office of Force Transformation by SedDef Donald Rumsfeld

Late

2001

DD-21 terminated

Apr

2003

Lockheed Martin shows initial LCS concept offering

 

2003

Adm. Clark declares LCS his number one budget priority

May

2004

Initial LCS construction contracts awarded

Jun

2005

LCS Freedom laid

Nov

2005

Cebrowski died

 

 

 

As we see from the timeline, the end of the Cold War, in 1991, left the Navy with a fleet of large combatants and no peer enemy.  Faced with potentially declining budgets, the Navy opted to create a new enemy which it dubbed ‘littoral’.  Despite having absolutely no evidence that ‘littoral’ required anything new or unique, the Navy latched onto it as a rationale for continued funding (see, “Littoral Warfare – Is There Such A Thing?”).  The solution to defeating the littoral bogeyman was the LCS, according to the Navy.  Well, wait ... what about Streetfighter?  Wasn’t it the answer to the littoral challenge?

 

Here’s where we start to see the myths surrounding Streetfighter.

 

One of the [many] misconceptions surrounding Streetfighter was that it preceded the LCS.  In fact, as we see in the timeline, the LCS originated with a series of wargames in the mid-1990’s (see, “LCS Conceptual Origin”).  The first mention of Streetfighter does not occur until 1999, some four or five years later.

 

Whether Cebrowski/Hughes got their inspiration for Streetfighter from the LCS origin games or whether they developed their concept independently is unknown.  I can find no reference to Cebrowski having participated in or referencing the LCS origins.

 

In fact, I can find no actual link between Streetfighter and LCS.  There is no document stating that one flowed from, or morphed into, the other.  As best I can tell, the two concepts never overlapped.  Possibly there was informal, undocumented cross pollination but, if so, there’s no evidence of it. 

 

Again, the timeline demonstrates that the LCS concept arose prior to Streetfighter as evidenced by the mid-1990’s design wargames.  Streetfighter first appeared several years after the original LCS design beginnings.  Thus, all the questions and moanings about the LCS failing to ‘stick’ to the original Streetfighter concept appear to be after-the-fact fantasies and reversed fantasies, at that! 

 

To sum up, the Navy’s official response to the end of the Cold War was, initially, the DD-21/SC-21 program which began in 1992.  However, within a few years, small combatant studies and wargames had begun and the SC-21 program was on the road to termination.  The LCS concept took hold and quickly began to metamorphose into the directionless, do-everything-but-do-it-poorly fantasy ship that we have today.  Streetfighter appears to have been a very brief, parallel but not overlapping, side road on the LCS development path.

 

Now, let’s take a closer look at Cebrowski and Hughes article, “Rebalancing the Fleet”, that first mentions the word ‘Streetfighter’.

 

“Rebalancing the Fleet”

 

Cebrowski and Hughes published their landmark piece describing a future fleet structure that incorporated small combatants dubbed Streetfighters, in Nov-1999.

 

While the piece discussed several important, noteworthy issues such as the cost-risk relationship, it failed to offer any details and relied heavily on non-existent technologies and unproven concepts for its envisioned success.  The article was more of a marketing brochure than a substantive technical analysis.  For example,

 

Foremost, Streetfighter will be able to clear out the clutter and sort friend from foe.[1]

 

That’s a great marketing campaign slogan but offers no actual, technical insight or methodologies for its claimed ability to “clear out the clutter and sort friend from foe”.

 

Another myth about Streetfighter is that it was a single, specific ship.  However, in the ‘Rebalancing the Fleet’ article, Streetfighter is described as a family of ‘capabilities’, not a ship.

 

The Economy B force is a family of capabilities—often referred to as the "Streetfighter Concept"—that, in conjunction with power-projection forces, will enable the U.S. Navy to operate anytime, anywhere … [1]

 

Indeed, Cebrowski/Hughes never actually described what Streetfighter was beyond generalities.  There are suggestions of vessels in the 300-1200 ton range with no specifics.  There was no description of size, speed, weapons fit, sensors, etc.  This has led every subsequent naval analyst to assign their own vision to Streetfighter, just as happened to the LCS.

 

The reality is that ‘Streetfighter’ seems to have originally been a reference to a concept of a family of smaller vessels acting as a group.  It was described as a ‘family of capabilities’, not as a type of ship.

 

 

 

A noteworthy follow up piece by Hughes addresses Streetfighter concerns that were raised at the time.

 

“22 Questions for Streetfighter”

 

Hughes, himself, offers criticisms of the Streetfighter concept although he does so in what he believes are positive statements.  For example,

 

One of the first things learned by a task analysis of coastal operations is that low-flying aircraft, not big ships or submarines, are the alternative to streetfighters.[2]

 

Thus, Hughes, himself, offers a far more cost effective and combat effective alternative to Streetfighter in the form of aircraft!

 

In attempting to extol the virtues of Streetfighter, Hughes falls back on the common claim that the enemy will be paralyzed with fear at the thought of a single vessel roaming undetected no matter how individually incapable that vessel might be.

 

… if there is a flock of small ships, each powerfully armed yet hard to detect, then the enemy will live in continuing fear over whether he has found them all.

 

An enemy probably also will see deviltry and cunning in a squadron of streetfighters.[2]

 

This is, again, great as a marketing slogan but woefully short on combat reality.

 

Regarding Streetfighter’s self-defense,

 

A 300-ton streetfighter would depend on stealth characteristics, soft kill, numbers, and the ability to lose itself "in the clutter." It could carry light antiair weapons such as Stingers. The design philosophy should be that visual detection of it will predominate, no present missile guidance system will detect and home on it, and added safely comes from confronting an enemy with a swarm of targets.[2]

 

Even a larger 1200 ton Streetfighter was recognized as having inherent defensive problems,

 

A larger version of 1,200 tons might carry not only soft kill systems but also deployable decoys and Rolling Airframe missile (RAM) or the equivalent, while accepting that low observability and active defense are conflicting characteristics.[2]

 

As Hughes recognizes, you can’t defend without broadcasting (radar) your position and if you broadcast your position, you die since you have no credible defense.

 

Hughes does offer one brilliant and prescient observation,

 

The biggest danger is that streetfighter will be conceived as a junior variation of the projection navy: the same habitability standards, spacious bridge, electronically comprehensive combat information center, offices, and paperwork; a galley with cooks and mess cooks; defenses that are supposed to defeat every attack; stocks for months at sea; standard damage-control teams and procedures; and a guarantee for each young captain that one grounding or failed inspection will send him packing.[2]

 

Indeed, this is exactly what happened to the LCS!

 

 

 

Analysis

 

 

‘Wired’ website offers interesting thoughts about the lack of CONOPS, which doomed the LCS.

 

The confusion over the LCS' roles has gone on so long it has created a bizarre feedback loop, with the Navy, its shipbuilders, the Pentagon and America's regional commanders each developing plans and technologies for the LCS based on conflicting assumptions. The result is a warship theoretically capable of almost anything, and increasingly optimized for nothing.[3]

 

This vagueness and lack of a concept of operations also extended to Streetfighter.

 

For all Cebrowski's and Hughes' passion about small-ship theory, and Clark's and Rumsfeld's determination to build the diminutive vessels, no one had clearly defined exactly what a small warship should look like, and what it should and shouldn't do. On at least one key point – expendability – the strategists and the mainstream Navy were totally at odds.[3]

 

This fundamental flaw – the lack of a viable CONOPS - continues to this day and not just for the LCS but for any conceptual small combatant.  I have yet to hear any viable CONOPS for any small combatant in US service.  Supporters of small combatants are wildly enthusiastic about the ships, themselves (meaning, the weapons, speed, stealth, and other physical characteristics), but totally ignore the fundamental question of how the ship will be used. 

 

This was the problem with Streetfighter. 

 

This was the problem with the LCS. 

 

This is the problem with any small combatant.

 

We’ve thoroughly discussed the problems that arise from the lack of a CONOPS when a ship is designed.  Well, here’s someone else’s discussion of the problem as it relates to the LCS.

 

The only thing everyone agreed on was that the LCS would sail close to shore. But no one specified how close "close" really was. One mile? Twenty-five miles?

 

As theorists, Hughes and Cebrowski never had to be specific. Rumsfeld, for his part, was notorious for ignoring the nitty-gritty details of running the military. Clark tried his best to keep his boss happy and grow the fleet.

 

"As a result, the Navy’s leadership was forced to test out arguments for the new ship on the fly," [DepSecDef] Work recalled. "Sometimes the LCS was labeled transformational because of its high speed ... other times it was because the ship was designed to defeat 'asymmetric' littoral threats." On still other occasions, the Navy chose to emphasize LCS' supposed "transformational impact on the American shipbuilding industry."

 

"The constantly changing rationale for the new ship helped to confuse both the Navy’s internal and external audiences," Work concluded.

 

In short, the circumstances of the LCS' genesis were a perfect recipe for a shipbuilding fiasco.[3]

 

And the utterly predictable result occurred.

 

The [LCS] plan was, in a word, ambitious – which was not what Cebrowski and Hughes had in mind when they argued for the Navy to add smaller, simpler, cheaper ships. In the course of just four years, the Navy fought, embraced, and then completely corrupted the small-ship philosophy. Instead of compact, brute-simple coastal brawlers, it would get over-inflated, gas-guzzling, gutless ships dependent on ultrahigh-tech gizmos.

 

In the absence of clear missions and realistic capabilities, LCS became everything to everyone, as long as no one thought too hard about anything.[3]

 

More generally, the following illustrates a (the?) fundamental flaw in all the ‘streetfighter’, small combatant type ship designs and force structures.  It makes the assumption that large ships are unable to function in a littoral scenario – an assumption that is utterly unsupported by any evidence and, in fact, a great deal of evidence exists to support the exact opposite conclusion!  For example, the destroyers at Normandy that sailed right up to shore to do battle with German shore batteries conclusively proved that large, ocean-going ships had no problems operating and fighting successfully in shallow waters.

 

In the late 1990s, the Navy realized it had a problem. Its 9,000-ton cruisers and destroyers, inherited from the Cold War, were great for open-ocean warfare against the Soviets. But the same ships were considered too vulnerable to safely operate in the shallow, crowded, chaotic coastal waters – aka, the "littorals" – that were fast becoming the next naval battleground.

 

Here, dangers might include gun-armed speedboats, missile-firing fast-attack craft, small submarines and sea mines, plus antiship missiles and aircraft launched from land.

 

The preceding assumption, that large, ocean-going ships can’t function and survive in shallow waters is valid only if one cedes all offensive operation to the opponent … which is exactly what we’ve done;  witness Iran’s constant harassment (to include mining of merchant ships – an act of war or piracy or both).  If, on the other hand, one retains the right of offensive action, any large, ocean-going combatant can wipe away littoral threats with no effort.

 

 

Conclusion

 

It seems clear that the common belief that Streetfighter preceded the LCS is incorrect.  The corollary belief that LCS ‘abandoned’ the Streetfighter design is also false as there is no evidence that the LCS ever had any formal connection with Streetfighter.  Further, Streetfighter was never a Navy program of record and, therefore, there was never any official embrace of Streetfighter other than, perhaps, some informal and undocumented hope that Cebrowski’s appointment by Rumsfeld to head his pet Office of Force Transformation might result in some degree of incorporation of the Streetfighter concept into the LCS.  By that time, however, the LCS was already pretty well set, at least in concept.

 

Most importantly, Streetfighter appears to have never been given any definitive form in the way of specifications.  In fact, I can find no Cebrowski-Hughes artist’s concept drawing of what the Streetfighter vessel might have looked like.  The lack of any formal description has given rise to endless versions proposed by subsequent naval commentators but none have the slightest connection to Cebrowski and Hughes’ concept which, indeed, never actually specified an actual vessel – only a ‘family of capabilities’.

 

Thus, all the romanticism about Streetfighter is just that:  romantic notions that were never actually espoused by Cebrowski and Hughes.

 

All subsequent Streetfighter discussion has been pure, individual speculation with no attached CONOPS – just a vague array of marketing slogans by people who are more enamored of ship weapons than any useful description of how a Streetfighter would actually function.  If you want to begin to get an understanding of just how flawed the small combatant concept is, read the post, “Undisputed and Unaccepted”, which discusses some of the flaws in Hughes small combatant concept as described in his fleet tactics book.


 

We can blame the LCS for a host of failings but failing to follow the design of Streetfighter is not one of them.

 

 

 

 

 

Disclaimer:  Information from the beginnings of the LCS and Streetfighter are hard to find.  If someone can produce information I haven’t found, I’ll gladly consider it and modify my conclusions, if appropriate.

 


________________________________

 

[1]USNI Proceedings, “Rebalancing the Fleet”, Vice Admiral A. K. Cebrowski, USN, and Captain Wayne P. Hughes, Jr., USN (Ret.), Volume 125/11/1,161, Nov-1999

https://www.usni.org/magazines/proceedings/1999/november/rebalancing-fleet

 

[2]USNI Proceedings, “22 Questions for Streetfighter”, Captain Wayne P. Hughes, Jr., USN (Ret.), Vol. 126/2/1,164, Feb-2000

https://www.usni.org/magazines/proceedings/2000/february/22-questions-streetfighter

 

[3]https://www.wired.com/2011/08/future-warship-ran-aground/


Monday, June 20, 2022

So Close … Too Close?

USNI News website is reporting that the Independence variant LCS USS Montgomery (LCS-8) recently conducted a demonstration launch of Hellfire missiles at targets on land.[1] 

 

Well that’s exciting.  The LCS can now support ground forces.  That’s good, right?

 

“This test proved the critical next step in increasing lethality of the Littoral Combat Ship,” Cmdr. Dustin Lonero, the commanding officer of the ship, said in a Navy news release. “Using our speed and shallow draft, we are now uniquely optimized to bring this level of firepower extremely close to shore in support of our warfighters and operators on the beach.”[1]

 

Outstanding!

 

Just out of curiosity, what’s the range of Hellfire?  The article credits the Hellfire with a range of around 5 miles.  Um … that’s not very far for ground support.  Unless the troops are literally at the water’s edge, the LCS would have to approach closer than 5 miles to land to get its Hellfires in range.  In fact, the maximum inland support range is only 5 miles and even that would require the LCS to be beached.  Is there really a lot of ground support to be done less than 5 miles from shore?

 

Moving on …

 

Do we recall that the Navy has stated that its amphibious ships can’t approach land closer than 25-50 miles due to the threat from anti-ship missiles?  And yet, now we’re going to send the LCS within 5 miles of land? 

 

Do we recall that the Russians just lost a Slava class cruiser operating close to shore? 

 

Do we recall that the ex-HSV Swift was demolished off Yemen by a rocket/missile attack?

 

Are we now saying that we’re going to operate an LCS – which has minimal self-defense capability (and I’m being generous) – within 5 miles of enemy land?  While not a multi-billion dollar ship, the LCS still costs around $600M.  That’s not cheap and expendable.

 

Have we thought this through or, like most Navy actions, is this just a random impulse with no detailed Concept of Operations supporting and justifying it?

 

 

 

_____________________________________ 

 

On a side note, the Navy also had this to say about the awesomeness of the Hellfire:

 

“The Longbow Hellfire missile already plays a key role in the up-gunned surface warfare mission package,” the Navy said in the news release.[1]

 

Just one problem with that statement, Navy.  It’s categorically false.  The surface warfare module is the hugely dumbed down version of the original which called for the NLOS networked, loitering missile which had a range of around 22 miles.  Thus, a 5 mile Hellfire is not a component of an up-gunned surface warfare module.  Instead, it is the sorry and pathetic end result of a failed and now significantly down-gunned module.  It’s an embarrassment not a success.

 

 

 

_____________________________________

 

[1]USNI News website, “LCS USS Montgomery Fires Hellfire Missiles in Land Attack Test”, Mallory Shelbourne, 16-May-2022,

https://news.usni.org/2022/05/16/video-lcs-uss-montgomery-fires-hellfire-missiles-in-land-attack-test


Thursday, February 18, 2021

LCS Scorecard

The LCS production run is nearing an end and the ships have been in service for over a decade so let’s take a moment and see how the promise of the LCS has panned out.

 

 

 

LCS Attribute

Result

Comment

Speed

fail

Arguably the number one design attribute of the LCS, the speed has been steadily reduced to a pedestrian 35-37 kts despite so much being sacrificed at the altar of speed.

Module Swapping

fail

This was abandoned when stability and other issues were found to preclude rapid swapping.  The LCS is now a single function, non-swappable vessel.

Minimal Manning

fail

The original minimal core crew of around 40 has ballooned up to 50-60 and now two crews per ship put the total core crew at well over one hundred.  Add in the module crew, helo detachment personnel, and shore maintenance crew and the manning figure is around 200+ per ship.

Deployment

fail

The rotating crew concept was supposed to enable extended forward deployments but the reality is that very few deployments of any kind have occurred.  Most LCS have remained pier side on a nearly permanent basis.

Affordability

fail

The LCS was originally targeted at $200M each which then increased to $220M and then on up to $750M or so before steadying out around $500M-$600M without modules.

Modules

fail

After nearly two decades of development, no LCS has yet deployed with an effective module of any type despite each module having been dumbed down to nearly ineffective levels.

Numbers

fail

The initial plan called for 55 LCS.  The number was steadily reduced and currently stands at 35 vessels built, under construction, or on order.  The first four LCS have already been retired, leaving a current total of 31 and several of those have been designated non-deployable training vessels.

 

 

 

The LCS is the very epitome of a failed program.  Not a single promised capability has materialized and most capabilities have been significantly dumbed down.  The original concept has been completely abandoned and the entire LCS fleet has been reorganized multiple times along with total revamping of the crew training program.  Speed, range, and endurance have been downgraded.  The modules, which are the main weapon of the LCS, have failed completely and have been continually revised downward.  The ASW module was completely abandoned and re-conceptualized when the original concept was deemed a mistake.  The ASM and MCM modules are struggling with performance and weight issues.  The ASuW module has been hugely downgraded and has still not been fielded in any useful, combat-effective form.  The Freedom class variant is plagued by a systematic propulsion design flaw severe enough to cause the Navy to halt ship deliveries.  Most LCS that have put to sea have suffered major propulsion plant failures and many have suffered multiple failures.  The first four LCS have already been retired.  And the list goes on …

 

The promise of the LCS has utterly failed to materialize.  This is the very definition of abject failure.


Saturday, February 6, 2021

LCS Update

Naval News website has some fascinating tidbits on the LCS.  Let’s take a look.

 

More Studies.  The LCS must lead the league in Admiral-chaired studies.  The Navy regularly forms groups to study the LCS with results that accomplish … nothing useful.  Changes are made but none are worthwhile.  For example, one study group recommended changing from 3 crews for 2 ships to a Blue/Gold (2 crews per ship) scheme.  Okay, one can debate the merits of each approach but, in the final analysis, the change accomplishes nothing.  It doesn’t make the LCS better or more effective.  It just changes the crewing construct.  It’s just churn.

 

Unbelievably, the Navy has now formed yet another study group with the catchy name, LCS Strike Team, to analyze the maintenance, reliability, and lethality issues regarding these small warships.(1)  Maybe this team will recommend switching up and forward to down and aft … you know, something meaningless.

 

The “LCS Strike Team” is also in charge of a few studies, such as a “2016 LCS Study” addressing LCS issues with the crew, maintenance, and training.  This study is set to conclude soon while another study will address the lethality of the LCS. (1)

 

So, studies that study studies?  Sounds productive.

 

 

Maintenance.  This one is interesting.  Everyone except the Navy has known from day one that eliminating a crew’s ability to conduct maintenance and repairs aboard ship was an idiotic decision.  Maybe that will change …

 

RDML Casey Moton, USN, envisions giving more self-sufficiency to the LCS crews to make their own repairs and hopes to make quick progress addressing these maintenance issues. In addition, the U.S. Navy announced late last year that it would test Spearhead-Class EPF USNS Burlington as a maintenance and repair vessel for Littoral Combat Ships.(1)

 

Of course you want more maintenance and repair self-sufficiency onboard ship, Admiral.  It should take all of ten seconds to come to that conclusion although it took you and the Navy a decade and a half.  The problem is that you’ve painted yourself into a corner with the mandated design requirement of minimal manning.  More onboard maintenance and repair means bigger crews, more parts storage, and fabrication shops and the LCS design has no more personnel berthing and hotel services capacity for additional crew and no room for shops unless you start cutting into module space and weight margins.  Face it, you concocted a bad design and now the consequences are coming home to roost.  There’s just not much that can be done to fix the LCS because the original design was so flawed. 


The interesting aspect of this maintenance tidbit was the mention of a potential tender in the form of the Joint High Speed Vessel (now EPF in one of the Navy's ridiculous renaming ventures).  The LCS has cried out for a tender from the start and this could make deployment of the LCS more viable (neglecting the inherent lack of LCS capabilities, of course).  We should get rid of the LCS but, failing that, this would be a significant step forward in getting whatever use we can out of the LCS.

 

 

Mission.  How many years in and the Navy still doesn’t know what mission(s) the LCS can perform??? 

 

Nonetheless, the Vice-Admiral did state that the U.S. Navy has to determine what missions the LCSs are suitable for to accomplish. (1)

 

This is what happens when you design and build without a CONOPS.  A decade and a half into the class’ service life and you still don’t know what mission it can perform.  Here’s a hint:  it can’t perform any mission!

 

 

MCM.  Mine Countermeasures was always an idiotic idea for the LCS.  In the MCM role, the ship is far too large, far too expensive, has useless speed for the slowest task in the Navy, and has limited unmanned vehicle handling and storage capacity and the situation is made worse by the fact that none of the MCM components work. 

 

Stunningly, none of those things are the worst problem with the LCS MCM concept.  The worst thing is that even if everything worked perfectly, the concept is too slow to be useful.  The Avenger minesweeper, which the LCS is trying to replace, is several times faster and it is too slow to be useful.  We’ve documented in several posts the problems with the LCS MCM concept but now the Navy is finally, publicly, admitting it.

 

Compare the LCS to the MCM Avengers. If the Avenger acquires a mine via sonar, it can do a run to detonate the mine.  With an LCS using unmanned systems, the LCS sends out the drone, gathers the data, analyzes it, and if questionable, sends out the drone again, do a different pattern to gather more data and then analyzes it again, and then send out a system to neutralize the mine.  So, for an Avenger that can detect and destroy a mine in four hours, it might take the LCS an entire day and that is because the LCS cannot do a single sortie to detect and engage and relies on unmanned systems. So, it’s like comparing apples to oranges when you look at the LCS and the Avenger.  But looking forward, I think that the LCS, when compared to the LCS itself, the LCS [of today] can clear [mines] faster [than an LCS five years ago with immature and untested MCM packages].” (1)

 

The LCS MCM process involves, at minimum, a three pass process to eliminate a single mine.  You don’t have to be a MCM expert to understand why taking three passes at a mine takes longer than a single pass and why such a process would be absolutely useless in combat.

 

 

Conclusion

 

Well, there you have it.  The Navy is finally catching up to where we’ve been since day one.  Yes, it took the Navy a decade and half but they’re slowly realizing just how bad this ship is.  While I applaud the Navy, ever so slightly, for trying to fix the problems and improve the class, the reality is that the original design is so badly flawed that no significant improvement is possible.  Weight margins are gone, berthing is max’ed out, the ship’s structure is weak, stability (Freedom class) is an issue, and so on.  There’s nothing to work with and no significant improvement is possible due to the inherent design flaws.  Tragically, the only logical thing to do is retire the entire class and cut our losses.

 

Even more tragic is that the entire debacle could have been avoided if the Navy had listened to … well … absolutely anyone outside the Navy because absolutely everyone outside the Navy could see the problems with the LCS right from the start.  The tragedy of the LCS was that it was entirely avoidable and that’s the real tragedy.

 

 

 

__________________________________

 

(1)Naval News website, “Update on the U.S. Navy’s Littoral Combat Ship Program”, Peter Ong, 4-Feb-2021,

https://www.navalnews.com/naval-news/2021/02/update-on-the-u-s-navys-littoral-combat-ship-program/