Showing posts with label LCS Mission Packages. Show all posts
Showing posts with label LCS Mission Packages. Show all posts

Monday, May 29, 2023

LCS MCM Status Update

As you know, the poor LCS has been sailing for many years without any functional, useful modules.  The modules were supposed to have been:
 
ASuW (anti-surface warfare) – The module has been watered down to near nothingness.  I think, now, it consists of a guy on the bow with a 9 mm handgun.
 
ASW (anti-submarine warfare) – The module was cancelled and ASW has been terminated as an LCS mission.
 
MCM (mine countermeasures) – The module has been in development since just after the Revolutionary War.
 
Well now, after a dozen or so LCS have been retired or scheduled for retirement, the Navy has finally declared initial operating capability (IOC) for the LCS MCM module.  Let’s update ourselves on the MCM module.
 
The mission module components keep changing as they fail, one after the other, so it’s difficult to keep up with the current status but, as best I can glean, the main components of the MCM module are:
 
MH-60 Helicopter
Airborne Laser Mine Detection System (ALMDS)
Airborne Mine Neutralization System (AMNS)
 
Mine Countermeasures Unmanned Surface Vessel (USV)
Unmanned Influence Sweep System (UISS)
AN/AQS-20C mine-hunting sonar
 
 
The helo tows or operates the ALMDS and AMNS while the USV tows the UISS and sonar.
 
Knifefish and other (too many to list) individual components have been tested over the years and have fallen by the wayside.
 
It’s been quite a wait for the MCM module, hasn’t it?  And the wait isn’t quite over.  The first LCS was launched in 2006 and the modules began development prior to that so the MCM module has been in development for an unbelievable 17+ years … and still isn’t quite complete! 
Moton [Rear Adm. Casey Moton, program executive officer for unmanned and small combatants] said the Navy planned to deploy the first LCS with the mine countermeasure package in fiscal 2025.[1]
Deployment in 2025, assuming that isn’t further delayed, would put the development at 19+ years.
 
The Navy’s next task is to congratulate themselves and hand out medals all around.  When asked about the development effort, Moton had this to say, 
“Overall we’ve proceeded well throughout it.”[2] 
Well done, indeed, Adm. Moton!  A mere 17+ years to develop the MCM module is a praise-worthy accomplishment, without a doubt!
 
Well, at least the MCM module is here, now, and we know it works because it’s been tested against simulated mines rather than real ones. 
For the IOT&E testing, Moton said Cincinnati’s crew operated the mission package “against a simulated minefield to achieve required mission objectives, including maintenance, pre and post-mission system prep, post-mission data analysis, in-mission command and control and launch and recovery.”[2] 
Does ‘simulated’ mean an inert mine body or does it mean a virtual, non-existent mine as so many of our exercises use today? 
“We completed approximately 230 hours of MCM USV mine hunt operations, over 33 missions from the host LCS as well as from a shore-based command center to fully asses [sic] the sonar’s performance. We executed a total of 12 airborne sorties, with fielded ALMDS and AMNS systems demonstrating the full integration with the MCM mission package,” Moton said.[2] 
We demonstrated 16 full launch and recovery iterations in the MCM mission package IOT&E.”[2] 
Twelve airborne sorties?!  Wow!  That’s testing the crap out of the system, all right!  That many sorties must have thoroughly tested the system in day, night, shallow water, deep water, good weather, bad weather, warm water, cold water, fast currents, high sea states, and against all types of [simulated] mines, and each test must have been conducted many times over to establish statistical validity.  The Navy managed to test all those conditions and establish statistical relevancy in only 12 sorties!  And against ‘simulated’ mines at that!  I’m impressed!  There is no chance this system won’t work flawlessly in the real world.
 
Sixteen launch and recovery iterations?!  Under all the conditions just mentioned?  Again … wow!
 
Well, obviously, I’m mocking the Navy’s LCS-MCM effort.  Specifically, I’m mocking 
  • the protracted 17+ year developmental effort
  • the pathetically inadequate testing
  • the utterly lacking statistically valid test protocols and repetitions
  • the ignoring of the many real world, operational conditions that ought to have been tested (you had 17+ years, for crying out loud!)
  • the use of ‘simulated’ mines as proof of performance
  • the Navy’s delusional, self-congratulatory attitude to what can only be classified as a fiasco of historic proportions 
If I was the Navy, I wouldn’t have even declared IOC – and, seriously, does anyone believe it’s a real IOC as opposed to a pencil-whipped, public relations stunt?  Instead, I would have left it alone and hoped no one noticed the humiliating, embarrassment the MCM module is.  Heck, in a few years the LCS will all be gone via early retirement and the MCM module status will just be a forgotten footnote in history.  Declaring IOC just brings the entire, painful, humiliating episode to the front for everyone to mock.
 
 
 
_____________________________
 
[1]Defense News website, “US Navy declares its mine countermeasures suite ready for operations”, Megan Eckstein, 11-May-2023,
https://www.defensenews.com/naval/2023/05/11/us-navy-declares-its-mine-countermeasures-suite-ready-for-operations/
 
[2]USNI News website, “Navy Talks Details on LCS Mine Countermeasures Mission Package”, Mallory Shelbourne, 12-May-2023,
https://news.usni.org/2023/05/12/navy-talks-details-on-lcs-mine-countermeaures-mission-package

Friday, August 10, 2018

Their Lips Move

What’s the old joke?  How can you tell when the Navy is lying?  Answer - Their lips move.

If they’re speaking (or writing), they’re lying.  It’s become that simple.

The latest example is a Department of Defense Inspector General (IG) report (1) that states that the Navy fraudulently declared Initial Operational Capability for three mine countermeasures (MCM) components of the LCS MCM mission module.  The MCM components the IG reviewed are

  • AN/ASQ‑235 Airborne Mine Neutralization System (AMNS)
  • Airborne Laser Mine Detection System (ALMDS)
  • Coastal Battlefield Reconnaissance and Analysis (COBRA) Block I
Here’s the blunt statement of finding by the IG.

The Navy declared IOC for the three MCM mission package systems reviewed prior to demonstrating that the systems were effective and suitable for their intended operational uses.

Here’s what out and out fraud sounds like,

We [IG] determined that N95 declared IOC for the COBRA Block I to avoid requesting a sixth change to the IOC date that would further delay the delivery …

Note:  N95 is Major General David W. Coffman, USMC, Director, Expeditionary Warfare (N95)

The DOD-IG is not alone in criticizing the MCM’s ALMDS and AMNS components.  A June 2016 DOT&E (Director Operational Testing & Evaluation) report states,

… the MH-60S helicopter with the current ALMDS and AMNS units would not be operationally effective or suitable to conduct mine countermeasure operations.

“Not operationally effective or suitable”?????  That’s saying it’s useless.

What does all this mean?

As a result, the Navy has delivered units that have known performance problems to the fleet …

Since declaring IOC, the Navy has delivered two ALMDS, one AMNS, and one COBRA Block I units to the fleet with known performance problems …

So, despite all the problems, the Navy is knowingly and intentionally fielding flawed equipment.  This violates the trust of the nation and the trust of the sailors in the fleet.  CNO Richardson needs to be relieved for loss of confidence in his ability to command.



_____________________________________

(1)Department of Defense, Inspector General, “Acquisition of the Navy’s Mine Countermeasures Mission Package”, Report No. DODIG-2018-140, 25-Jul-2018





Friday, May 25, 2018

LCS Hellfire Update

The Navy seems to be committed to mounting the AGM-114L Longbow Hellfire missile on the LCS for use against small craft.  Hellfire had previously been tested in March 2017 for launch capability and the Navy was working on problems with tip over – trying to get the missile to tip over from the vertical launch to horizontal flight and pick up the target.  That issue has apparently been solved, at least enough to allow further testing. 

USNI News website reports that the Navy conducted a live fire test in which four Hellfires were vertically launched from the USS Milwaukee, LCS-5, cued from ship’s radar and “other systems”, and hit small craft targets.  Thus, the test appears to have been an integrated launch using the ship’s combat control system.  The conditions of the test and the results are unknown although the Navy released footage showing one missile hitting a target.  Whether the other missiles hit is unknown.  The targets appeared to be moving although speed and range were not stated and it is unknown whether the targets were maneuvering.  The website article contains a brief video of the launch, if you’re interested. (1)

Just to refresh, here’s a few specs on the Longbow Hellfire, which is the Apache helicopter version of the missile.

Weight     100 lbs
Length     64 in
Diameter   7 in
Seeker     millimeter wave radar
Warhead    20 lbs
Range      ~4 miles with a minimum safe range of 546 yds


Hellfire missiles have a variety of warhead types (fragmentation, shaped charge, etc.) and it is unknown which type or types will be used by the LCS.

LCS Hellfire Launch

Range is less than for helo launched missiles due to the vertical launch.

The LCS launcher appears to be an adaptation of the Army M299 launcher in an embedded box mounted in the former NLOS weapon pit.  The launcher can hold 24 missiles. (2)

Recall the lineage of this LCS weapon. 

  1. The original surface to surface missile for the LCS was to have been the Non-Line of Sight (NLOS) networked munition

  1. After cancellation of NLOS, the Navy looked to develop a custom replacement missile but dropped this project.

  1. The Griffin missile was announced in 2011 as the next replacement but was also dropped.

Note that the Navy has still not officially committed to the Hellfire.  The project is considered developmental and is due to wrap up in 2019-20 at which point a decision will be made about deploying the system.

Successful integration of the Longbow Hellfire missile into the LCS will finally provide a credible anti-swarm capability.  Of course, the range is too short and the warhead too small to be a serious threat to corvette or larger size ships.  Thus, the Hellfire will offer a substantial improvement over the current, well … nothing, but still falls woefully short of the original anti-surface and land attack requirement of the ASuW module.



______________________________________

(1)USNI News website, “USS Milwaukee Launches Hellfires in LCS Surface-to-Surface Missile Module Test”, Megan Eckstein, 16-May-2018,

(2)Navy Recognition, “Q & A with the U.S. Navy on Lockheed Martin Hellfire missiles for Littoral Combat Ships”, 17-Jul-2014,



Thursday, April 12, 2018

LCS Module Update

The original LCS program called for 55 LCS and 62 (if I recall correctly) mission modules.  As the program was whittled down, the number and type of modules was left in limbo.  Now that the LCS program is down to around 32 ships, here’s the latest on the number of modules that will be procured, courtesy of a USNI summary of a government report (1).


  • 10 SUW
  • 10 ASW
  • 24 MCM

This gives a total of 44 deployable mission modules.  Here’s a more detailed breakdown of where/how the modules will be assigned and used:

  • 24 modules (8 SUW, 8 ASW, 8 MCM) to outfit the focused mission LCS ships that make up the LCS divisions of 3 deployable ships and l training ship

  • 3 modules (1 SUW, l ASW, l MCM) in Mayport, FL to ensure high operational
    availability (Ao) of the training systems for the training ships in the LCS divisions
    and to provide spare systems for each focused mission area

  • 4 modules (1 SUW, l ASW, 2 MCM) in San Diego, CA to outfit the test ships (LCS l-4) and provide additional spare capacity for training ships and deployers

  • 4 modules (4 MCM) to outfit LCS 29-32 to mitigate warfighting capability needs across the MCM mission area

  • 9 MCM modules for use on other Vessels of Opportunity (VOOs) to meet the warfighting capability requirements and account for MCM maintenance cycles

There are a few interesting observations from this.

Note the 9 MCM modules that are for “Vessels of Opportunity”.  The Navy doesn’t actually need or want these modules and has no ships to use them but are required by law to procure 24 MCM modules.  From the article,

“An overall total of 24 MCM [modules] are required to comply with Section 1046 of the FY 2018 NDAA which prohibits the retirement of legacy MCM forces until the Navy has identified replacement capability and procured a quantity of such systems to meet combatant MCM operational requirements that are currently being met by legacy forces.”

Thus, the actual total of “wanted” modules is 35 for the 32 LCS seaframes.  This is the final, official nail in the coffin of swappable modules. 

Further, setting aside the 9 MCM modules that will be set aside on the Island of Misfit Weapons and discounting the MCM modules that are dedicated to the training ships, the total operationally deployable LCS mine countermeasure modules is 8 plus, potentially, 4 for LCS 29-32.

Let’s say that again because it’s incredibly important.  The total LCS MCM capability is 8 ships with an ultimate potential of 12.  That’s our total future U.S. military mine countermeasures capabiity.  We’re replacing 14 Avenger class minesweepers and two squadrons of MH-53E MCM helos (total inventory is 28 helos) with 8-12 LCS.

Does anyone really believe that’s adequate?  China, Russia, Iran, and NKorea each have hundreds of thousands of mines and we think 8-12 LCS are adequate to deal with that threat?  There goes any hope of conducting an amphibious assault.  On a larger scale, our Navy is going to be paralyzed by mine threats it can’t deal with.

I trust I’ve made my point about the inadequacy of our MCM force?

Moving on …

ASuW Module.  This module is currently a joke and consists of a couple of 30 mm machine guns and a helo.  The anticipated Longbow Hellfire missile which will provide some actual, though short ranged, firepower is scheduled for operation in 2019-20. 

Hellfire testing to date has demonstrated 83% success rate (1, full doc p.6) from 24 tests.  That’s surprisingly low given the scripted, simplistic, “designed to succeed” nature of such tests.  Real world performance is likely to be half that.

Current projected module purchase cost for the 30 mm guns, Hellfire, and RHIBs is $23.1M per module (1, full doc p.6).  The helo costs are not included.  It is not clear whether those are the individual equipment costs or the complete, packaged, installed costs.  It seems likely that they are just the individual component costs since the report also categorizes “common” costs as a separate item.

The ASuW performance is underwhelming, to say the least.  The Navy has established two levels of performance for the Key Performance Parameters (KPP):  a minimum threshold and a better, desired objective.  The ASuW module, even with the Hellfire missiles, will only barely meet the threshold requirements and will not even be remotely near the objective requirements.  The Navy’s graphic depiction of the actual and projected performance versus threshold and objective is so bad that they didn’t even include scales with actual values (1, full doc p.7).  Further, you know that the Navy’s projected performance is overly optimistic so the performance versus threshold/objective will be even worse than depicted.


ASW Module.  This module currently consists of,

  • Continuously Active Variable Depth Sonar (VDS)
  • Multi-Function Towed Array (MFTA)
  • Light Weight Tow Torpedo Defense (LWT)
  • MH-60R Helo
  • MQ-8 UAV

There is no realistic scheduled operational date for the module although the Navy is suggesting sometime around 2020-21.  As always, that will be delayed.

Current projected module purchase cost for the VDS, MFTA, and LWT is $19.8M per module (1, full doc p.14).  The helo/UAV costs are not included.  It is not clear whether those are the individual equipment costs or the complete, packaged, installed costs.  It seems likely that they are just the individual component costs since the report also categorizes “common” costs as a separate item.

As with the ASuW module, the performance when compared to the KPP threshold and objective requirements is barely adequate.  Further, the DOT&E testing demonstrates that the Navy’s reporting on performance results is “optimistic”, to put it politely.

The MFTA is the only individual component that has achieved Initial Operational Capability (IOC).  Overall module IOC is scheduled for late 2019.  It is certain that will slip.


MCM Module.  This module uses a cobbled together collection of components that seem to change daily.  Current components include,

  • Knifefish UUV for buried or bottom mine detection
  • AES-1 Airborne Laser Mine Detection System (ALMDS) for near surface (top 30 ft) mine detection
  • AQS-20 Sonar for suspended mine (volume) detection
  • ASQ-235 Airborne Mine Neutralization System (AMNS)
  • Unmanned Influence Sweep System (UISS) – acoustic and magnetic
  • DVS-1 Coastal Battlefield Reconnaissance and Analysis (COBRA) for beach and surf zone mine detection
  • MH-60S helo
  • MQ-8 Firescout
  • EX64 Archerfish neutralizer

Additional components are being developed such as an unmanned surface tow drone for sonar and sweep components and the Barracuda system for near surface mine neutralization.

The various capabilities are expected to trickle in over the next several years.

The various module subsystems are not meeting their performance requirements and many are not even close (1, full doc p.22-23).

Current projected module purchase cost for the various non-helo components is $87M per module (1, full doc p.22).  The helo/UAV costs are not included.  It is not clear whether those are the individual equipment costs or the complete, packaged, installed costs.  It seems likely that they are just the individual component costs since the report also categorizes “common” costs as a separate item.

The Annual Report lists module development costs as totaling $2.6B (1, full doc p.28).  Of course, those costs will increase well beyond that before all development is complete!

The report lists total anticipated module procurement costs, including the separate “common” category as (1, full doc p.29),


Module  Qty    Tot Cost   Mod Cost

ASuW     10      $319M     $ 32M
ASW      10      $267M     $ 27M
MCM      24      $2.5B     $100M
Common   44      $576M     $ 13M

Total    44      $3.6B     $ 82M

The key column is the Mod Cost  which is the unit cost for each module of the indicated type.  Note that the costs don’t agree with the individual component costs described above.  The costs listed here are likely to be more accurate.

It is worth noting that the modules have been under development since sometime around 2003/4.  Now, some 14 years later, not a single module exists in an operationally useful form.  Operational modules are not expected for another few to several years and then another few years will be required to actually manufacture the modules.  We are burning through LCS seaframe life spans without any modules to equip them.  It is possible, indeed likely, that some LCS vessels will retire without ever having had a functional, useful module equipped!

LCS module development has been an embarrassment of staggering proportions and the fiasco continues.



_____________________________________

(1)USNI News website, “Littoral Combat Ship Mission Package Annual Report”, February 2018 Annual Report to Congress for the Littoral Combat Ship Mission Modules Program, 3-Apr-2018,
Full document:



Friday, December 15, 2017

LCS Service Without A Module

The LCS program has many problems.  One of the major ones is that there are no combat-useful modules available despite years of development effort.  Without a module, the LCS is just a large patrol boat.

Here’s a table showing the commissioned LCS vessels and the number of years that they have, thus far, served without a module.  Recalling that the target service life span of the LCS is 25 years and noting that almost no Navy vessel has made it to their full life span in recent decades, we’re seeing LCS’s that are expending significant portions of their service lives without any useful capability whatsoever.

Ship      Commissioned   Years Without a Module

LCS-1         2008               9
LCS-2         2010               7
LCS-3         2012               5
LCS-4         2014               3
LCS-5         2015               2
LCS-6         2015               2
LCS-7         2016               1
LCS-8         2016               1
LCS-9
LCS-10        2017               0


The troubling aspect to this is that there is no readily discernible end to the module development in sight.  The Navy claims that each module is just a few years from operation but they’ve been claiming that for the last decade.

This is the equivalent of a battleship being built, commissioned, and serving for years without its main battery.

If a war starts tonight, what can the commissioned LCS’s contribute?  Nothing.

That’s what 9 of our commissioned warships bring to the combat table.  Nothing.


Wednesday, October 11, 2017

COBRA Declared Operational

Apparently, the Navy quietly declared the LCS MCM Coastal Battlefield Reconnaissance and Analysis (COBRA) system operational during the summer as just reported in a USNI News website article (1).  COBRA is an aerial mine detection system that has been under development for many years.

Before we go any further, does anyone believe the Navy’s declaration of operational capability?  How many systems have we see declared operational and nothing short of magnificent only to find out the reality, as actually measured by DOT&E, falls far short?  To put it bluntly, I don’t believe the Navy and I don’t believe the COBRA system is operational.

Setting that aside, something else caught my eye in the article.  Apparently, the Navy plans to purchase a total of 30 COBRA systems. 

“… the Navy bought two systems in Fiscal Year 2017 and will continue to buy more as quickly as budgets allow.  … the plan is to buy 24 additional COBRAs, for a total of 30.” (1)

Now, you’ll recall that after the recent reorganization of the LCS fleet, there will be three functional squadrons of four ships each on each coast, one squadron for each type of module/function: ASW, MCM, and ASuW (see, “Navy Surrenders”). 

Thus, there will be a total of 8 MCM type LCS vessels.  Therefore, 30 COBRA systems is way beyond the minimum required.  For one system per ship, only 8 are needed.  Even with two, the maximum possible per ship, only 16 are needed.  Throw in a few for backups or maintenance unavailabilities and that still leaves a bunch extra.  Is the Navy planning for combat attrition?  That would be wise and very unlike the Navy.


MQ-8 Fire Scout


Recall that the COBRA system is intended to search for mines along the shore.  The host platform for the COBRA is the MQ-8B/C Fire Scout unmanned helo.  In an opposed scenario which, by definition, any mined shore would be, a large, slow, non-stealthy, hovering helo is going to have a very short life expectancy.  Additional COBRA systems will be required, for sure!  However, I’m unaware that the Navy is planning to procure additional UAVs so having extra COBRA systems would be pointless.

I’m a little puzzled by this.  Could the Navy be planning to mount the COBRA systems on some other platform in addition to the LCS/Fire Scout?  Alternatively, does the Navy already know that the reliability is such that 30 units will be required to keep 8 in service?

I’ll have to continue looking into this.



__________________________________

(1)USNI News website, “Navy Declares COBRA Coastal Mine Detection System Operational After Successful Test”, Megan Eckstein, 10-Oct-2017,


Monday, January 30, 2017

LCS ASW Update

Here’s an interesting tidbit from the DOT&E 2016 Annual Report (p.267) concerning the LCS ASW module development and testing.

“The Navy did not conduct any at-sea testing of the ASW mission package in FY16.”

Huh???  I thought the ASW package was settled and a vendor for the variable depth sonar, Thales, was selected and the module was in the final integration and testing stages.  I guess not.

What’s the hold up?  Apparently, it’s weight. 

“The Navy continued its efforts on a weight reduction program for the components of the mission package, including the handling system and support structures for the variable depth sonar and multifunction towed array.”

We’ve repeatedly noted that the LCS (both variants) are overweight and have no weight growth margins.  Every pound added to the LCS has to be balanced by a pound removed.  The LCS “growth” has become a zero-sum game.  In other words, growth is no longer possible for the LCS.

Regarding the VDS vendor selection, apparently that is not the settled issue I thought it was.

“The Navy anticipates downselecting to a single vendor for the variable depth sonar in FY17 and beginning a test program soon thereafter.”

To refresh your memory, the ASW module currently consists of

  • Lightweight Tow torpedo countermeasure (a Nixie-like acoustic decoy)
  • Multi-Function Towed Array
  • Variable Depth Sonar
  • MH-60R and MQ-8B/C Fire Scout VTUAV

The Navy hopes to begin testing in 2018 or 2019.  Assuming, optimistically, a typical few years of testing and a few more years to actually purchase production modules, we’re looking at 2025 or so before production ASW modules reach the fleet.  That’s a lot of time and effort for what will be a pretty anemic ASW fit.  Many LCS ships are going to live significant portions of their service lives without any modules.  

Saturday, December 31, 2016

LCS Assessment Update

Dr. Michael Gilmore, Director, Operational Test & Evaluation (DOT&E), revealed a great deal of previously unknown (at least to me!) information regarding issues with the LCS in a statement to Congress before the US House of Representatives Armed Services Committee (1).  Here’s some highlights with my emphasis added.  This is a long post but worth the read.

Regarding survivability, we see what ComNavOps has been saying all along about the LCS’ lack of shock hardening and failure to meet even Level 1 standards, contrary to the Navy’s explicit lies on this matter.

“With respect to survivability, neither LCS variant is expected to be survivable in high-intensity combat because the Navy’s requirements accept the risk of abandoning the ship under circumstances that would not require such an action on other surface combatants. As designed, the LCS lacks the shock hardening, redundancy, and the vertical and longitudinal separation of equipment found in other combatants. … Thus far, the results of the LCS Live Fire Test and Evaluation (LFT&E) program confirm this assessment.”

“…the LFT&E program has already identified over 100 technical improvements that could be applied to improve LCS’s performance against threat weapons, although, given the ships’ fundamental limitations, none of these improvements will make the ships’ survivability comparable to that of the Navy’s other surface combatants.”

Moving on, Gilmore calls into question the very concept of the LCS - that it will free up larger ships for more important missions.

“… the Navy’s CONOPS require LCS, in some scenarios, to remain stationed near much slower units who are providing the LCS with dedicated air defense support to have any reasonable chance of surviving attacks using ASCMs… Moreover, this CONOPS implies that destroyers and cruisers will be required to provide this protection to LCSs, which is contrary to the concept that independently operated LCSs will free up the Navy’s destroyers and cruiser and “allow [them] to focus on the high-end missions,” which is what the Navy has touted in the past.”

DOT&E’s overall assessment is bleak.

“…DOT&E has sufficient data to conclude that both seaframe variants are not operationally suitable …”

“Not operationally suitable” – ouch!

Here’s some failures that weren’t widely known.

“During this last year, problems with main engines, waterjets, communications, air defense systems, and cooling for the combat system occurred regularly …”

It’s distressing that the listed problems occur regularly given that the ships have been in production and operation for several years.  They’re no longer first of class problems.  At this point, they’re systemic problems.

Gilmore had this to say about reliability,

“… when averaged over time, and accounting for both planned and unplanned maintenance downtimes, LCS 4 was fully mission capable for SUW missions just 24 percent of the 2015 test period.”

Further,

“Both variants … have a near-zero chance of completing a 30-day mission (the Navy’s requirement) without a critical failure of one or more seaframe subsystems essential for wartime operations.”

Crew size comes under fire.

“… the small crew size has limited the Independence variant from operating with sufficient watchstanders to maintain an alert posture for extended periods of time.”

The fundamental maintenance concept for the LCS whereby on-board maintenance is deferred is cited as a limiting factor in LCS effectiveness.

“An example of this limitation occurred during LCS 4’s operational testing during 2015 and 2016, where the ship’s primary air defense system, SeaRAM, suffered from seven long periods of downtime (greater than 48 hours).”

The inherent helplessness of the LCS was further highlighted.

“During the LCS 3 operational test period, the crew was unable to repair multiple critical systems, such as the ship’s navigation data distribution system, the air search radar, and Link 16 tactical link, each of which resulted in multiple days of downtime while awaiting assistance from contractors to troubleshoot and repair the systems.”

The LCS air defense capability is also questioned along with previously unreported revelations about SeaRAM problems.

“it is unlikely that LCS will be able to meet the Navy’s requirements for air defens … More recently, limitations in the SeaRAM system (currently installed on Independence variants) revealed some significant classified concerns.”

One of the oft called for “solutions” to acquisition problems is to buy foreign.  DOT&E, however, offers some practical warnings about problems with foreign purchases.

“… the Navy stopped work on the air defense modeling and simulation test bed because it did not have the intellectual property rights and detailed technical information for the ship’s air defense radar (AN/SPS-75). The lack of intellectual property for these foreign radars has been a problem for both variants of LCS, making it difficult for engineers to develop high-fidelity models and understand the capabilities and limitations of these radars or effect changes when problems are found.”

Although the Navy plans to eventually replace the Freedom variant’s RAM with SeaRAM, DOT&E notes an issue with the Navy’s related decision not to test the RAM system.

“… the Navy does not plan to test (at all) the existing Freedom-variant air defense systems installed on LCS 1 through 15. This is a high risk for deploying crews, given that many Freedom-variant ships will deploy between now and 2020 when backfits of the SeaRAM system on those hulls are scheduled to begin.”

Worse, the Navy has cancelled plans to test the Independence variant’s SeaRAM system.

“The Navy had planned to conduct the first of the planned operationally realistic live-fire events on the self-defense test ship in FY16, but postponed the test indefinitely because of anticipated poor performance predicted by pre-test modeling and analysis of the planned test event scenario.”

Setting aside RAM issues, the Freedom variant has additional AAW issues.

“For the Freedom variant, these tests revealed that because of the limited capabilities of the air defense radar, the crew was unable to detect and track some types of air threats well enough to engage them.”

The Independence variant also had threat detection issues.

“For the Independence variant, although the ships relies on the SeaRAM system, the ship’s air surveillance radar provided LCS crews with only limited warning to defend itself against ASCMs in certain situations.”

And more,

“In the Navy’s developmental test events, we learned that the electro-optical system used to target the seaframe’s gun was unable to provide reliable tracking information against some targets.”

More,

“…the program decided to cancel all subsequent live-fire events, including those scheduled for operational testing, conceding that the Independence variant is unlikely to be consistently successful when engaging some of these threats until future upgrades of the tracking system can be implemented.”

The LCS’ cyber security is also problematic.

“Much of my assessment of the two seaframes’ cybersecurity posture and capabilities is classified and covered in detail in my recent operational test reports. However, I will state that the testing conducted in FY14 on LCS 3, testing conducted in 2015 on LCS 2, and finally the most recent test aboard LCS 4 have revealed significant deficiencies in the ship’s ability to protect the security of information and prevent malicious intrusion. …  the severity of the cybersecurity problems discovered on LCS will degrade the operational effectiveness of either variant until the problems are corrected.”

I have repeatedly discussed the shortcomings of the 57 mm gun and opined that reliance on it to stop swarm attacks was flawed.  Here is DOT&E’s thoughts.

“The inaccuracy of the targeting systems, the difficulty in establishing a track on the target, and the requirement to hit the target directly when using the point-detonation fuze combine to severely impair effective employment of the gun, and limit effective performance to dangerously short ranges.”

The electro-optical fire control has always been a source of puzzlement and DOT&E singled it out for criticism.

“The ship’s electro-optical/infrared camera, SAFIRE, is the primary sensor for targeting the 57 mm gun. The system suffers from a number of shortcomings that contribute to inconsistent tracking performance against surface and air targets, including a cumbersome human-systems interface, poor auto-tracker performance, and long intervals between laser range finder returns.”

The LCS’ single function limitation is noted.

“LCS will have no capability to detect or defend against torpedoes unless the ASW mission package is embarked … The lack of capability implies that a submarine could launch an attack on an LCS, without the crew knowing that they were under attack …”

The LCS’ single function limitation requires that multiple LCS be used to accomplish a given mission and, worse, may require the addition of an Aegis destroyer to provide the AAW capability that the LCS inherently lacks.

“The original vision, therefore, of a nimble, mission-focused ship has been overcome by the realities of the multi-mission nature of naval warfare combined with the multiple threat environments of high-intensity naval conflicts.

Providing additional warships for LCS protection means stretching already limited battle group air defense assets.”

What about ASW performance?  Apparently, the LCS sonar is not optimized for littoral ASW.  Wait, what now?  Doesn’t the “L” in LCS stand for littoral?

“LCS’s sonar system is specifically optimized for deep water and will not be suitable for some very shallow-water environments such as in the littorals.”

If the LCS does find a submarine, there’s not a lot it can do about it.

“LCS has no organic capability to engage submarines and must rely on a single embarked helicopter to deliver torpedoes …”

In summary, Dr. Gilmore’s assessment of the state of the LCS was brutal and paints a picture of a Navy that is blind and zealous in its pursuit of hulls in the water regardless of capability or lack thereof.



__________________________

(1) “Statement By J. Michael Gilmore, Director, Operational Test and Evaluation, Office of the Secretary of Defense, Before the  US House of Representatives Armed Services Committee on the Navy’s Littoral Combat Ship Program”, Dec 8, 2016




Sunday, March 6, 2016

CUSV for LCS MCM

Well, here’s one that somehow slipped by me.  Textron’s Common Unmanned Surface Vehicle (CUSV) has been selected to tow the unmanned influence sweep system (minesweeping) for the LCS MCM module.  The CUSV is an 11 meter unmanned surface craft.  It has self-righting capability, a draft of a little over 2 ft, data links, remote operator control station, max speed of 28 kts, 24 hr endurance, 1200 nm cruising range, can operate up to sea state 4, and can tow 5000 lb at 10 kts.  The payload bay is 14 ft x 6 ft x 3.5 ft.

Textron has a $34M contract to provide a CUSV for the Unmanned Influence Sweep System (UISS).

This sounds like a nice little craft for the minesweeping task other than the potentially slow speed and questionable towing capacity.  As a point of reference, the standard helo-towed Mk105 minesweeping sled weighs around 9000 lbs fueled and operational.  Given the manufacturer’s claim of being able to tow 5000 lb at 10 kts, the 9000 lb Mk105 would most likely be beyond the ability of the CUSV to tow.  I’ve been unable to find a detailed description or specs on the UISS so I don’t know the weight of the equipment.


CUSV - Enough Power To Tow?


I would desperately like to believe that someone in the Navy looked at the CUSV towing capacity before committing to this but we all recall the fiasco of the original Seahawk type helo being found unable to safely tow its intended MCM equipment.  Is this another example of that?  Until someone tells me that this craft can actually tow the UISS, I’m going to remain nervous about this.

So, this is a nice little craft that may or may not be suitable for the task.  Of course, there’s also the issue of whether it can actually meet its specs.  We’ve seen that the MCM module has nice specs but the equipment can’t meet the specs despite years of development.


I’ll keep an eye on this.

Monday, August 31, 2015

MCM Module Failures Continue

As you know, ComNavOps prefers not to simply repeat another website’s posting information.  ComNavOps’ job is to add value through analysis but occasionally another website has information that is just too important and too self-explanatory and must, therefore, simply be largely repeated.  Such is the case with Defense News website’s reporting of the continued failure of the LCS mine countermeasures (MCM) module (1).

You’ll recall that the Navy bet all in on the LCS as the MCM platform of the future.  The existing Avenger class dedicated MCM vessels were literally allowed to rot pierside and the Navy has had to scramble to try to bring them back to operational status due to the failure of the LCS MCM module.  The module has been under continuous development since the beginning of the LCS program and has nothing to show for the effort. 

Hints of the problems have been available in the DOT&E annual reports as well as the relative scarcity of glowing public information releases from the Navy.  The Independence (LCS-2) has been the dedicated test platform for the MCM module and has been employed nearly full time testing the system.

The individual components of the MCM module have been documented to fail to meet their performance requirements and the overall module has never operated with the mandated degree of reliability.

Defense News now reports that the Director of DOT&E, Michael Gilmore, has issued a memo to Pentagon acquisition chief, Frank Kendall, detailing the continued failings of the MCM module and, worse, the Navy’s attempts to mislead concerning system reliability.

“Recent developmental testing provides no statistical evidence that the system is demonstrating improved reliability, and instead indicates that reliability plateaued nearly a decade ago.”

“The reliability of existing systems is so poor that it poses a significant risk to both the upcoming operational test of the LCS Independence-variant equipped with the first increment of the Mine Countermeasures (MCM) mission package, and to the Navy’s plan to field and sustain a viable LCS-based minehunting and mine clearance capability prior to fiscal year 2020.”

What is the actual reliability data?

“… reliability has improved since then, but continues to fall far short of the threshold of 75 hours’ mean time between operational mission failure (MTBOMF).

So, the standard is set at 75 hours between failures.  What is the actual reliability performance?

“But despite all the efforts to improve reliability, Gilmore assessed the RMS system’s current overall reliability at 18.8 hours between failure, and the RMMV vehicle at 25.0 hours.”

Wow!  That’s quite a failing.  The standard is 75 hours and the equipment is achieving 19-25 hours.  That’s not even close.  But it gets worst.  The Navy is attempting to mislead concerning reliability data.

He [Gilmore] took consistent issue with Navy reliability data, pointing out that in some instances, ‘the Navy inflated operating time estimates for the MTBOMF calculations by assuming that post-mission analysis time (when the vehicle is not in the water and not operating) could be counted.’ ”

So not only is the MCM module failing but the Navy is trying to hide the failure.  I’ve stated repeatedly that the Navy’s integrity is highly suspect, to put it as politely as I can.  This is all on CNO Greenert.  He is condoning this type of fraudulent reporting. 

Now, here’s the even more stunning part of this sad story.  Despite all this failure, the Navy is set to restart production of the module!  The module isn’t even close to working so the Navy’s response is to buy more.  This is stupidity at a staggering level.  Way to go Greenert.

There is one more aspect to this that caught my attention.  You’ll recall that the Pentagon recently ordered the Navy to conduct shock testing on the new carrier Ford even though the Navy was attempting to postpone the testing for several years until the next carrier or even indefinitely (see, “Shocking”).  The Pentagon, through the office of the acquisition chief, Frank Kendall, issued the order to the Navy directing the earlier testing.  At the time I wondered who had the authority and was pulling the strings on this.  Now, it appears we have an answer.  Michael Gilmore seems to be communicating directly with Frank Kendall and Kendall seems to be buying in to Gilmore’s thoughts on acquisition and testing deficiencies in the Navy.  This is about as good news as ComNavOps could hope for.  Gilmore has apparently gotten fed up with the Navy’s games and is taking his case to higher authority in the form of Kendall.  This can only benefit the Navy although it’s almost criminally shameful that the Navy has to be forced in this manner to do what’s right.


(1)Defense News, “Official: Minehunting System Shows No Improvement”, Christopher P. Cavas, August 30, 2015,


Thursday, August 20, 2015

The Ship That Couldn't Shoot Straight

The Navy has announced that the Coronado (LCS-4) has completed live fire tests of its major gun systems, the Mk110 57mm, and the Mk46 30mm.  I apologize for using the word “major” to describe a machine gun and a 2.2” gun but for the LCS, they’re considered major.  As usual, the Navy describes the tests as stunningly successful.  Given the Navy’s egregious PR spin efforts in the past, I’m not even going to bother offering a link to an announcement.  If you want to read made up rainbows and sunshine that badly, you can easily find it on the Internet.

So, why is this event of interest?  A couple of reasons, actually.

First, this is a rare sign of progress for the LCS-2 version which has, thus far, failed to deploy and failed to demonstrate any useful progress towards becoming  a functioning warship.  Again, I apologize, this time for using the word “warship” in conjunction with the LCS.  We’re stuck with these ships so it would be nice to see them at least achieve whatever functionality they’re capable of.

Second, and more important, you’ll recall that the LCS-1 version’s 57mm gun was found to be inaccurate at much above 10 kts due to the ship’s vibration.  The question is whether the -2 version suffers from the same problem.  On the one hand, you’d think not simply due to the fact that the two ships have nothing in common as far as the shape of their hulls or the way the move through the water.  On the other hand, both ships have been built extremely light with all signs pointing to woefully insufficient structural reinforcement in both classes.  The -2 version suffered cracking of structural members during heavy weather testing and has had restrictions placed on its operating envelope.

A 57mm gun is nothing to write home about.  You’ll recall that the Zumwalt program rejected the gun and switched to a smaller 30mm gun for close in protection – a fairly stunning commentary on the 57mm.  Still, the 57mm is what the LCS has so it would be nice if it could shoot straight.  The Navy certainly won’t tell us if the -2 version has gun problems so ComNavOps will keep an eye on the DOT&E reports.


Here’s hoping that the -2 version will begin to actually do something and that its gun will shoot straight!

Wednesday, August 5, 2015

LCS Module Update

GAO’s 2015 annual weapons assessment report contains some interesting tidbits about the LCS modules (1).

ASW Module

Regarding the ASW module,

“Program officials report that currently the [ASW] mission package is 5 tons too heavy to fit within the parameters reserved for the packages.”

This is probably the most mature and useful module if only because the Navy abandoned every aspect of the original module and is now using proven, existing components:  a Thales variable depth sonar, a multi-function towed array, and a standard Navy helo.  The challenge is whether they can get the components to integrate in an effective manner.  Of course, the LCS can never be an effective ASW platform due to inherent structural problems that impact ASW performance:  the vessel is not quieted and optimized for ASW and the ship’s self-noise from the water jets not only precludes a hull mounted sonar but makes the ship an acoustic beacon for miles around.  Add to that the lack of an onboard ASW weapon and you have an extremely mediocre ASW platform.  Further, the inability to operate two helos (yes, some reports credit the LCS-2 version with the ability to operate two but that is questionable due to flight deck structural weaknesses) severely limits the extent of available helo ASW coverage. 

The Navy is currently contracting with three companies for ideas on how to reduce weight in the ASW module without removing a key component.  You know the process when things go through contracts and studies.  It will be years, yet, before we see a functioning ASW module.

MCM Module

Regarding the MCM module,

“The Navy has accepted five MCM packages without demonstrating that they meet interim—or threshold—requirements and plans to accept one more in fiscal 2015.”

As we know from various reports, the MCM module has proven particularly troublesome with most, or all, of the module components failing to meet their performance criteria.  Thus, the Navy’s continued purchases of MCM modules is puzzling, to say the least.  I guess it’s analogous to buying F-35s that are not ready.

Further, the Navy just announced that the MCM module would not reach its scheduled IOC in September due to across the board reliability issues discovered during testing.

“… LCS Mission Modules Program Manager Capt. Casey Moton said Thursday at a Mine Warfare Association lunch that across-the-board reliability problems in the two start-to-finish mine clearance runs in the technical evaluation led the program to extend the evaluation for several months rather than move prematurely to IOT&E.”

Independence, LCS-2, has been testing the MCM module for how long, now?  Since the mid-70’s, it seems like.  Despite all that work, the module reliability is still unacceptable.  How bad must the reliability be, to be unacceptable to the Navy?!  They’ve accepted barely built ships and F-35’s that have no combat capability.  For them to balk, it must be really bad!

It appears that IOC will be pushed back another year or so.

ASuW Module

The Navy has dropped the plan to use the incredibly short ranged and lightweight Griffon missile in favor of the Hellfire missile.  While there is nothing wrong with the Hellfire, it is still a lightweight, short range missile.  Wiki lists the range as 550 yds out to 5 miles.  It is doubtful that range holds for a surface, vertical launch.  The effective range will likely be more like 3-4 miles.  Also, note the minimum range.  If a target gets inside 550 yds the LCS will have to engage with guns which have, thus far, proven problematic.  The 30 mm guns have had a succession of maintenance and performance issues and the 57mm gun is inaccurate above 10 kts or so due to ship vibration.  Further, the guns are optically aimed and are not linked to radar in the ship’s fire control system.

USNI News has some disturbing news even about the Hellfire missile testing. (2)

“The program office began tests on a research vessel at the end of February against ‘high-speed maneuvering targets out off the Virginia Capes.’  That testing wrapped up in June, and based on the results, the office has to do ‘some tweaking – it’s really that level, tweaking – to the missile seeker and such.”

When you factor in the military’s ridiculously positive spin on testing – every test is an unqualified success, no matter how bad (remember the fabulously successful F-35B tests on the Wasp that actually barely achieved 50% availability? – you get the sense that the Hellfire has some serious issues integrating into a vertical launch system.  “Tweaking”, with the slight negative connotation it has, must indicate that the missile failed badly!  Getting a missile that is designed to launch horizontally to launch vertically, tip over, and acquire its target, is not a trivial feat without mid-course guidance.

The missile will have to undergo another set of tests several months down the road.



Here is GAO’s summary assessment in their typically bland style.

“The systems that comprise the Navy's mission packages have yet to work successfully together to achieve results. For example, none of the mission packages for any increment have achieved interim requirements on the Independence variant, or meet its threshold requirements for either seaframe.”

Remember, also, that the IOCs that the Navy is trying so desperately to achieve are not for the desired modules but for very stripped down versions that simply allow the Navy to field a bare minimum (many would say less than minimum) capability as a PR event.  The desired modules that the Navy sold the LCS program on are many years down the road or, more likely, will never be achieved.  Go back and read the original module descriptions to see just how much the modules have been dumbed down in the quest to get something, anything, fielded.  We’ve largely forgotten the grandiose promises made and have come to believe that the current, anemic versions of the modules are what was always intended.  Nothing could be further from the truth.  As a group, the modules are an utter and colossal failure.

Perhaps the most important point in the report, though, is this one,

“The Navy continues to procure LCS seaframes, even though the sub-systems necessary to meet full mission package requirements have not yet been fully developed, demonstrated, and integrated with either seaframe class.”

The LCS’s value and effectiveness, whether you support it or not, is predicated on the performance of its modules just as a carrier’s value is based wholly on its air wing.  An LCS without an effective module is just an overgrown Coast Guard cutter, if even that.  GAO points out that the Navy is proceeding full speed with seaframe acquisition in the absence of any useful and effective module.  The only module that even theoretically exists is the ASuW module and, let’s be real, an ASuW module that consists of a couple of machine guns and a RHIB is hardly useful or effective.

Worse is the Navy’s laser like focus on seaframes.  While the modules languish, seaframe construction continues unabated.  It would be nice if the Navy put the same effort into the modules as the seaframes and it would be even nicer if the Navy would recognize the importance of the modules.  No module, no useful LCS.  If the Navy isn’t careful, half the LCS seaframes will reach their end of life without ever seeing a useful module.  What a waste that would be (assuming you don’t consider the LCS to already be a waste!).


(1)Government Accountability Office, “Defense Acquisitions – Assessments of Selected Weapon Programs”, Mar 2015, GAO-15-342SP

(2)USNI, “LCS Anti-Sub Warfare Package Too Heavy; 3 Contracts Issued For Weight Reduction Study”, Megan Eckstein, July 30, 2015