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

Friday, October 6, 2023

Contractor-Led Maintenance

Some things just burn my behind because of their sheer stupidity.  Once such example is the LCS, specifically, the entire concept of shore-based, contractor supplied maintenance.  That was stupid on a plate with a side helping of idiotic fantasy spread with a delicious icing of combat impracticality.  From day one, in the entire universe, only the Navy didn’t instantly recognize that maintenance model as a failure waiting to happen.  Only someone as stupid as a Navy admiral could fail to see the flaws in that maintenance model.
 
Now, from a USNI News website article,
 
Industry experiments with direct contractors have been met with mixed success. In particular, the Navy is moving away from the contractor-led maintenance model that prevents sailors from servicing equipment on ships. In particular, Lockheed Martin’s Freedom-class littoral combat ship design relied on contractor maintenance.[1]

So, having thrown away a generation of naval ship development, an entire class of ship, and flushed billions of dollars down the drain, the Navy is finally recognizing that contractor-led maintenance might not be the best approach?  Well, welcome, Navy.  Welcome to what the rest of the universe has known for decades.  In fact, we’re throwing a massive ‘told you so’ party in your honor.
 
How many admirals does it take to screw in a light bulb?  No one knows because they’ve never yet done it successfully.
  
 
 
_____________________________
 
[1]USNI News website, “Lockheed CEO Pitches Pentagon on Subscription Software”, John Grady, 4-Oct-2023,
https://news.usni.org/2023/10/04/lockheed-ceo-pitches-pentagon-on-subscription-software

Friday, October 7, 2022

Putin Syndrome

It seems all too apparent that one of Russia’s [many] problems related to its invasion of Ukraine is that Putin was fed wildly optimistic information in an attempt to keep him happy and keep lesser officials from being seen as the bearers of bad news.  That led to some incredibly inaccurate and delusional assessments of the situation that bordered on pure fantasy.

 

As we know from the many documented examples on this blog, the US Navy (and military, in general) is engaged in the same kind of ‘good news only’ reporting to superiors who are perfectly happy to accept what should be obvious pieces of fantasy.

 

The latest example of delusional reporting and assessment is this report about the ‘success’ of LCS USS Sioux City during a recent five month deployment.  Breaking Defense website reports on the ‘historic’ deployment with the Navy absolutely raving about the success – the ‘success’ being mainly that it didn’t break down.  According to Cmdr. Scott Whitworth, commanding officer of the blue crew,

 

We were able to steam over 28,000 nautical miles and we had no issues with our combining gear during the entire deployment.[1]

 

We were able to achieve speeds above 30 knots. The engineers have done a fantastic job, both civilian and Navy engineers, developing the procedures where we can operate the ship at high speeds and not cause damage to the combining gear.[1]

 

The Navy seems inordinately pleased that it was able to operate a ship for five months without the combining gear breaking down.  Avoiding a mechanical breakdown seems to be the new standard for success in the Navy.  If that’s not delusional, I don’t know what is.  Putin Navy leadership will be given glowing reports about the success of the deployment and they won’t ask any questions … questions like, the design speed of the LCS was 45+ knots so why are you bragging about 30 kts?  That’s at least 33% below the design specification.  That’s what you call success?

 

This deployment represents a failure of the LCS to achieve its minimum design objective regarding speed and yet the Navy is treating the failure as a success. 

 

This is how you wind up with a deluded, hollow Navy and leaders who have no connection to reality.

 

 

 

______________________________________

 

[1]Breaking Defense website, “Navy’s LCS combining gear problem didn’t interrupt ‘historic’ global deployment”, Justin Katz, 5-Oct-2022,

https://breakingdefense.com/2022/10/navys-lcs-combining-gear-problem-didnt-interrupt-historic-global-deployment/


Wednesday, September 7, 2022

LCS - Worse Than We Could Possibly Have Imagined

The LCS has been beat up by naval observers just about every possible way.  It’s not even fun anymore.  What’s left to criticize?  And yet … it seems as if the problems are even worse than we already knew.

 

USNI News website reports on the content of media remarks by Vice Adm. Roy Kitchener, the commander of Naval Surface Forces, regarding the LCS ships in general and the Independence class, in particular.[1]

 

Bear in mind that the first Freedom LCS was launched in 2006 and the first Independence LCS was launched in 2008.  That’s 16 and 14 years ago, respectively.  One would think that a decade and a half ought to have been enough time to work out the bugs, right?  Well, consider these comments from the article:

 

While the Independence-class ships, based at Naval Station San Diego, have been deploying to the Indo-Pacific, the Navy in recent years has sent the Freedom-class LCS to U.S. Southern Command for counter-drug operations.[1]

 

That deployment pattern illustrates just how bad the Freedom variant’s propulsion problems are.  The Navy is forced to keep the ships within easy sailing (meaning recovery via tug/tow) distance of US ports.  It is also a tacit acknowledgement that they have no combat value.

 

As you recall, the entire LCS concept was predicted on a civilian-provided, forward (meaning foreign) based maintenance model.  Kitchener had this to say,

 

Again, still some things to look at and to work on as far as expeditionary maintenance … [1]

 

So, after 14-16 years, the Navy is still trying to figure out the maintenance model?  That’s bad.  That’s really bad.  It’s damning.

 

After 14-16 years, reliability is still an issue, according to Kitchener who had this to say about the Independence variant reliability:

 

The Navy has made progress on fixing the reliability issues on the Independence-class ships based in San Diego with the help of its Task Force LCS effort, Kitchener said.

 

We’ve had a lot of success with reliability fixes and maintaining those ships on station, operationally longer. We still have some challenges as far as some of them systems and part of that is an effort of making sure we have the right parts at the point of need.[1]

 

So, 14 years operating Independence variants and we’ve ‘made progress’ but we ‘still have some challenges’?  And you know he’s lying applying the maximum positive spin.  The reality is, without a doubt, much, much worse.

 

Regarding maintenance and parts issues, Kitchener said,

 

I’ve been pretty happy with that, but there’s a lot more work to do … [1]

 

Read that statement without the spin and he’s actually describing a still badly broken system … after 14 years!

 

Here’s a damning statement that Kitchener appears to be taking pride in,

 

The Naval Sea Systems Command LCS Strike team, led by Program Executive Office for Unmanned and Small Combatants Rear Adm. Casey Moton, helped the service make fixes to USS Oakland (LCS-24) ahead of its deployment.

 

The work that the strike team did – the NAVSEA engineers – on reliability fixes, we pushed Oakland out, who’s our latest deployer, recently with about 20 to 25 of those fixes.[1]

 

This is telling us that LCS vessels are unfit to deploy unless they receive a focused set of reliability fixes … and lots of them!  This is worse than I thought.

 

More on maintenance:

 

While the Navy has sent the Freedom-class ships to U.S. 4th Fleet for counter-drug operations over the last few years, Kitchener said the service has only recently figured out how to perform maintenance on the ships during deployments.[1] [emphasis added]

 

Seriously?  The Freedom variant has been operating for 16 years and the Navy ‘has only recently figured out how to perform maintenance on the ships during deployments’.  This was the core concept of the ship.  What have you been doing for the last 16 years, admiral?

 

One of the problems the Navy faces, fleet wide, is the issue of data rights.  Kitchener addressed this for the LCS:

 

As we transition to more of the sailor-focused maintenance, we spent a lot of time on getting our sailors some specialized training, buying some of the – getting the rights to some of the gear – we continue to do that.[1]

 

This is demonstrating that we bought equipment without the corresponding data rights – thinking the manufacturer would perform the maintenance - and now that we’ve opted to have sailors perform the maintenance, we find that we lack the specifications, data, and manuals to successfully do so.

 

Kitchener also discusses problems with some seemingly mundane equipment.

 

He pointed to the crane at the back of the LCS that is used to deploy the Unmanned Influence Sweep System (UISS) and the rigid hull inflatable boats (RHIBs) as an example of where the Navy had to train its sailors as part of the maintenance model shift.

 

Traditionally that’s been very problematic for us. There are some mechanical issues with it and there are also some training issues with it and some depth of knowledge issues, quite frankly.[1]

 

Kitchener is acknowledging that we’ve lost the ability, as a Navy, to operate and maintain a simple crane mechanism … and yet we believe we’ll be able to operate incredibly advanced radar  and combat systems?  But, I digress …

 

Kitchener’s general assessment:

 

While the Navy has made headway on LCS reliability and maintenance, Kitchener said the service needs to make more progress to ensure the ships are operating at full capacity.

 

I still get concerned over some of the system readiness. I think we’ve improved our ability to stay underway, though sometimes I think from a system perspective we have more work to do in making sure that not only are they underway, but they’re 100 percent fully redundant on some of their combat readiness.[1]

 

Read between the lines.  Kitchener is saying that the LCS still has massive problems.  If this is what he’s acknowledging, you can be sure there’s plenty more he’s keeping quiet about and the problems are worse than we could possibly have imagined.


 

 

__________________________________

 

[1]USNI News website, “SWO Boss Wants 6 Littoral Combat Ships in Western Pacific”, Mallory Shelbourne, 22-Aug-2022,

https://news.usni.org/2022/08/22/swo-boss-wants-6-littoral-combat-ships-in-western-pacific


Monday, August 16, 2021

What’s Wrong With This Picture?

The Navy has repeatedly tried to early retire the entire Ticonderoga Aegis cruiser class because the Navy claims the ships are too old and too expensive to maintain and operate.

 

The Navy has tried at least twice to early retire Nimitz class carriers because the Navy says that they are too expensive to maintain.

 

The Navy early retired the Tarawa class because they claimed they were too expensive to maintain and operate.

 

 

That’s a lot of highly capable, combat-worthy ships that the Navy has gotten rid of or tried to get rid of due to claimed maintenance and operating costs.

 

 

In contrast, and disturbingly,

 

The Navy has issued multiple awards cumulatively worth up to $2.76 billion to maintain its East Coast-based Littoral Combat Ships, according to a Friday Defense Department contract announcement. (1)

 

So, the cruisers, carriers, and amphibious ship’s maintenance costs are too expensive to justify keeping them in the fleet but the LCS, with no credible combat capability, is worth nearly $3B to keep active?

 

What’s wrong with this picture? 

 

 

 

 

 

Note:  And that’s just the east coast LCS.  The west coast will, presumably, need an equal amount of money for maintenance.

 

 

 

_____________________________________

 

(1)USNI News website, “Navy Issues Multiple Contracts Worth Up to $2.76B for East Coast Littoral Combat Ship Maintenance”, Mallory Shelbourne, 13-Aug-2021,

https://news.usni.org/2021/08/13/navy-issues-multiple-contracts-worth-up-to-2-76b-for-east-coast-littoral-combat-ship-maintenance


Monday, June 14, 2021

LCS - How Much Worse Can It Get?

I’ve stated before that the Navy has reached a point where even they quietly acknowledge that the LCS is a complete and total failure.  Consider the evidence: 

  • nothing but an occasional token deployment
  • attempting to early retire 6 ships
  • all but given up on module development and just going through the motions
  • abandoned module swapping
  • given up on minimal manning
  • acknowledged that the maintenance model of using civilian contractors is an abject failure

 

Now the latest in a string of panels, boards, task forces, reports, investigations, etc. has found more systemic defects.

 

The Navy has identified almost three dozen upgrades and fixes that are needed for the littoral combat ships to improve their reliability, and has selected a commander to oversee the ship’s improvement efforts. 

 

“We found…there were about 32 key reliability issues across both variants that were impacting our ability to get underway and meet those fleet commander requirements,” Vice Adm. Roy Kitchener, the commander of Naval Surface Forces, told reporters Monday. (1)

 

What were the problems?

 

The problems with the Freedom variant are with the combining gear, diesel generator rigid mounts, fuel lines, a water jet upgrade, and boat davit upgrades. The combining gear, which connects the ship’s two engines, had already been determined to be a class-wide defect following propulsion failures with multiple ships. (1)

 

The Independence-class needs water cylinder replacements, pressure switch replacements, diesel engine replacements, and water jackets on the diesel engines. (1)

 

Doesn’t this feel like we’re just beating a dead horse?  I mean, how many more ways do we need to describe what a complete and utter failure the LCS program is?  What’s the point? 

 

With that complete lack of interest in further beating the dead LCS horse, I would like to note what I feel is the most significant aspect of this latest LCS debacle and that is the title of the next guy who’s going to ‘fix’ the LCS:

 

The study’s data and conclusions guide efforts to improve the ships by Task Force LCS, led by Rear Adm. Robert Nowakowski, the deputy commander of both Navy Recruiting Command and Naval Education and Training Command Force Development. (1)

 

Deputy commander of Navy Recruiting Command and Naval Education and Training Command Force Development?????  Are you kidding me?  Was the commander of the Navy Footwear Recommendation Board too busy?  Were the Annapolis midshipmen all busy studying for finals?  This is who they had to get?  How much less importance and emphasis can you assign something? 

 

This tells me, unequivocally, that the Navy has given up on the LCS.  We’re going to see a constant stream of requests to Congress to retire the LCS ships, a few each year until the entire class slowly and quietly disappears.  Although they won’t quite say this publicly, the Navy would like nothing better than to have the LCS fleet fade into the sunset.

 


 

 

____________________________________

 

(1)Defense One website, “Navy Finds 32 Problems with Littoral Combat Ships”, Caitlin Kenney, 8-Jun-2021,

https://www.defenseone.com/threats/2021/06/navy-finds-32-problems-littoral-combat-ships/174588/


Monday, August 3, 2020

CNO Gilday Remembers The LCS

Let’s be honest, after many years of enjoyable LCS-bashing, we’ve kind of forgotten about them, haven’t we?  They can’t do anything.  The Navy has pretty much given up boasting about their single-handed, war-winning capabilities.  They don’t deploy.  They have no useful modules.  Four have already been designated for very early retirement in an admission of uselessness by the Navy.  The rest just sit pier-side and pass time waiting for their own early retirements.  We’ve moved on to other, more relevant issues.

Well, Chief of Naval Operations (CNO) Gilday seems to have suddenly remembered the LCS and wants to see them deployed a few more times.  Of course, what they would usefully do on deployment, he didn’t say and I can’t imagine but at least it might give the crew some sea time.

We’ve known the LCS has had major reliability and maintenance problems, all along, despite the Navy’s constant glowing affirmations about the miracle of the LCS maintenance model – you know, the model that involves no at sea maintenance and requires excessively costly dock side maintenance every couple of weeks.  Well, CNO Gilday now acknowledges the problems.

We know enough about that platform [ed. the LCS] and the problems that we have that plague us with regard to reliability and sustainability, and I need them resolved.” (1)

LCS reliability problems have impacted deployments with some stunning failures and the specter of systemic propulsion problems looms large for future deployments.

“The propulsion architecture’s unreliability means you are going to have to come up with a different way to deploy the ship that doesn’t require every deployment to be transoceanic,” Clark [Bryan Clark, a retired submarine officer and senior fellow at the Hudson Institute.] said. “By the time the ship gets to Singapore, it needs a lot of work done to it and your deployment time is cut down by the fact that you have to repair the ship once it arrives. (1)

What does this systemic inability to transit tell us about the Navy’s fantasy vision of distributed lethality operations deep inside enemy waters?  It tells us that it’s pure fantasy.  If we can’t even transit from one port to the next, how can the LCS operate for extended periods in combat?  Oh wait, we can’t because even if we can get to the operating area without breaking down, we have to return to port every two weeks for dock side maintenance.  Seriously, who came up with this maintenance model and then what genius ignored the model and decided it made the LCS ideal for distributed lethality?

Reliability and maintenance aside, there’s also the matter of the non-existent modules.  The only module that exists in any semi-functional form is the anti-surface warfare (ASuW) module and it’s only semi-functional because the original specifications and requirements have been downgraded so completely.  The anti-submarine (ASW) and mine countermeasure (MCM) modules have been in development for decades and show no signs of being ready in our lifetimes.

CNO Gilday acknowledges the modules failures.

“I have to deliver ... both the mine and ASW modules.” (1)

Good luck, CNO!  You’re running out of time.  Four of the ships are being immediately retired, never having seen a module, and the rest are rapidly running through their lifespans, again without any functional modules.  We’re going to see more LCS retiring without ever having carried a useful, functional module.  That’s just embarrassing.


Just Park It Off To The Side Somewhere 
And We'll Dispose Of It When We Get Some Time



Without modules, the LCS is barely a Coast Guard cutter.  Gilday acknowledges this,

The Navy deployed the LCS Detroit to South America — the 4th Fleet area of operations — last year on a counternarcotics mission, and it returned earlier this month. Those are the kinds of missions for which the LCS is perfectly suited, Gilday said.

“I can deploy these things with a [law enforcement detachment] and a signals intelligence capability, and I can do that on LCS with carry-on gear,” Gilday said. “It’s the right kind of platform for that. (1)

So, CNO Gilday acknowledges that the Navy built a supposed warship whose only suitable purpose is low end, Coast Guard type missions.  Nicely done, Navy.

One of the major problems for the LCS is that it no longer offers anything unique.  For example, the new frigate will offer superior ASW capability – that actually works when the ship is delivered, one hopes!  That said, why would the Navy continue to pour money into the LCS and ASW module when the LCS is only marginally deployable and will begin retiring soon?  It is not hard to foresee the Navy deciding to suspend LCS ASW funding. 

Similarly, the LCS ASuW module offers nothing that the new frigate doesn’t offer ten times over.

The LCS MCM capability would be useful since there is no alternative but it’s still years away and, again, the ships are going to begin retiring before the modules start showing up!

Gilday sums his LCS objective up, thusly,

“LCS for me is something, on my watch, I’ve got to get right.” (1)

Seriously, the opportunity for the LCS to ‘get right’ was before the program started, when it was still a concept.  That was the time to develop a Concept of Operations (CONOPS) and understand what you would and would not get from such a ship.  The opportunity for the LCS to ‘get right’ was before you committed to using non-existent technology.  The opportunity for the LCS to ‘get right’ was before you conceived an idiotic no-maintenance-at-sea concept.

I’m sorry, CNO Gilday but the opportunity for the LCS to ‘get right’ ended on day one of the program when the Navy committed to 55 ships with no CONOPS, non-existent technology, and an idiotic maintenance plan.  There’s nothing left to ‘get right’.  The best thing that can be done, at this point, is to stop kidding yourself that this class has anything to offer, retire the entire class, and move on to more pressing matters.  Stop pouring money into an acquisition money pit and acknowledge what all the rest of us could see from day one – that the program was an ill-conceived, dismal failure – and take your lumps and move on. 



_________________________________

(1)Defense News website, “US Navy prepares major surge of littoral combat ship deployments”, David B. Larter, 1-Aug-2020,
https://www.defensenews.com/naval/2020/07/31/the-us-navy-is-preparing-a-major-surge-of-lcs-deployments/

Friday, February 1, 2019

Frigate Manning and Maintenance


For years, now, the Navy has been complaining that manpower was too costly and, indeed, the Navy embarked on an unwise, misguided, and, ultimately, ill-fated cruise down “optimal” (meaning, minimal) manning creek.  The attempt ended in disastrous maintenance problems and excessive wear and tear on ships due to neglect and many ships were forced into early retirement.

You’ll recall that the LCS was one such attempt at minimal manning.  The ship was, supposedly, going to be crewed by six people and a mascot dog who was also a qualified navigator and cross trained as a cat.  Of course, the LCS crew size has increased dramatically as the Navy has abandoned the initial attempt at three crews for two ships (3:2) and now has settled on two crews for one ship (2:1 or, to put it on a common basis, 4:2 versus the original 3:2).  That, alone, is a 33% increase in LCS manning. 

In addition, the base crew size has increased and the shore side “crew”, which performs the maintenance, has been found to far exceed initial estimates.  The net result is that the LCS now requires as much or more crew as the Perry class frigates!

Okay, that’s interesting but it’s old news.  Well, what’s new news is that the Navy, despite their ongoing moaning about manpower (having apparently forgotten that we once fully crewed a 600 ship fleet) is planning on doubling the crew size of the new frigate by using a blue-gold, 2:1 manning scheme.  That’s right, each ship will have two crews.

Boxall [RAdm. Boxall, director of surface warfare] said the Navy is planning a Blue-Gold crewing model, which means that half the crew would be out with the ship, the other crew is shoreside.

“We’re looking at the blue-gold construct on FFG(X), we’re planning on it, which gives us a larger operational availability – it should double it. (1)

Wasn’t reduced manpower the driving force behind the overall design of the LCS?  So now we’re going to have not one but two crews for each frigate (and each LCS).  Which is it?  Is manpower a crippling drain on the Navy or not?

What about maintenance?  Wasn’t the unintended consequence of minimal manning the neglected maintenance that is crippling the fleet today?  Seemingly, every day we read about more ships requiring more maintenance than anticipated due to deferred and neglected maintenance.  So, what is the Navy doing?  They’re going to keep the new frigates at sea twice as long which means HALF THE MAINTENANCE!  Is the math too complex for you, Adm. Boxall?  How do you not get this?  You’re planning to run these frigates into early graves.  Ironically, the Navy just recently waved their hands and  pronounced extended life spans for all ship classes while noting that it could only happen if the required maintenance was scrupulously performed.  Hey, Adm. Boxall, you can’t perform maintenance on a ship that’s constantly at sea.



Here’s a little bonus LCS/Boxall tidbit.  You know how ComNavOps is constantly harping on the need for a well thought out, well developed CONOPS prior to designing a ship?  Well, consider this quote from the esteemed RAdm. Boxall,

We haven't even thought of the best use of LCS yet, if you ask me. (1)

Hey, Admiral, you know why you haven’t thought of the best use for the LCS yet?  Because you never had a CONOPS and still don’t!  And, best of all, you’re proceeding full steam ahead with your new frigate AND YOU DON’T HAVE A CONOPS FOR IT, EITHER!  Talk about being learning-challenged.

I guess I shouldn’t complain.  For a naval blogger, like myself, RAdm. Boxall is the gift that keeps on giving.  He’s giving me endless material to work with!



________________________________

(1)Defense News website, “Surface Navy Deleted Scenes & The NeverEnding Mission: The Drift XV”, David B. Larter, 25-Jan-2019,
https://www.defensenews.com/naval/the-drift/2019/01/25/surface-navy-deleted-scenes-the-neverending-mission-the-drift-xv/

Monday, June 19, 2017

Spin The LCS

You know what “spin” is, right?  In case you’re not familiar with the word, it means to present a piece of information in the best possible light.  In today’s usage, it generally connotes a distortion of the facts that borders on lying. 

Here’s a simple, classic example from the Cold War era.  A Soviet and a US runner race and the US runner wins.  The Soviets report that the Soviet runner came in second while the US runner placed next to last.  That’s spin!  It’s technically true but so distorts the truth as to border on lying.

Bear in mind the definition of spin as you consider this article posted by Defense News website about the Coronado conducting periodic maintenance in Cam Ranh Bay, Vietnam. (1) 

Let’s look at the Navy’s proud claim about the LCS.

LCS Coronado conducted a required maintenance period while forward deployed and in Cam Rahn Bay.  As the Navy proudly states,

“…a demonstration of its ability to conduct maintenance while deployed.”

What the Navy didn’t say was that dozens of Burkes, and gators, and carriers simultaneously demonstrated their ability to not need a scheduled maintenance period in the middle of a forward deployment.  So, a ship that requires many times more scheduled maintenance stops than any other ship in the fleet can either be seen as a maintenance headache and having significantly reduced availability during deployments or it can be spun as a major accomplishment.

The Navy also didn’t mention the enormous amount of money it must have cost to fly Navy technicians, contractors, tools, parts, etc. to Cam Rahn Bay to conduct maintenance that no other ship in the fleet requires.

The Navy also didn’t mention that the LCS maintenance model only works during peacetime.  During war, the LCS isn’t going to be able to pull into Cam Rahn Bay or any other forward base for maintenance.  Even if the ship could, the maintainers, tools, and parts certainly couldn’t.

So, there was a lot of useful and relevant information the Navy could have presented about this maintenance PR stunt which demonstrated one of the many weaknesses inherent in the LCS design and maintenance model but they chose to spin it as an accomplishment, instead.



_________________________________

(1)Defense News website, “US Navy Littoral Combat Ship Shows Off Maintenance Capabilities Overseas”, Mike Yeo, 15-Jun-2017,


Tuesday, October 18, 2016

Nice To Meet You, Wouldn't Want To Be You

Nice to meet you, wouldn’t want to be you!  That’s how Navy officers must be looking at prospective LCS commands these days.  LCS command is beginning to look like a one way ticket to career suicide.  Two LCS CO’s have been fired this year.  Given how few vessels are in service and how very, very few cumulative days at sea have been racked up by the LCS’s, that’s a staggering firing rate!

“Cmdr. Michael Wohnhaas, who commanded LCS Crew 106, was relieved “due to loss of confidence in his ability to effectively lead and carry out his assigned duties” on Oct. 13 by Commander of Naval Surface Forces, U.S. Pacific Fleet (SURFPAC) Vice Adm. Tom Rowden.” (1)

“Cmdr. Michael L. Atwell, formerly the commanding officer of LCS Crew 101, was relieved of his position on Monday as a direct result of the investigation following the Jan. 12 propulsion casualty that has left the ship sidelined in Singapore.” (2)

It would be one thing if these CO’s were fired for committing a crime or for gross personal misconduct but these officers were fired for no reason other than having the bad luck to be in command when engineering breakdowns occurred – the same breakdowns that have systematically afflicted the LCS class and led to every LCS that has put to sea being sidelined for one problem or another.  Six of the seven commissioned LCS’s have experienced engineering breakdowns.  In its infinite wisdom, the Navy has concluded that the engineering breakdowns were, somehow, the fault of the command officers.  I understand the concept of ultimate responsibility resting with the CO but to blame the Captain for what is clearly a class-wide, systemic problem is insane.  All that’s going to do is scare prospective CO’s away from the LCS program!

If the Navy really wanted to affix blame where it belongs and demonstrate a loss of confidence they would fire the person who came up with the minimally manned crew concept that put overworked, overstressed personnel in situations they weren’t prepared to handle.  They would fire the person who developed the obviously inadequate training process for LCS engineering personnel.  They would fire the person who purchased such complex machinery that the best trained engineers in the Navy (according to the Navy) can’t seem to operate the equipment without screwing it up.  They would fire the person who developed a needlessly complex LCS engineering plant.  They would fire the person who specified a speed requirement that has no tactical utility but resulted in an overly complex engineering plant.  And so on.  Unfortunately, the Navy is more interested in PR and scapegoats than actual accountability.

Prospective LCS commanding officers …….  run away !!!



_______________________________

(1)USNI News website, “USS Freedom Crew CO Relieved Of Duty After Investigation Into Engine Damage”, Megan Eckstein, 14-Oct-2016,

(2)USNI News website, “USS Fort Worth CO Relieved Over January Propulsion Casualty”, Sam LaGrone, 28-Mar-2016,




Wednesday, September 21, 2016

LCS Readiness

Over at his blog, Cdr. Salamander poses the question

“If we had to go to war, exactly what would the LCS we've commissioned over the last eight years be able to contribute?”

I don’t like repeating someone else’s blog post but this is simply too good to pass up.  I’ve kept you apprised of the mechanical failings of the LCS but when you see it summarized, it’s breathtaking (1).

  • USS FREEDOM (LCS 1): Unavailable due to mechanical failures from Jul 16.
  • USS INDEPENDENCE (LCS 2): Available.
  • USS FORT WORTH (LCS 3): Unavailable due to mechanical failures from Jan 16.
  • USS CORONADO (LCS 4): Unavailable due to mechanical failures from Aug 16.
  • USS MILWAUKEE (LCS 5): Unavailable due to mechanical failures from Dec 15.
  • USS JACKSON (LCS 6): Unavailable due to post-shock test repairs.
  • USS MONTGOMERY (LCS 8): Unavailable due to mechanical failures from Sep 16.

LCS-7, PCU Detroit, is built but won’t be commissioned until 22-Oct.

That’s impressive, isn’t it?  We’ve commissioned 7 LCS warships and only one is available for combat and it’s been designated a non-combatant training and test ship!

The good amphibian posed the question about the LCS and war but only provided an immediate, snapshot picture by way of an answer.  Let’s examine the question and answer a bit deeper and see if we can’t expand and expound on the Commander’s post.

A commissioned warship is supposed to be ready for war.  We’ve commissioned 7 LCS so we should have 7 LCS warships ready for war.  Setting aside their mechanical unreliability and unavailability, what do we have in the way of combat capability from our 7 LCS?

Currently, there is no functional mine countermeasures (MCM) module or anti-submarine (ASW) module.  That leaves only the anti-surface warfare (ASuW) module which consists of two 30 mm machine guns a rubber boat and a helo.  Not exactly an impressive combat capability, is it?  Worse, as best I can tell, only a few ASuW modules have been purchased and are available so only a few ships can even carry a module.

So, here we are with 7 commissioned LCS and all they can contribute to a peer war is the ability to shoot small boats?  The problem is that it’s not going to get better, to any appreciable extent, with time.

The LCS was intended to replace,

  • 55 Perry class frigates
  • 12 Avenger class MCM
  • 14 Cyclone class PC

According to the Navy’s latest LCS plan, we’re going to wind up with,

  • 8 LCS-ASuW
  • 8 LCS-MCM
  • 8 LCS-ASW

Further down the road, we may acquire an additional several LCS “frigates” to get to a total build of 40.

MCM vessels, while vital, are not part of the combat fleet.  They are auxiliaries.  That leaves us with a total of 16 LCS-ASuW/ASW that might, using a very relaxed definition, be construed as frigates with an additional 8 or so possible in the future.  We retired 55 true frigates and we’re going to get 16-24 pseudo-frigates to replace them and none of those will be even remotely close to a true frigate in terms of capability.

Similarly, we’re going to retire 12 Avenger MCM ships and get 8 replacements (assuming a workable MCM module is ever developed).

Let’s circle back to Cdr. Salamander’s question about what the LCS’s can contribute to war?  The answer is, next to nothing.

Worryingly, the Navy considers (and counts) the LCS as part of the combat fleet and is betting our future naval combat capability on these floating piles.  You do not want to be an LCS sailor if war comes!




__________________________

(1)cdr salamander website, “LCS - Annus Horribilus”, 20-Sep-2016,


Saturday, September 10, 2016

Navy Surrenders

Since the day the first LCS was announced, observers have analyzed the fundamental LCS concept and found it to be badly flawed.  I won’t bother reciting the litany of flaws inherent in both the ship and its operational concept (to the extent that the Navy had an operational concept – the lack thereof being one of the flaws!).  They are legion.  My general sense is that 90% of observers outside the Navy viewed the vessel as badly flawed.  The Navy, however, steadfastly ignored observers and pressed forward, undeterred, in the face of an endless series of failures of the ship, the modules, and the concept.  Actual deployments only solidified and reinforced the critical observations.  Still, the Navy trumpeted the “success” of the program, going so far as to falsify conclusions about the Fort Worth’s failed deployment to make it seem like a success.

Now, the Navy has come out with the results of an internal review and are going to make fairly sweeping changes that effectively end the LCS concept and tacitly acknowledge that the program was a complete and utter failure.

Here are the specific changes that have been announced (1, 2) in a public statement released by VAdm. Tom Rowden, Commander, Naval Surface Forces (3).

Manning – The vaunted 3:2:1 manning arrangement which would, supposedly, have produced previously unseen increases in actual deployment time while minimizing crew fatigue and without jeopardizing ship maintenance is being abandoned in favor of a blue/gold dual crew manning arrangement like the SSBNs use.  Two crews will alternate on each ship every four or five months.

Modularity – The entire concept of modules being swapped out on a frequent basis as needs dictated is being abandoned.  Each ship will be initially equipped with a given module type which will be permanently embarked for the life of the ship.

Crew Size – The minimal manning effort has been abandoned.  The new crew size will be 70 core crew plus 23 aviation crew for a total of 93 crewmembers per ship.

Retirement – The first four LCSs (two of each version) are being removed from regular deployments and will be used as test/training platforms. 

Organization – The remaining LCSs will be organized in four-ship divisions.  All the Freedom variants (3 divisions) will be home ported on the east coast and the Independence variants (3 divisions) will be home ported on the west coast.  Each division will be composed of four of the same type of ship (ASW, MCM, or ASuW).  Presumably, this means that on each coast there will be one division of each type of function.  Each division will have one ship designated as a training ship with a single crew.  The remaining three ships will operate on the blue/gold crewing system.

Deployment – Ships are planned to be forward deployed for 24 months and then rotate back for refit and maintenance.  The ships are planned to be operationally available for 50% of their life.

Maintenance – Additional Maintenance Execution Teams will be established within the division organization to augment the preventive and corrective maintenance efforts of the individual ships

Ownership – The statement by Adm. Rowden makes it clear that one of the underlying problems with the program was the lack of ownership caused by the 3:2:1 manning construct.  The blue/gold manning is intended to increase the sense of ownership by the crews.  By implication, it is hoped that increased ownership will help prevent the crew-related mechanical failures that have plagued the ships.

Now that we see the changes, let’s look at some of these in a bit more detail.

Manning – Do you remember the initial claims that the LCS would be crewed by a core of 40 sailors and a total of around 75 with module and aviation crews?  Remember how the Navy crowed about how much smaller the crews were compared to the Perry FFGs?  Of course, that was a false claim.  Given the 3:2 manning concept, the Navy had 3 crews for each 2 ships which meant that it actually required 225 sailors to man two ships which is an average of 112 per ship compared to the 175 or so for a Perry.  Even that ignored the dockside crew requirements that the LCS maintenance model required.  So, the actual land and ship crew size was actually just about the same as the Perry. 

Now, with the 2:1 crewing and the increased crew size of 93, it requires 186 sailors to crew one ship.  That’s actually more than a Perry!  And, that still doesn’t take into account the dockside maintenance crew and the newly created Maintenance Execution Teams.  Those additions likely put the crew size up around 200 or so – well above a Perry.

So much for the vaunted minimal crew concept.

Modularity – Remember the claims that the LCS would be able to swap functions (modules) at a moment’s notice thereby making the LCS the most flexible and powerful ship in history? 

So much for modularity.

Aside from the satisfaction of thumbing our noses at the Navy, there’s a bigger, lingering issue.  What are we left with now that each ship will have a single function for its entire service life?  We’re left with ships that are not optimized for whatever role they have.  This has been the biggest problem with the entire LCS concept.  By being modular in design, the ship is not, and cannot be, optimized for any particular function.  The seaframe is sub-optimal (ill-suited) for whichever function it has.  The LCS is far too loud to be a good ASW vessel.  It lacks acoustic isolation of machinery, the water jets are hideously noisy, the self-noise precludes hull mounted sonars, etc.  Similarly, the LCS is ill-suited for MCM or ASuW.  We now have a  class of ship (actually six classes – a Freedom and Independence variant of each of the three ASW, MCM, and ASuW ships) that is, by design, ill-suited for its function(s).  This is a fatal flaw that will become painfully and bloodily apparent in combat.  Unfortunately, there is nothing that can be done about it but this really drives home the inherent flaw in modular designs.

Endurance – The LCS was only sized for about a two week endurance since the maintenance model had it pulling into port every two weeks for maintenance.  However, as the crew size has increased, and now with the even larger crew (93), the endurance has got to decrease due to limitations in food storage, cold storage, fresh water capacity, etc.  This is a ship that is going to spend very little time at sea during a deployment.

Lifespan – A target of 2 years continuously deployed between refits is absurd, especially for a lightly built vessel that is undermanned and has deferred maintenance built in to its operating concept.  These ships will wear out very fast due to programmed systematic neglect.  Expect to see these ships retired early – quite early.

Organization – The described divisional organization presumably means 8 LCS of each function type:  8 MCM, 8 ASW, 8 ASuW.  That’s a very poor outcome.  The LCS was envisioned as the replacement for the Avenger MCM vessels.  There were 12 of them and now it looks as if we’re going to replace 12 MCM with only 8 (and no functioning MCM module, as yet !).  This is a major blow to our MCM efforts that no one is talking about yet.

Well, the Navy has finally surrendered and admitted that the LCS was a colossal failure and is now correcting those aspects that it can.  That’s nice but it would have been a lot cheaper and easier to do so from the beginning.  They can’t even claim the problems were only apparent in hindsight because all these problems were apparent to everyone else from day one.

Unfortunately, many LCS problems remain.  The basic seaframe has fundamental flaws built in.  These ships will never amount to anything and will be retired early.  What a shame.  What a waste.

Navy, I accept your ignominious surrender.  Maybe next time you’ll listen to the critics up front?  Who am I kidding?  No, you won’t.



________________________________

(1)USNI News website, “Results of New LCS Review is Departure from Original Vision”, Sam LaGrone, 8-Sep-2016,


(2)Breaking Defense website, “Navy Sidelines First 4 LCS; Overhauls Deployment, Crewing”, Sydney J. Freedberg Jr., 8-Sep-2016,





Wednesday, September 7, 2016

LCS Engineering Review

The Navy ordered an engineering stand down for all LCS ships after the fourth major engineering casualty in the last year and, specifically, the two most recent engineering mishaps.  The suggestion in the order is that poor training was at fault.  Here’s what VAdm. Tom Rowden had to say,

“These stands down allowed for time to review, evaluate, and renew our commitment to ensuring our crews are fully prepared to operate these ships safely.” (1)

OK, I’m going to assume that Adm. Rowden’s statement wasn’t just for public relations cover.  I’m going to assume that it was a genuine and accurate statement.  Typically, these stand downs are 24 hours.  So, in that short period, whatever it was, the Navy and the LCS community managed to completely review the ship’s personnel, their level of training and knowledge, their competency, review all applicable engineering procedures, evaluate the entire training pipeline, and assess that the crews are fully prepared to operate the ships safely?  That must have been some busy 24 hours!

Hmm …  I’m starting to think that I shouldn’t take Rowden’s statement at face value.  I’m starting to think that maybe it was just a PR cover stunt that accomplished absolutely nothing.

But, wait, there’s more!  According to Rowden there’s more training and reviews on the way.

“I have asked the Surface Warfare Office School (SWOS) commander to review the wholeness of our LCS engineering education and training to include the testing and retraining of all LCS engineers,” Rowden said.  “This training will occur over the next 30 days and will allow the SWOS leadership to review our training program and determine if other changes need to be made to the training pipeline.” (1)

Outstanding!  The LCS engineers, who have each spent years mastering their profession and then an additional year or so qualifying for LCS engineering in the most advanced and rigorous training in the Navy, are now going to be retrained in 30 days!  If we can completely retrain engineers in 30 days, why did it take so long to train them the first time?  Again, the 30 day “training” period is a joke.

It gets better though.

“According to the service, “the required engineering training will be conducted by the SWOS’ engineering team, who will develop both a level-of-knowledge test and specialized training that will be deployed in the next 30 days to the LCS engineering force.” (1)

So, the LCS training program which took years to develop is now going to develop a completely new test and specialized training, also in 30 days.  Again, not really credible, is it?

Unbelievably, there’s still more!

“The commanding officer of SWOS is also conducting a comprehensive LCS engineering review, which will likely take 30-60 days. From there, more adjustments may be made to the engineering training pipeline.” (1)

So, the carefully crafted LCS training program and engineering training programs, developed by many brilliant people, the best the Navy had to offer, over the course of years, is now going to be comprehensively reviewed and adjusted by the commanding officer of SWOS.  If he’s that amazingly good that he can do this along with all his other duties in a span of 30-60 days, why didn’t we have him develop the training programs originally and save untold millions of dollars and years of time?  Yet again, this is pure bilgewater.

And finally,

“In addition to announcing the stand down and the retraining, the service also announced following Sunday’s return of Coronado to Hawaii NAVSURFOR sent a team to the ship “to take a holistic look at the engineering program on board. A preliminary investigation will provide an initial assessment and procedural review of the situation, and any shortfalls will be addressed quickly to get the ship fixed and back on deployment,” read the statement.” (1)

So, yet another team is going to take a “holistic” look at the engineering program.  Setting aside the buzzword bingo aspect of a “holistic” look, this team is going to provide an initial assessment, review, and corrections in an even shorter time – virtually instantaneous, it would appear!  Why do we need all the other reviews if this one can fix everything instantly?  Setting that aspect aside, shouldn’t this kind of review have been conducted, oh, I don’t know, say, when the first LCS was built?

This sudden frenzy of LCS reviews and assessments and retraining is just blatant PR attempts by the Navy to look as if they’re doing something.  It’s also an attempt to avoid being up front and honest and simply saying, “We screwed up the manning levels and training beyond belief and now we need to start over.”

Does this surprise anyone?  You cram high tech, complex equipment that requires careful care and attention into a ship that is horribly undermanned by engineers who have a hundred other duties besides engineering and then wonder why the equipment isn’t operated properly?  If this is a surprise, it’s a surprise only to the Navy.  The rest of us have seen this coming for years.  And this is just the tip of the iceberg.



___________________________

(1)USNI News website, “Navy Ordered Littoral Combat Ship Engineering Stand Down, Retraining Ongoing”, Sam LaGrone, 5-Sep-2016,


Monday, September 5, 2016

Exploring Distributed Lethality

As regular readers know, ComNavOps has not been a fan of the Navy’s distributed lethality concept.  In its original, articulated form, the Navy wanted to arm every ship that floated including amphibious ships, logistic ships, MLPs, MCM, and so on.  That’s just stupid.  Those ships are far too valuable to risk having them within attack range of enemy ships – if you’re in attack range then you’re also in range to be attacked.  Risking vital support ships just to carry 8 Harpoons is idiotic, but, hey, that’s the Navy for you.

Of late, I’ve heard less about arming support ships and more about focusing on arming the LCS as the distributed lethality platform.  Of course, arming a warship isn’t exactly distributed lethality;  it’s just making a warship what it’s supposed to be – a warship.  The only reason this is even a point of discussion is because the Navy has built a class of warship that has no useful weapons!

Let’s focus on arming the LCS with a credible anti-ship missile.  We’ll assume it’s the Harpoon, for sake of discussion, although the Navy is also looking at the NSM and other options.  Let’s further assume that the LCS will carry 8 Harpoons on two Mk 141 rack launchers which has been the standard Harpoon loadout on every ship that has carried Harpoons since the Perry FFGs.  It’s also possible that the LCS will only carry a single launcher which would mean just 4 Harpoons.  The number of missiles is likely a weight related issue given that the LCS is hard up against its weight margins.  For our discussion, the number of missiles doesn’t matter.

So, conceptually, how does this distributed lethality work?

Well, the LCS will have a 100 nm (the exact range depends on the exact missile but this is a good discussion figure) missile and a 20 nm targeting radar.  This is the first challenge in distributed lethality – how does the distributed shooter find a target?  The Navy’s answer is that targeting will come from off board sensors like a P-8 Poseidon, F-35, or Triton UAV.

What happens when an off board sensor finds a target?  In the case of the manned aircraft, does the pilot instantly radio the LCS and tell them to launch a missile?  Of course not.  The pilot doesn’t know what distributed shooters are available.  Further, the pilot doesn’t know the various missions that are on-going in the area and what priority the target he’s found would have.  He doesn’t know the weapon loadouts on the various distributed shooters.  He doesn’t know what missions the distributed shooters are currently on and whether it’s worthwhile to disrupt their current mission.  He doesn’t know whether it’s better to reveal the distributed shooter’s position by attacking or if it’s better to pass up the shot and stay hidden.  In short, the pilot doesn’t have the necessary situational awareness to make a “shoot” call. 

The pilot will simply transmit the information back to the local task group or regional commander for evaluation and decision.  The commander (presumably an Admiral and his staff) will get the information, weigh it against all of his tasks, and decide what to do about it.  You know how those things go.  We’re probably looking at a many hours long process to arrive at a decision. 

Side Note:  What does the off board sensor platform do while waiting for a decision to be made?  If he moves on or returns to base, contact is lost.  Given that the target is moving, the target co-ordinates are lost and the ability to launch an attack is lost if the delay is an hour or more (a ship moving at 20 kts has now displaced from its original target location by 20 nm).  Of course, we can always launch an attack at a predicted location and hope for the best but that’s a rapidly diminishing likelihood of success that, if it fails, will waste a shooter’s load and reveal its location for no gain.  Alternatively, does the off board sensor platform try to stay in contact for, potentially, many hours while waiting for command to make a decision?  Given the relatively short endurance of aerial platforms, that may not even be possible.  If possible, it may not be wise to stay tied to one location near an enemy.  That’s a good way to get shot down!

Let’s say a decision is made to launch an attack.  If there happens to be a shooter within range then the rest is simple.  The shooter is sent targeting data and the attack occurs.  More likely, there are no shooters in range (or not enough shooters in range – an attack will likely require multiple shooters to have a good chance of success).  More hours will pass while the shooters maneuver into range (refer again to the previous side note).  Once all the shooters are in position, the attack occurs.

So, setting aside the issue of trying to operate a data network in the face of peer level ECM, there is nothing wrong with the concept of distributed lethality.  It can find targets and attack them with any available distributed shooter ship.  The major issues would seem to be the process of simply making a decision whether to shoot and what to do with the off board sensor while that decision making process and shooter assembly plays out.

As I pointed out earlier, this is not really distributed lethality but simply networked warships akin to the Navy’s AAW Co-operative Engagement Capabiity (CEC).  Regardless of the semantics, it can work, though clumsily. 

One other possible scenario is that the LCS’ own helo or UAV is used to provide off-board target detection.  A helo or UAV is relatively short ranged which is not a problem since the Harpoon is relatively short ranged.  The problem is that the helo/UAV is also relatively short endurance – a few to several hours – and that assumes the target was located early in the flight.  More likely, the target is located during the second half of the flight with consequently much shorter target contact endurance.  As previously described, locating a target is only part of the process.  A sufficient number of shooters still need to be moved into position and that can take many hours, depending on the dispersal of the shooters. 

Of course, a squadron of LCS can operate together, in close proximity, so that upon target detection most or all of the shooters will be in range or can achieve firing positions in short order.  The flip side of having a squadron operate in close proximity is that it greatly increases the likelihood of the group being spotted and attacked before they can accomplish their purpose.  Close grouping of the shooters inherently contradicts the concept of “distributed” lethality.  If you’re going to have a squadron of LCS operate in close proximity then you may as well just have a single Burke which could not only carry as many weapons as a squadron (assuming a vertical launch anti-ship missile) but could also defend itself which a squadron of LCS cannot.

Let’s now consider what the distributed shooters are doing when they aren’t actively shooting.  Presumably, the shooters are cruising around in enemy or contested waters looking for targets.  However, given the mismatch between the shooter’s sensing range, even using helo/UAVs, and the enemy’s sensors (land based Over The Horizon radar, submarines, AWACS-ish aircraft, maritime patrol aircraft, UAVs, and larger ship radars, it is more likely that the shooters will be found before the shooters can find the enemy.  Thus, the shooters will be sunk one by one.

In the classic distributed lethality model, especially as espoused by Hughes, being detected doesn’t really matter because the individual shooters are cheap and expendable and individual losses create, hopefully, flaming data points due to the enemy revealing their location(s).  Of course, if the enemy attacks with land based anti-ship missiles or aircraft, they haven’t really revealed anything, have they?  It’s only if they attack with ships that they reveal anything we probably didn’t already know. 

So, the likelihood is that our distributed shooters will be destroyed piecemeal for no gain until a suitable target can be found.  If the shooters were cheap enough this might be acceptable.  However, an LCS currently costs $500M - $750M after including post-delivery construction, Government Furnished Equipment, and modules.  The “frigate” version will be even more expensive – likely $750M - $1B.  I’m not sure that a $500M - $1B ship can be considered expendable and sacrificing several just to obtain a single attack opportunity is unlikely to be a beneficial trade.

This also raises the question of how many LCS’s are available for use as distributed shooters?  Let’s assume we build the full 40 that are currently planned.  Of those, 12 are scheduled to be dedicated MCM vessels.  Would we really want to risk our very rare and very valuable MCM vessels?  Remember, when the LCS-MCM comes on line we’ll retire the Avengers and those 12 LCS-MCM’s will constitute our entire ship-based MCM capability!  So, if we don’t risk those as distributed shooters, that only leaves us with 28 possible distributed LCS shooters.  Another 12 or so are scheduled to be dedicated anti-submarine (ASW) ships.  The same logic applies.  Do we really want to risk them?  In this case, the answer may be yes because we do have other ASW assets throughout the fleet.  But, if we opt not to risk them, that drops the available distributed LCS shooters to 16 or less. 

If half to two thirds of  the LCS’s are in port at any given moment, and that’s being generous given the reliability issues, scheduled in-port maintenance requirements (every two weeks), and extremely limited endurance (8-14 days with the current crew levels), then we’re looking at only a half a dozen LCS being available as distributed shooters at any given moment.  That’s not a lot and won’t cover much area!

The LCS’ very limited endurance (8-14 days) combined with the maintenance model that requires the ship to put into port every two weeks (hence, the designed limited stores endurance) makes the LCS a very poor choice as a distributed shooter – no surprise, it’s a poor choice for anything! 

Worse, the requirement to put into port every two weeks implies that it will have to leave the war zone for two weeks or more every two weeks.  The enemy is not going to allow us to use a port located in the contested region.  Thus, the LCS will have to leave and travel to a protected or safe port well back from the war zone.  The LCS will use up most of its at sea endurance and two week operating window just traveling to and from its maintenance ports!  I don’t think the Navy really thought through the use of LCS’s in combat and has not thought through the use of the LCS as a distributed shooter ship.

Let’s now look at this from the enemy’s perspective.  One of the claimed benefits of distributed lethality is that it hugely complicates the enemy’s job.  He won’t know which ships can shoot and will have to assume they all can.  Supposedly, this somehow complicates his day to day life.

In war, each side will attempt to sink every enemy ship they find, right?  It doesn’t matter if the ship is armed or not.  It doesn’t matter if the ship is a warship or cargo vessel.  In short, the enemy will attempt to sink every ship they find.  So, if the enemy will attempt to sink every ship they find, how or why does it matter if the ship is a distributed shooter?  They’re going to try to sink it anyway.  I’m failing to see how the enemy’s tactical position is more complicated.  If they see an LCS, they’ll sink it (it’s not like the LCS can defend itself) whether it has Harpoon missiles on board or not. 

I’m mentally wargaming this from the enemy’s perspective and I just don’t see how the question of whether an LCS is armed or not affects anything the enemy will do.  The enemy’s task is:  see a ship, sink a ship.  It’s not:  see a ship, decide whether it’s a distributed shooter or not, maybe sink it or maybe not. 

If the reverse were true, that the enemy could not, or did not want to, sink a non-distributed shooter ship then their tactical situation would be greatly more complicated.  They’d have to somehow make a definitive determination of the target ship’s weapon load out which would require additional recon assets and time and add a great deal of uncertainty to the tactical picture.  However, that’s a ridiculous scenario.  In a war, the enemy will, see a ship, sink a ship, and not care what weapons, if any, it was carrying.

So, the claim of distributed lethality being a complication for the enemy seems unfounded.

Considering all of this, the concept of using the LCS as distributed shooters seems like a costly, high attrition exercise for relatively little benefit.  Further, the very LCS maintenance model and associated limited endurance make the LCS ill-suited as a distributed shooter.