File that under "oops"

[Prophet]

Today I thought I'd play the Kilo demo for fun. And it was fun, and then some.

It started off pretty standard, I found the O.H. Perry and the cargo ship right away, along with one lone freighter somewhere between myself and the convoy. No big deal, I locked down solutions on the cargo ship as well as the Perry just so I could keep tabs on it on the nav map. Then I launched my torpedo, but I accidentally flooded my tubes right as the Perry's sonar ping passed me, and somehow they were able to get a solution on me in about 10 seconds and launch one of their torpedoes back. No matter, I set an evasion course and drop countermeasures.

Now my torpedo is on a pretty constant 184 bearing, and the Perry's torpedo initially came from a bearing of 208. After about a minute I start hearing the Perry torpedo's active pings, which I thought was strange, to have the torpedo go active so quickly. After another minute all goes quiet, so I assume my countermeasures fooled the torpedo, even though I was some 7-8 KM away from the torpedo itself...is that possible?

Anyway, suddenly I get "Loud explosion bearing 168." I'm immediately confused, because I know it's not my torpedo. I look at the nav map, and it seems the one lone freighter exploded...because the Perry's torpedo had struck it. Hilarious...of course I killed the cargo ship as well, so an all around good day for me as I'm now just a ghost in the sea, and a completely putrid day for the crew of the Perry. I imagine their AAR for the day will look something like this:

FIRED UPON UNKNOWN HOSTILE SSN...SUNK SAME...UNFORTUNATELY THE GISELA TIDE WAS LOST DUE TO A MAJOR UNEXPECTED STORM...NO INFORMATION REGARDING MISSING FREIGHTER IN VICINITY OF SAKHALIN

On a side note, is there a more accurate method of finding range to a target? I'm currently using alternating zigzags using sonar, but I'm open to better suggestion.