Carrier Battle: Bay of Bengal
Posted: Thu May 25, 2017 11:39 pm
So this is the weirdest carrier battle I have ever seen, results are inconclusive, and I feel this was a wasted opportunity to reduce the # of enemy carriers
Bif1961: You were absolutely right, there were more carriers: Yorktown and Hermes are there. But in a sense I was also right.. they were there, yes, but they were not present... and I am really struggling to understand how so many carriers could provide so little... they should had massacred my TF.. was he keeping all squadrons on stand down? was he hoping to bait me, then hopefully find me from long range and then "turn on" the lights? surprise, surprise! did I just caught him before he could setup his trap?, thoughts gentlemen please that is the only explanation I have.. and thinking more about it, it makes quite a lot of sense, I mean he was driving his carriers as if it was the full KB on December 41, giving me plenty of time to identify the ships and squadrons he wanted me to find... so sneaky [:-] [:-] [:D]
So, key results:
- Nothing happened on the surface combat phase, I am disappointed with my supposedly aggresive BB TF commander, he either shine tomorrow or start sharpening his knife for some harakiri practice; I mean the TF ended one hex below a returning bombardment TF
- Very little happened in the AM phase, damn weather!!! he actually bombarded Akyab with TBDs/ SBDs. My Army guys tried and failed to hit the Hermes, got slaughtered of course. CL Kitakami ate 2 1,000 pound bombs A lot more details to follow
- PM turn Japan: Japanese strike was weak, and being at 7 hex distance, Vals were carrying 60kg bombs.. really useless, I put a few torpedoes, but all enemy carriers survived, Wasp received 2 torpedoes and ended with "heavy damage", but no explosions and since it is very close to Calcutta, I doubt it will sink. Other TFs were attacked, and Warspite ate a torpedo, I might be able to catch him later on
- PM turn Allies: US strike was a total blood feast disaster, Japanese CAP won big time and the ships are undamaged (other than the heavy "flank speed" damage incurred
Lots and lots of details to follow
Bif1961: You were absolutely right, there were more carriers: Yorktown and Hermes are there. But in a sense I was also right.. they were there, yes, but they were not present... and I am really struggling to understand how so many carriers could provide so little... they should had massacred my TF.. was he keeping all squadrons on stand down? was he hoping to bait me, then hopefully find me from long range and then "turn on" the lights? surprise, surprise! did I just caught him before he could setup his trap?, thoughts gentlemen please that is the only explanation I have.. and thinking more about it, it makes quite a lot of sense, I mean he was driving his carriers as if it was the full KB on December 41, giving me plenty of time to identify the ships and squadrons he wanted me to find... so sneaky [:-] [:-] [:D]
So, key results:
- Nothing happened on the surface combat phase, I am disappointed with my supposedly aggresive BB TF commander, he either shine tomorrow or start sharpening his knife for some harakiri practice; I mean the TF ended one hex below a returning bombardment TF
- Very little happened in the AM phase, damn weather!!! he actually bombarded Akyab with TBDs/ SBDs. My Army guys tried and failed to hit the Hermes, got slaughtered of course. CL Kitakami ate 2 1,000 pound bombs A lot more details to follow
- PM turn Japan: Japanese strike was weak, and being at 7 hex distance, Vals were carrying 60kg bombs.. really useless, I put a few torpedoes, but all enemy carriers survived, Wasp received 2 torpedoes and ended with "heavy damage", but no explosions and since it is very close to Calcutta, I doubt it will sink. Other TFs were attacked, and Warspite ate a torpedo, I might be able to catch him later on
- PM turn Allies: US strike was a total blood feast disaster, Japanese CAP won big time and the ships are undamaged (other than the heavy "flank speed" damage incurred
Lots and lots of details to follow






