RE: Death to Corsiars!
Posted: Thu Dec 09, 2010 6:47 pm
Jan. 17, 1944
A lot going on this turn. In no particular order:
The Kasagi came out of drydock today. It is joined by the Zuikaku and Junyo which also recently came out of the yards. These three carriers will now sail south to Ulithi to join the rest of the KB, although the Junyo will then be split off to join the slow KB down in the DEI. So now everyone is all done repairing from the actions around Ponape and from some sub attacks (both Junyo and Kasagi were the victims of sub attacks).
The airfield at Truk was almost totally repaired today. At the end of yesterday, it had 29 runway damage and 25 service damage. Today there was only 5 service damage left. Wow! [X(] [&o] I have never seen my runways repaired that quickly. I guess 250 engineers will do that. There was no follow up attack today, for obvious reasons. [;)]
The raid on the Darwin convoy was a resounding success. First, we encountered the Dutch sub KXVIII and put two solid hits on it and 10 damaging near misses.
Next, we ran into the PTs guarding the port. They did not cause a problem with visibility at 12k yards and after PT-112 was obliterated by a 20cm hit, the other 4 PTs decided to high-tail it.
Then it was on to the main event, the destruction of the allied supply convoy. Apparently, witpqs gambled that I would not go straight for Darwin since last time I went for a different hex. Or maybe he though I was up to something at Moa besides staging for a surface raid. Whatever the case may be, we encountered and sank 5 xAKs and a DE. Our spotting report from yesterday was amazingly accurate, reporting 7 xAKs.
Allied Ships
DE Encounter, Shell hits 7, and is sunk
xAK Empire Hamble, Shell hits 5, Torpedo hits 1, and is sunk
xAK Fatshan, Shell hits 6, Torpedo hits 2, and is sunk
xAK Hanyang, Shell hits 9, and is sunk
xAK Ping Wo, Shell hits 4, Torpedo hits 2, and is sunk
xAK Taiyuan, Shell hits 3, Torpedo hits 1, and is sunk
xAK Wulin, Shell hits 4, Torpedo hits 2, and is sunk
The bombardment was the one part of the operation that could have gone better. I forgot to set any of my float planes to recon, so we didn't have any spotters. As a result, damage to the airfield was minimal:
Japanese Ships
CA Kako
CA Kinugasa
CA Haguro
CA Myoko
CL Kuma
DD Yuzuki
DD Mochizuki
DD Mikazuki
DD Akebono
E Asagao
Allied ground losses:
11 casualties reported
Squads: 0 destroyed, 0 disabled
Non Combat: 0 destroyed, 2 disabled
Engineers: 0 destroyed, 0 disabled
Guns lost 1 (1 destroyed, 0 disabled)
Airbase hits 3
Runway hits 4
Finally, on the way out, the cruiser TF encountered the xAK Caithness which apparently was able to get underway before our bombardment force arrived. The Caithness is now slated to become a popular diving attraction after the war.
Over in China things look like they are about to heat up.
My troops advancing on Changsa/Henyang are making good progress - they have only 8 miles to go which they should cover in 2-3 days at most. Once they enter the target hex, witpqs will know something is up and start to react. I have already set another 5 divisions to march towards Henyang and 5 more are ready to move on Changsa.
So far so good. But witpqs has thrown quite a monkey wrench into my plans. Earlier, I pulled an HQ and an artillery unit out of Nanyang. Perhaps witpqs noticed this movement, perhaps he noticed the smaller number of units, or perhaps he has had an offensive planned for a while. But when I checked today I was chagrined to see 30 units sitting in the woods next to Nanyang. Previously, there were only 15 units there, the units I had kicked out of Nanyang when I captured the place. When these new units arrived I am not sure since I am not religious about checking in on the Chinese situation. At any rate, it is obvious a Chinese offensive is immanent.
I have already started three divisions marching towards Nanyang as reinforcements. I doubt they will arrive in time, but I need to try. These are all the reserves I can muster in the north China theater. My other reserves are all advancing on Changsa/Henyang!
So now we have an interesting situation. The shortest path, in terms of travel time, for my army in the south from its current position to the threat in north is through Changsa! So I will be advancing units into Change from the east, southeast, and southwest. This allow units entering from the southwest to exit through the eastern hex side should that prove necessary. So now getting a solid phalanx of troops into Changsa is vital to the movement of my reserves. The question is whether I should just let the situation in the north deteriorate while trying to continue the offensive against Henyang, or whether those troops should be diverted north. Only time will tell, but I am already starting to contemplate a possible retreat in the north in order to consolidate my position there. If the Chinese do advance out into the plain, however, this could be good for me since they will be more stretched out and in poor defensive terrain.
FatR: we have a hr limiting CAP/Sweeps/Bombing to 25k feet.

A lot going on this turn. In no particular order:
The Kasagi came out of drydock today. It is joined by the Zuikaku and Junyo which also recently came out of the yards. These three carriers will now sail south to Ulithi to join the rest of the KB, although the Junyo will then be split off to join the slow KB down in the DEI. So now everyone is all done repairing from the actions around Ponape and from some sub attacks (both Junyo and Kasagi were the victims of sub attacks).
The airfield at Truk was almost totally repaired today. At the end of yesterday, it had 29 runway damage and 25 service damage. Today there was only 5 service damage left. Wow! [X(] [&o] I have never seen my runways repaired that quickly. I guess 250 engineers will do that. There was no follow up attack today, for obvious reasons. [;)]
The raid on the Darwin convoy was a resounding success. First, we encountered the Dutch sub KXVIII and put two solid hits on it and 10 damaging near misses.
Next, we ran into the PTs guarding the port. They did not cause a problem with visibility at 12k yards and after PT-112 was obliterated by a 20cm hit, the other 4 PTs decided to high-tail it.
Then it was on to the main event, the destruction of the allied supply convoy. Apparently, witpqs gambled that I would not go straight for Darwin since last time I went for a different hex. Or maybe he though I was up to something at Moa besides staging for a surface raid. Whatever the case may be, we encountered and sank 5 xAKs and a DE. Our spotting report from yesterday was amazingly accurate, reporting 7 xAKs.
Allied Ships
DE Encounter, Shell hits 7, and is sunk
xAK Empire Hamble, Shell hits 5, Torpedo hits 1, and is sunk
xAK Fatshan, Shell hits 6, Torpedo hits 2, and is sunk
xAK Hanyang, Shell hits 9, and is sunk
xAK Ping Wo, Shell hits 4, Torpedo hits 2, and is sunk
xAK Taiyuan, Shell hits 3, Torpedo hits 1, and is sunk
xAK Wulin, Shell hits 4, Torpedo hits 2, and is sunk
The bombardment was the one part of the operation that could have gone better. I forgot to set any of my float planes to recon, so we didn't have any spotters. As a result, damage to the airfield was minimal:
Japanese Ships
CA Kako
CA Kinugasa
CA Haguro
CA Myoko
CL Kuma
DD Yuzuki
DD Mochizuki
DD Mikazuki
DD Akebono
E Asagao
Allied ground losses:
11 casualties reported
Squads: 0 destroyed, 0 disabled
Non Combat: 0 destroyed, 2 disabled
Engineers: 0 destroyed, 0 disabled
Guns lost 1 (1 destroyed, 0 disabled)
Airbase hits 3
Runway hits 4
Finally, on the way out, the cruiser TF encountered the xAK Caithness which apparently was able to get underway before our bombardment force arrived. The Caithness is now slated to become a popular diving attraction after the war.
Over in China things look like they are about to heat up.
My troops advancing on Changsa/Henyang are making good progress - they have only 8 miles to go which they should cover in 2-3 days at most. Once they enter the target hex, witpqs will know something is up and start to react. I have already set another 5 divisions to march towards Henyang and 5 more are ready to move on Changsa.
So far so good. But witpqs has thrown quite a monkey wrench into my plans. Earlier, I pulled an HQ and an artillery unit out of Nanyang. Perhaps witpqs noticed this movement, perhaps he noticed the smaller number of units, or perhaps he has had an offensive planned for a while. But when I checked today I was chagrined to see 30 units sitting in the woods next to Nanyang. Previously, there were only 15 units there, the units I had kicked out of Nanyang when I captured the place. When these new units arrived I am not sure since I am not religious about checking in on the Chinese situation. At any rate, it is obvious a Chinese offensive is immanent.
I have already started three divisions marching towards Nanyang as reinforcements. I doubt they will arrive in time, but I need to try. These are all the reserves I can muster in the north China theater. My other reserves are all advancing on Changsa/Henyang!
So now we have an interesting situation. The shortest path, in terms of travel time, for my army in the south from its current position to the threat in north is through Changsa! So I will be advancing units into Change from the east, southeast, and southwest. This allow units entering from the southwest to exit through the eastern hex side should that prove necessary. So now getting a solid phalanx of troops into Changsa is vital to the movement of my reserves. The question is whether I should just let the situation in the north deteriorate while trying to continue the offensive against Henyang, or whether those troops should be diverted north. Only time will tell, but I am already starting to contemplate a possible retreat in the north in order to consolidate my position there. If the Chinese do advance out into the plain, however, this could be good for me since they will be more stretched out and in poor defensive terrain.
FatR: we have a hr limiting CAP/Sweeps/Bombing to 25k feet.







