drgondog
Major
I'm researching the 445th BG/2nd CW disaster on 27 September and noiced that both 20th BW and the 14th BW Target MPI were substantially different from the 2nd.
Does anyone have have the MPI codes for Kassel/Gottingen area targets?
MPI are Mean Point of Impact codes for specific target aiming points and different from Lat-Long.
The reason I ask is that the 355th FG Briefing Map points to a specfic (and different) track from the IP to Kassel bomb run. The 445th BG led the 389th and 453rd on the track East, while the 14th and 20th headed to Kassel targets to e-s-e. The map clearly shows the branch, the separate target bmb run. the N-N-E break for both forces to the Rally Point.
Current wisdom points to defective Mickey Nav Radar in 445th BG lead ship, but the 355th map continues to nag. The 355th was lead escort covering 14th BW, with 4th covering middle (2BW) and 361st in trail - the 479th was positioned for TE on the 'Gottingen' vector.
My father was on that mission and Robin Olds (479th) was on that mission.
Regards,
Bill
Does anyone have have the MPI codes for Kassel/Gottingen area targets?
MPI are Mean Point of Impact codes for specific target aiming points and different from Lat-Long.
The reason I ask is that the 355th FG Briefing Map points to a specfic (and different) track from the IP to Kassel bomb run. The 445th BG led the 389th and 453rd on the track East, while the 14th and 20th headed to Kassel targets to e-s-e. The map clearly shows the branch, the separate target bmb run. the N-N-E break for both forces to the Rally Point.
Current wisdom points to defective Mickey Nav Radar in 445th BG lead ship, but the 355th map continues to nag. The 355th was lead escort covering 14th BW, with 4th covering middle (2BW) and 361st in trail - the 479th was positioned for TE on the 'Gottingen' vector.
My father was on that mission and Robin Olds (479th) was on that mission.
Regards,
Bill
