Advertisements

Quick Battle – Parameters

  • Starting Separation: 30 nm.
  • Adversary EMCON State: Sonars passive
  • Local Time: Morning (0600)
  • Engagement takes place in: Deep, warm water in the South China Sea
  • Weather: Clear, very light clouds, wind state 1, avg. temp. 14C.
*Characteristics from the game database

Video

Comparison of Main Weapons

*Characteristics from the game database

Statistics

Notes from the message log

*ZULU times in parenthesis.

  1. 6 May 2020 (0829) – [Player] New contact! Designated GOBLIN – Detected by DDG 103 Truxtun [Arleigh Burke Flight IIA] [Sensors: AN/SQS-53C(V)1] at 52deg – 28.6nm
  2. (0913) – [OPFOR] Contact: DDG 103 Truxtun [Arleigh Burke Flight IIA] has been positively identified as: DDG 103 Truxtun [Arleigh Burke Flight IIA] – Determined as: Hostile (ID by: S 119 Astute [Sensor: Type 2065 [Type 2076 Suite]] at Estimated 15 nm)
  3. (0929) – [OPFOR] New contact! Designated TORPEDO #9 – Detected by S 119 Astute [Sensors: Type 2065 [Type 2076 Suite]] at 110deg – Estimated 17nm
  4. (0929) – [OPFOR] Contact: Torpedo #9 has been classified as: Mk54 LHT Mod 0 – Determined as: Hostile (Classification by: S 119 Astute [Sensor: Type 2079 [Type 2076 Suite]] at Estimated 0 nm)
  5. (0930) – Decoy (SCAD 102; Tech: Early 2000s) from S 119 Astute is attempting to seduce sensor: Torpedo Seeker (Tech: Late 2000s)(Guiding weapon: Mk54 LHT Mod 0). Final probability: 25%. Result: 35 – FAILURE
  6. (0930) – Decoy (SCAD 200; Tech: Early 2000s) from S 119 Astute is attempting to seduce sensor: Torpedo Seeker (Tech: Late 2000s)(Guiding weapon: Mk54 LHT Mod 0). Final probability: 25%. Result: 88 – FAILURE
  7. (0930) – Torpedo Mk54 LHT Mod 0 is attacking S 119 Astute with a base PH of 85%. Final PH: 85%. Result: 55 – HIT
  8. (0930) – Weapon: Mk54 LHT Mod 0 has impacted S 119 Astute.
  9. (0930) – [OPFOR] S 119 Astute has been destroyed!

Evaluation

I started the Quick Battle (QB) by setting a patrol square (in retrospect, I should’ve made it a circle) of 30nm because that was the starting separation between the forces and I knew the enemy submarine would be somewhere in that area.

I’ve tried ASW QBs where the submarine began at 5nm away from the player’s ship, but the enemy sub immediately ID’d, and sank it. So, to give me some degree of fair chance and challenge at finding it, I set the starting separation parameters at 30nm.

Bear in mind that I’m not an expert at any particular type of warfare. Submarines are basically the original stealth vessel on the sea and they operate in an environment that I’m very unfamiliar with. Due to their inherent stealth capabilities and the undersea environment, subs are very difficult to detect. Note that the QB began on 5 May at 1400 ZULU and we didn’t locate Astute until 6 May at 0829. Over 18 hours later.

Again, given that the doctrine was set for FREE fire on any submerged contact, Truxton fired a RUM-139C ASROC at the contact once it was in range of its underwater weapons. Astute attempted to decoy the torpedo, but failed, and was sunk.

A few things to note are that one, Astute was detected by Truxton‘s hull sonar in a convergence zone at 28.6 nm and not by one of the sonobuoys. Secondly, Astute had already positively ID’d Truxton at ~15 nm, but apparently didn’t get within range to fire a torpedo before Truxton‘s ASROC went flying. The entire engagement, from Truxton making contact to the sinking of Astute, lasted only 1 hour and only one weapon (apart from Astute‘s decoys) was fired.

Alternatives

  • Truxton could’ve been sunk by Astute.
  • Astute could’ve been detected by the dropped sonobuoys instead of by Truxton‘s sonar.
  • The Seahawk helo could’ve prosecuted the attack on Astute with her air-dropped torpedoes.
Advertisements