I’m bumping this old thread up for consideration again due to issues with my latest upcoming historical mission design which show that the AI directional control problem is still unresolved in the 4.14.1 patch.
I do hope that the team is considering fixing this issue as it is a major problem for those wanting to produce carrier missions using historically poor weather.
My design requires 8 Hellcats to takeoff from an Essex class carrier in overcast (Cloud Type 4) to work historically. The work-around of having the second flight as an air-start doesn’t fit this situation, and doesn't fully stop the crashes anyway. Unfortunately the Hellcat is even more prone to crashing than the Wildcat. Those taking off from the port side just lock on starboard rudder without allowing for deck roll and very frequently and explosively crash into the gun turrets or island structure!
Despite discussion on Mission4Today (see link below), and much experimentation, I am unable to achieve the above scenario without frequent AI crashes on takeoff (sometimes 3 out of 8!), even when a realistic headwind is added. We know that the cause is the deck roll that the game automatically introduces with the poorer cloud conditions. But carrier operations were often in poor weather. In fact they generally relied on cloud cover to screen their location from the enemy, so it is extremely frustrating not to be able to produce workable carrier missions with even just an overcast sky.
This is even worse than the situation I noted in this thread a couple of years ago in regard to the Wildcat. It is especially bad when you consider that a sufficiently bad crash on takeoff can cause damage to the carrier and cause it to lose speed and formation and collide with its escorting fleet!
If Daidalos can’t fix the directional control issue when there is deck roll, can you please give the mission builder the option to choose the amount of deck roll separately to the cloud cover? 
https://www.mission4today.com/index....wtopic&t=25003