PDA

View Full Version : AAR: Hold the Line 20 OCT 2008



Molon Labe
10-20-2007, 06:52 PM
Unfortunately we had a crash on this one, but it was fun while it lasted.

Phil (Seawolf) and I (688I) were tasked with hauling ass to a point of ocean near the GUIK Gap where a Russian SSM-heavy SAG was headed, intent on blowing away a British ASW carrier task force. Bobbyzero and Cyklop were escorting the SAG in Akula-IIs. We had a fix on the position of the SAG that was an hour old, and 2 hours to get to the point that it would be able to fire upon the Carrier group.

We started off at 2200hrs with a faint tonal on the SAG. Not wanting to be late, I went deep early and made a 10 minute sprint. A 2nd tonal showed up after that sprint, well SE of what seemed to be the PIM of the SAG. I called that a POSSUB and went deep again. After the 2nd sprint, I noticed a significant signal increase in the POSSUB while I was watching it, which indicated an increase in speed. The POSSUB became a sprinting PROSUB. At 2240 Phil and I came to comms to share our solutions; he too had the same contact off the PIM, so at this point I was pretty sure I'd spotted Cyklop sprinting in the surface duct.

At this point, it appeared that Cyklop was in pretty close to the formation... perhaps looking for me to get into something like the "sweet spot" TLAM spoke of in the Kilo guide. A collapsing defense meant I had more time to get in close, so I went deep for another sprint. Before putting the speed on, I detected a deep tonal to the north, another PROSUB, probably BobbyZero. I put out a UUV (to provide TIW alerts in case I was wrong about the collapsing D) and got ready to sprint again, but then noticed another deep tonal, also north. Oops. That guy I thought was Cyklop was just an escort. And the place Cyklop is in is not in position to block me. This changes things. I had meant to sneak in close on Cyklop and torp him, then send two torps after the SAG, forcing it to turn towards Phil at best, or at worst away from the goal line and buying us some time. But it seemed now that the "back door was open," so I could take a serious shot at the objective cruisers.

The sprint part of the plan didn't change, so I went got deep and put on the speed for a short sprint. After that sprint, we had about 45 minutes to the goal line. I was about 18nm away from that spot...not at close as I wanted to be. Active returns started lighting everything up, and the escorts were getting dangerously close to being inside of detection range. I kept a close eye on the two subs to the north and tried to stay on the opposite side of the layer. But this close to the goal line, they could afford to get slow and dangle below the layer from above, so that wasn't much of a guarantee. At 30 minutes to goal, it was time to strike. I still wasn't as close as I wanted to be; the nearest sub looked about 10-12nm out to the NNW, and the cruisers were at least 14nm NE. Both of them are far enough out to outrun the shots... but I decided to go deep and fire under the layer and hope for the best. Even if the sub just ran, he would be neutralized for the time--and would be running towards Phil, and if the SAG ran it would just be like the old plan, so that's still not bad.

The near sub crossed the layer almost immediately after I fired, so he definitely heard it. So much for surprise. I sprinted in anticipation of missile shots. I was surprised that after a few minutes, none had been fired. I slowed down and tried to keep my track on the target sub. My torps started enabling. The one on the sub wasn't finding anything, but the two fired at the crusiers were going for blood. I resteered the sub torp as best I could and preenabled. About this time, I realized I had been wrong about Cyklop again. I was now getting tonals behind me, to the west, suggesting that I had overrun him. I would have tried to think about it a bit to figure out where the correct contact would have been at the time, but now the missiles were falling, and the bearing lines on those weapons from the UUV were pointed right at me.:eek:

I set up a two decoy drop leading SE and turned north behind it, baiting the nearest torp to miss me to the right, and then turn to the right when it lost the track. Reloaded decoys, turned ENE to clear. Lost two torp wires...somebody's day just got ruined...reloaded those tubes. Re-enabled the sub torp. New torps in the water to the north, they looked a little far but not far enough. Drop shallow decoys, turned ESE. Hopefully they'll be baited shallow while I'm deep. Oh shit, I'm not deep, I'm still above the layer. Why am I still above the layer?! Dumbass! :slap: Active reports from the west show acquisition...I need more decoys. Lost the wire and the 3rd torp--guess that Akula wasn't too far after all! Reload torp, still no decoys. Check position of torps... not looking good...... and I'm hit.

And then two minutes later, DW crashes.:gdamnit:


My first two torps hit and sunk a Slava, one of the 3 objective ships. The other torp hit Bobbyzero, who was on Phil's side of the SAG, not mine. Cyklop, who was on my side, was well off on the left flank of the SAG. I had only tagged his mirror contact during my approach.:confused: Whoops. All in all, I think I had 6 SUB/ASROCs shot at me, not including what I'm guessing were 3-4 Stallions Cyklop tried to fire from above 50m. (Good to know I"m not the only player that's rusty!) It was a pair of -27s from him that were the first torps to threaten me; the first of the pair acquired me and was the one I spoofed in the beginning of the evasion sequence. This MPT-1UE completed its second circle, went through the decoy field again, and reacquired at a relatively long range, and was slowly chasing me down the whole time I was reacting to the Silexes from the Udaloy (the other TIWs) and managing my torps. So it ended up being the first of the 6 torps intended for me that ended up hitting me. Nice job, Cyklop.

The crash was at a really bad time for Phil... The SAG was coming about after failing to escape my torp salvo, and with Bobby out of Phil's way, the SAG was pretty much at his mercy. Damn DW crashes!:gdamnit:

Phil21
10-20-2007, 09:47 PM
The crash was at a really bad time for Phil... The SAG was coming about after failing to escape my torp salvo, and with Bobby out of Phil's way, the SAG was pretty much at his mercy. Damn DW crashes!:gdamnit:

I just went deep trying to mask my shots, and then just when a full salvo was about to enter the whole madness...DW crashed. But it was very thrilling until the end.

Now the story from my point of view:
After starting on the northern side of the SAGs course i had to turn to keep it out of my baffles. I went to the north, slowly listening for any escort or sub to sprint ahead to intercept us. After a while i had two groups of 50hz lines, but unfortunatly my angle to them was that bad i couldn't the different contacts in each group. After linkung information with Molon Labe, i decided to sprint down south/south-east to get in a better position.

After a while a faint 165hz line showed up, so i could at least identify an escort. As i continued to close distance, Solutions were made for some of the different contacts (one possub, one or two escorts and one ship which showed up as a cruiser later). The image was about to become clearer, when i got the info that the SAG was only about 30min from its firingpoint away. ML started his attack and within minutes my sonar was full of sprinting ships and torps (with alot of TIWs)...complete madness for my TMA, but after a few minutes i managed to reorganize.

But then i got the info that ML was hit taking a sub and something big with him. I was just about going below the layer to mask my torps when loud explosions washed my sonar out. This was the time i decided to fire my package: 4 MK48 were launched at what seemed to be a second sub and a cruiser and two more were waiting in their tubes for the second salvo.

Unfortunatly DW crashed moments later, but nontheless it was really entertaining! We have to repeat this in a while...

Cyklop
10-22-2007, 05:41 AM
Thanks for sharing your impressions.
Now let me tell the story seem from my point of view.

We (Bobby and I) started quite far away from each other, about 50 kms I guess. I expected from the briefing (sea state 5, sandy bottom) that the detection range for a 688i running slow would be not more than 10 NMs in good conditions. Since there was a big gap between Bobby and me we decided to reduce the distance. What we saw via the data link from our SAG was three friendly ASW helicoptes searching the are in front of us.

We kept sprinting and drifting, looking above and below the layer. All we could see were two whales located more or less in the area where the enemy was expected to show.

Suddenly I had a faint 60 Hz line from the west declared POSSUB. The line disappeared after a minute, but this was the first warning. I kept approaching the area, trying to reacquire the contact. Then I heard TIWs from his bearing. At that point I was below the layer and no torpedo signatures were available on sonar. I didn't know who had fired. We thought that maybe one of our helicopters had attacked the enemy or the whales.

When I came above the layer, I classified the torpedoes as MK48s, so there was no doubt. I prepared and set up three of my SS-N-27 ASW torpedoes, slowed down to 5 kts and ordered "launch external tubes 1,2,3". And what?
This is the part where MolonLabe is right about not only him being rusty - I was 50 m too deep for a successful launch. I decided to fire two more from the correct depth this time, which I did a minute or two later.
It turned out my solution was quite accurate, as the primary torpedo entered the water very close behind MolonLabe's 688i. From that moment on I just kept watching. I heard several TIWs (friendly units firing at MolonLabe) and decoys very close to my torpedoe. Then "Conn Sonar, explosion on the bearing of S06" and MolonLabe was gone. So was Bobby, who went to the bottom in the meantime. I had no idea of Phil lurking in the depths to the NW, so all I could do was come to comms depth and try to enhance my situational awareness with the datalink tracks. But this is when the DW crashed on the host's PC and the good game was over.

Thanks again and hope for more next time!