AAR Viktorius

[Flankerk]

AAR Viktorius.

This is a DB2000 scenario written by Mike set over two days. Essentially two SSBN’s are leaving Faslane and subsurface Soviet forces are to locate and sink them.
The scenario is set in 11/8/86 at 18.00 start. This test was played through with version 3.7

At scenario start I had the rough patrol area marked at which an interception of the submarines might take place, this roughly forming a channel headed North Westerly from the Faslane area.

I had two submarines to the North and East of that channel and some way out, K264, a Victor III and K371 a Victor II.

Closer to the channel and generally to the South and West of it were three submarines, two Victor III’s K299 and K244 with a less capable Victor II K467.

At game start initially all subs spent some time at creep to check their surrounds, then soon afterwards headed at cruise speed for the central channel area. Once they entered the channel they then dropped to creep speed again.

21.59 K371 was briefly actively pinged by a helicopter contact. Contact lost and K371 cleared the area.

22.09 A Broadsword type located at some speed to the North of K244, considered to be at considerable range.

22.16 Some considerable time after the last active helicopter ping, K371 receives another pinging and a torpedo dropped astern, the sub being lost.

22.23 Leander contact, again some considerable distance to the North of K244. Presumed grouped with the Broadsword, appearing to be making high speed in the general direction of the search area.

23.37 Contact to South and East of K264, soon classified to be Ark Royal. However zone of uncertainty was massive and never was even vaguely localised.

2.51 on the 12th K467 picks up a faint subsurface contact to North East. Speed dropped to 5 knots.

2.55 Contact classed as a Swiftsure at 10 knots.

3.07 K 264, thought to be undetected is struck by a torpedo and lost. All submarines operating to the Eastern side now lost.

5.49 K 467 now at creep speed picks up a Resolution class contact due North.

5.51 Resolution also making ten knots, no way for K 467 to intercept therefore speed back to cruise to close range.

6.59 K 467 drops to creep speed and reacquires Resolution some distance away, back to cruise 15 knots.

7.14 Speed back to creep assuming now closing on resolution. Completely correct as immediately detect an incoming Tigerfish torpedo ! Out of range for a return shot. Torpedo evaded but takes K 467 well out of any possible intercept position.

9.07 K 244 now in range, fires a USET-80 at Resolution.

9.14 Torpedo misses so a second is fired.

9.20 Resolution class struck and sinking.

9.21 K 467 detects a close subsurface contact, thought to be at or about 6NM.

9.31 Contact classed as Swiftsure.

10.13 Swiftsure contact becomes very vague, K 467 drops speed and awaits a firmer contact. This comes soon after with a Tigerfish launch. SET 65M counter fired, K 467 evades at flank speed..

10.19 Swiftsure struck and sunk, Tigerfish lost.

10.54 Unknown subsurface contact to East of K 467.

10.58 Classified as Resolution class.

11.10 Resolution heading directly for K 467 at ten knots. K 467 at very low speed.

11.52 No firm contact with Resolution until torpedo launch. K 467 goes active .

11.53 Resolution is at 1 NM, SET 65M fired.

11.57 Both torpedoes miss, both submarines fire again. K 467 attempts to evade at flank speed.

12.04 K 467 struck by Tigerfish and lost. Not known if the SET 65M hit.

12.59 It clearly didn’t…… close contact detected by K 244 at about 4NM. USET-80 fired.

13.06 Resolution sinking.

13.35 Victory Conditions trigger.

The sonar values and close torpedo ranges used in DB2000 are effective in making this a creepy close range encounter, and it is often not possible to be sure whether you are winning the scenario or not. Helicopters from Ark Royal probably finished off those submarines in the Eastern section yet we never really knew where that group was and using the periscope didn’t appeal!
A nicely balanced scenario always with something going on to occupy you. The scenario also plays at a good pace. Nice to see the AI offering a real threat, somehow they always manage to in any done by Mike……
The scenario looks to operate fine in 3.7 and the sunk submarines all were registered in the game report.