VertRep

VertRep
Showing posts with label War at Sea. Show all posts
Showing posts with label War at Sea. Show all posts

Tuesday, November 12, 2013

War at Sea: Missile or Torpedo Firing Unmanned Surface Vessels

USV's that fire missiles must be part of the littoral or near coastal sea battle force . . . from about a year ago, US Navy tests first 11-meter missile-firing sea drone (video):

Now, a little bigger, please. Gimme a quad set of such armed USVs operating from a mother ship and I could make life miserable for someone. here. Here's part of the section on weapons for the USV: Oh, yes, the U.S. Navy has a USV "Master Plan"
• Torpedoes - Under consideration within the analysis were: CVLWT, Mk 54 and Mk 48 (ADCAP) Results: Torpedoes provide dual-use capability (ASW, SUW). Torpedoes could also conceivably have a “dial-a-blast” effect (detonate short of target to vary “shock” factor), but this option is not under development and is not strictly required for this mission to be effective.
• Missiles – Under consideration within the analysis were: Hellfire, NLOS-LS (NetFires), and Brimstone. Missile system capabilities that would be desired include: inertial navigation system, fixed box launcher (reconfigurable/modular), sealed units (fire-through end cap), network-able, discrimination achieved via multiple sensor sources, maritime environment operations capable ("marinized"). Results: Small low-cost missiles would be effective, but not at much greater range than larger torpedoes. Though more capable missile systems (e. g., longer standoff ranges, bigger warheads), they are more appropriately installed on and launched from the host ship. For the sizes of missiles reasonable for USV applications, there is little advantage to USV launch. In summary, the weapons of choice in this scenario appear to be torpedoes, since in the sizes capable of being carried on USVs, they alone have the range to engage the enemy outside the threat's counter-boat weapon range. There is also a much greater chance of the target being unalerted by a torpedo attack than a gun or missile attack.
NLOS-LS is toast, so that leaves smaller systems or making the USVs big enough to handle something larger than Hellfire or Brimstone. UPDATE: A very recent Rand report on U.S. Navy Employment Options for UNMANNED SURFACE VEHICLES (USVs) (PDF). Hat tip: Naval Drones, who notes:
The study analyzed the suitability of USVs for 62 different naval missions (yes, there are that many). USVs were compared to other platforms, including manned, and unmanned (UUVs and UAVs). According to the report, USVs are more suitable than other platforms in missions requiring longer endurance, higher power availability for payloads, and the ability to interface “cross domain” sensors and with other platforms above, on, and below the water.

Tuesday, June 05, 2012

How to Win a Sea Battle

A slightly updated re-posting from 2009 as part of the 70th Anniversary of the Battle of Midway:

In preparing for a major sea battle, make sure of the following:
  1. Have your major surface combatants destroyed or seriously damaged and unavailable for use.
  2. Make sure the enemy has 4 aircraft carriers and some big battleships headed for you.
  3. Make sure you are outnumbered in aircraft carriers by 4 to 3.
  4. Have 1 of your 3 aircraft carriers severely damaged and limp into port unable to support flight operations.
  5. Have only a vague idea where the enemy fleet might be.
  6. Arrange to have your most aggressive, experienced aviator admiral come down with some sort of skin infection that puts him in a hospital bed, unavailable for duty.
  7. Replace him with a non-aviator admiral just in time for what you know has to be a battle largely fought by carrier aircraft. See #1.
  8. Have him hatch a scheme that hides the fleet way off to the north of where you think the enemy are headed. Just in case they aren't because your fleet is all that stands as a defensive barrier between Hawaii and the U.S. mainland.
  9. Make sure the whole battle will turn on which fleet spots the other fleet first.
  10. Do hasty repairs on that banged up carrier and send her, after 24 hours out to sea with civilian workers to try and do more repairs underway.
  11. Don't have enough patrol aircraft out looking for the enemy fleet so that your coverage of possible avenues of approach is spotty.
  12. Make sure your torpedo attack planes are slow and carry torpedoes that can only o be dropped after a long, slow low level flight toward enemy ships.
  13. When you spot the enemy fleet, make sure it is at the maximum range of your aircraft.
  14. Make sure your tactics include the arrival of the low slow torpedo bombers and the dive bombers and fighters all at the same time, otherwise the torpedo bombers will be "sitting ducks."
  15. Make sure that the tactic described in #12 does not work out at all. Lose nearly all your torpedo planes early in the engagement.
  16. Arrange for an enemy sub to end up in the middle of your formation where it will eventually sink one of your carriers.
  17. Have ground based aircraft from Midway Island find the enemy fleet and carry the fight to him as well as they can.
  18. Have this fight cause the enemy fleet to be in the act of rearming reserve aircraft when your main air attack starts and fouling the deck with ordnance.
  19. Have the enemy distracted by the low and slow torpedo bombers while your dive bombers arrive to do their work.
  20. Scatter your aircraft so that instead of all arriving at once they appear to come in waves.
  21. Have a stubborn squadron leader who, instead of turning back with low fuel, kept searching until the enemy fleet was spotted and attacked.
  22. Have the non-aviator admiral make the decision to head his carriers toward the enemy fleet so he could cycle his aircraft faster.
  23. Sink all 4 enemy carriers, while only losing 1.
  24. Completely halt the enemy attack and turn the tide of the war.
  25. Be very, very lucky.
70 years ago. The Battle of Midway.

Art from the Navy Art Collection

Tuesday, August 09, 2011

Guadalcanal Days 2 and 3: The Battle of Savo Island

 UPDATE: Let's do this like historians - up to this addition, I've given you the result and the lessons learned, but left out an explanation of how things came to pass. Start with the fact that the U.S. Navy and Marines caught the Japanese by surprise and invaded the lightly held (maybe 800 Japanese) but vital island of Guadalcanal on 7 August 1942. See my previous post and the links therein covering how this was accomplished and why here. Now, let's get into RADM Morison's The Two Ocean War as he sets the scene:
Early in the morning of 7 August news of the American landings reached Vice Admiral Mikawa at Rabaul. His decision was prompt and intelligent - to send reinforements to the Tulagi-Guadacanal garrison, and to assemble a task group to attack the American ships unloading there. {Note by E1: The ship carrying the troops is sunk by an American submarine around midnight on 8 August. It's the task force that is the focus of the battle]
***
Mikawa's naval reaction is a very different story. One hour after receiving the bad news from Tulagi, he began collecting ... a task group to attack the American Expeditionary Force. It was a "scratch team," the ships had never trained together before, but it proved to be good enough for the task in hand. Heavy cruisers Chokai (flagship), Aoba, Kako, Kinugasa and Furutaka, light cruisers Tenryu and Yubari and one destroyer, Yunagi, made rendezvous in St.George Channel around 1900 August 7 and started hell-bent for Guadalcanal. Mikawa's battle plan . . . was to enter Ironbottom Sound in the small hours of the 9th, strike the warships guarding the expeditionary force, shoot up the unloading transports, and retire. An excellent plan; but the chances of detection were great, as the striking force had to steam in full daylight down the "Slot" between the central Solomon Islands before entering the cover of darkness.

Owing to a series of blunders on our side, [5/7/2013 UPDATE NOTE: AN INACCURATE ALLEGATION BY MORISON HAS BEEN TOTALLY REFUTED BY A NUMBER OF SOURCES PLEASE SEE COMMENTS BELOW - THIS POST HAS BEEN EDITED TO REFLECT WHAT IS NOW KNOWN]  . . . one (or more) sighting(s) of Mikawa's force that day (was/were mishandled) . . .  Admiral Turner did not receive it (them) until over eight hours had passed. (Further what was reported evidently was miscontrued) On that basis (i.e. the misunderstanding of what was seen) Turner made the bad guess that the Japanese were not coming through that night, but intended to set up a seaplane bases at Santa Isabel Island, some 150 miles from Savo, and attack later. [As indicated here below and in other places, Admiral Turner and/or his staff got it wrong in many, many ways.]

Dogmatically deciding what the enemy would do, instead of considering what he could or might do, was not Turner's only mistake on that fatal night. He allowed his fighting ships to be divided into three separate forces to guard three possible sea approaches by the enemy. Rear Admiral Norman Scott with two light cruisers and two destroyers patrolled the transport area between Tulugi and Guadalcanal, and never got into the battle.
***[Note by E1: Morison lays out the other groups, commanded by Royal Navy Rear Victor Crutchley, VC - but coordination among his ships was - uh - lacking]

Turner was so certain that the enemy would not attack that night he made the further mistake of summoning Crutchley, in Australia, to a conference on board his flagship . . . some 20 miles away . . . This action of Turner's stemmed from the worst of all blunders that night: Admiral Fletcher's decision to retire his three-carrier task force from covering position, depriving the landing force of air covernext day. **** He commenced this withdrawal at about 1810 August 8 without consulting Turner, who was below him in the chain of command. That was why Turner felt he had to confer with Crutchley and Vandegrift {Marine commander] to decide whether the partially unloaded transports should depart that night, or risk more Japanese air attack without air protection. Consequently, cruiser Australia and the O.T.C. [Officer in Tactical Command] were not on hand when badly needed, and the depleted cruiser group south of Savo Island was commanded by Captain Bode of Chicago, who acted as if dazed.
And then the confusion began.

From HyperWar: The Battle of Savo Island [ONI Combat Narrative], a discussion of what Samuel Eliot Morison called, ". . . [P]robably the worst defeat ever inflicted on the United States Navy in a fair fight":
The disposition of our cruisers and the remaining destroyers was governed by "Special Instructions to the Screening Group," issued by Rear Admiral V. A. C. Crutchley, R. N., commander of the escort groups and second in command of the Amphibious Forces. To protect the disembarkation area from attack from the eastward, the American San Juan and the Australian Hobart, both light cruisers, were assigned to the area east of longitude 160° 04' E., guarding Lengo and Sealark Channels. They were screened by the destroyers Monssen and Buchanan. At 1850 these ships began their patrol at 15 knots on courses 000° and 180° between Guadalcanal and the Tulagi area.

As a precaution against surprise from the northwest, two destroyers were assigned to radar guard and antisubmarine patrol beyond Savo Island. The Ralph Talbot was north of the island, patrolling between positions 08° 59' S., 159° 55' E. and 09° 01' S., 159° 49' E. The Blue was stationed west of the island between positions 09° 05' S., 159° 42' E.4 and 09° 09' S., 159° 37' E., patrolling on courses 051° and 231° at 12 knots.

The area inside Savo Island, between Guadalcanal and Florida, was divided into two patrol districts by a line drawn 125° T. from the center of Savo. It was upon the vessels patrolling these sectors that the Japanese raid was to fall. The area to the north of this line was assigned to the heavy cruisers Vincennes, Astoria, and Quincy, screened by the Helm and Wilson. The last-named replaced the Jarvis, which had been damaged by a torpedo during the day's air attack. This group was patrolling at a speed of 10 knots on a square, the center of which lay approximately midway between Savo and the western end of Florida Island. At midnight it turned onto course 045° T. and was to make a change of 90° to the right approximately every half hour.

The area to the south of the line was covered by the Chicago and H. M. A. S. Canberra, screened by the Patterson and Bagley. H. M. A. S. Australia was the flag and lead ship of this group, but at the time of the action she was absent, having taken Admiral Crutchley to the conference aboard the McCawley. Capt. Howard D. Bode of the Chicago was left in command of the group, although the Canberra ahead of his ship acted as guide. The group was steering various courses in a general northwest-southeast line--the base patrol course was 305°-125° T.--reversing course approximately every hour.

Admiral Crutchley's instructions were that in case of a night attack each cruiser group was to act independently, but was to support the other as required. In addition to the Melbourne warning, a dispatch had been received indicating that enemy submarines were in the area, and night orders placed emphasis on alertness and the necessity for keeping a sharp all-around lookout. The destroyers were to shadow unknown vessels, disseminate information and illuminate targets as needed. It was provided that if they should be ordered to form a striking force, all destroyers of Squadron FOUR except the Blue and Talbot were to concentrate 5 miles northwest of Savo Island. This arrangement was to cause some confusion during the battle.
and
"The fact must be faced that we had an adequate force placed with the very purpose of repelling surface attack and when that surface attack was made, it destroyed our force," said Admiral Crutchley. After full allowance for the element of surprise and for the fact that the attacker at night enjoys an immense advantage, there remain many questions about the action which cannot be answered.
***
The redeeming feature of the battle was the splendid performance of our officers and men. They had been on the alert for days and had had about 48 hours of continuous, active operations immediately before the battle. In spite of this, their conduct under the most trying circumstances was beyond praise, and they made it, in the happy phrase of one of our officers, "a night in which heroism was commonplace."
HMAS Canberra sinking

Instead of repeating the ONI Combat Narrative here, please go read the Hyperwar link. It is well worth your time.

You can also find a report in the USNI Solomons Campaign series at Execution at Savo Island by CDR Bill Ballard:
There is no shortage of lessons learned from Savo Island.  To pull out just a few of the big ones:

Communication between supporting/-ed commanders: With the entire operation in its infancy, URR’s lesson of streamlined dissemination and obtaining of INTEL and aerial reconnaissance information is still applicable.  Allied shore-based reconnaissance aircraft were either under the command of COMSOPAC or COMSOWESPAC, with little effective communication or coordination.  COMSOWESPAC aircraft detected (and mis-identified) Mikawa’s force the morning of the 8th; by the time it reached CTF 62 it was too late to send any more aircraft to either further identify or attack them.


Capability vs. Intent: Be ready for what your enemy CAN do to you, not what you think your enemy WILL do to you.  Taking two seaplane tenders out of the mis-identified formation, there were still five ships that were capable of reaching Savo that night.  Taking this into account, had some or all of TG 62.6 been in Condition I through the night, with a real plan or set of PPR’s in place…


Trusting your Technology: Only if you understand its limitations.  On a tactical level this battle was less a case of visually targeted torpedoes defeating RADAR-directed gunnery and more a case of over-reliance on incorrectly employed RADAR leading to the complete surprise of TG 62.6.  Even though in training BLUE and RALPH TALBOT exhibited RADAR detection ranges greater than Japanese visual detection ranges, the long wave SC RADAR’s performance suffered terribly near land.  Additionally, their assigned search tracks at times left 20 mile gaps between the two ships. (Bates, pg. 350)  Interestingly, the most capable Allied RADAR, the SG RADAR, was aboard SAN JUAN and never saw action.  One wonders what the outcome could have been if, between Crutchley, Scott and their staffs, they had decided to put SAN JUAN in one of the picket stations.


Technology vs. Tactics, Training and Procedures (TTP): The action at Savo commenced with both sides well within the effective range of their preferred weapons.  This is the range at which training pays off.  Simply put: the IJN had trained; the USN hadn’t.  Of the Allied ships, only ASTORIA had conducted any recent night target practice, and it had been at least eight months (more than likely indefinite in the case of QUINCY and VINCENNES, recently arrived from the Atlantic) since any other cruiser had conducted either night target exercises or a night battle problem. (Bates, pg. 356)

US Navy losses: From here:
Battle of Savo Island
Navy 936 dead 11 wounded
Marine 33 dead
UPDATE: Added some additional paragraphs from the ONI report to set some background.

Sunday, June 06, 2010

Iran: Revolutionary Guard Navy Says It's Ready to Escort Ships to Gaza

Report here from the Tehran Times:
The Islamic Revolution Guards Corps Navy is totally prepared to escort Gaza-bound aid ships to protect them against Israeli attacks, the Supreme Leader’s representative in the IRGC Navy has announced.

“Enemies should be met head-on through a spontaneous international movement, and we should foil their evil plots,” Hojjatoleslam Ali Shirazi told the Mehr News Agency on Sunday.

“The Islamic Revolution Guards Corps Navy is ready to escort the peace and freedom convoys that carry humanitarian assistance for the defenseless and oppressed people of Gaza with all its strength,” he added.

The IRGC follows Supreme Leader of the Islamic Revolution Ayatollah Seyyed Ali Khamenei’s orders, and if he issues an order in this regard, the IRGC Navy will mobilize all its forces to provide security for Gaza-bound aid convoys, he stated.

Presumably Israel is prepared to sink all the IRGC Navy ships that show up. It's a long transit from Iran to Israel. The blue arrow points to Israel, the yellow to Iran.

Some in Iran seem to feel this whole Gaza shipping hullabaloo is a sign of Israel's demise, as set out in this diatribe:
Iranian President Mahmoud Ahmadinejad said that the act of the "cancerous tumor," i.e. Israel, against the Gaza flotilla denotes the beginning of the end of the Israeli regime, and attests to its weakness. In a speech in the city of Ilam, in western Iran, he said that Israel had attacked the ship with a missile fired from an airplane, killing 20.
Ahmadinejad warned Israel's supporters in the region and its allies to stop their support for this "professional assassin" regime, because their support had made them collaborators in the Zionists' crimes. He said that Israel "should be aware that this [action] will lead to its end," and added, "Someone asked me why I no longer say Israel must be torn down... I said because there is no (longer a) need to say [this] – as this regime is already in the process of being destroyed."
Ahmadinejad added: "The absolute track of history is the elimination of oppression and arrogance. Accordingly, it is best that the supporters of the Zionist regime distance themselves from it. This is friendly advice. History shows that if they do not take this advice, the force of the nations will put them in their place."