Surprisingly, two of the Navy’s MCM configured LCS have been
moved from the Middle East to a port in Malaysia despite the obvious
possibility of Iranian mines in the Strait of Hormuz. The ships were relocated about a week or so
before the US strikes began. If the
Iranians do lay mines (there are no confirmed reports yet), we’ll desperately
miss the LCS MCM capabilities … or will we?
From a Hunterbrooks website report, we learn that the LCS
MCM capability is even more problematic and limited than we already knew. The report provides information from a US
Navy briefing.[1]
As you read it, bear in mind that the summarized information
presented below is the Navy’s information, not mine. If you want to dispute anything, you’ll have
to take it up with the Navy.
By trying to be multi-mission, training time available for
mine countermeasures is being significantly reduced to support ASuW, VBSS, and
other missions.
The entire MCM package consists of
1x MH-60S Seahawk
That’s 5.5+ hrs of time before the mission even begins!
AQS-20 sonar has a habit of failing to record data which is
not detectable until after the mission, during the post-mission analysis.
CUSV still has a tendency to “runaway”, out of control.
CUSV comms are unacceptably short range requiring the LCS to
operate in or near the minefield.
Navy MCM doctrine requires a visual ID of mines and the
camera fails even in relatively clear waters.
The single CUSV crane is a single point of failure and is
prone to failure.
1x MH-60S Seahawk
- Airborne Laser Mine Detection System (ALMDS)
- mine neutralization system (underwater suicide drone)
- AN/AQS-20 side-scan and volume-search sonar
- Unmanned Influence Sweep System (UISS)
- 4+ hrs pre-mission maintenance
- 1.5 hrs post-launch sonar calibration
https://hntrbrk.com/demining-hormuz/
No comments:
Post a Comment
Comments will be moderated for posts older than 7 days in order to reduce spam.