Bahger Posted March 14, 2013 Posted March 14, 2013 I have two flights ingressing via fairly close, parallel routes. Each gets its target from a separate JTAC. I have placed separate IP nodes at each flight's IP. I've noticed that the JTAC does not reference the right IP and nor does he give the right distance, during the nine-line brief. I wonder, should I use just one IP for both flights (and deconflict those flights by altitude)? Is there a rule of thumb regarding the distance from IP to target, or initial check-in point with the JTAC and the IP, to assure that the system works properly and the right IP and distance is referenced? Also, nobody has responded to my question about the "marked by willie pete", shortly followed by "no mark" sequence of responses by the JTAC. I don't know what I'm doing wrong either in the ME or in flying the JTAC approach to make this happen, but if I can't get it to work, I'll have to eliminate the WP mark option in the ME, as it's not mission-critical. I sort of suspect that mark works better the further away you make the first call and the greater the spacing is between that call, the IP and the target.
TC Posted March 14, 2013 Posted March 14, 2013 I take it you are refering to the same mission as yesterday, then yes you should place just one IP as they are almost on top of each other. The way you placed them tho makes em more like a CP as you have another WP afterwards (that should be the IP). As for distance to target ... The JTAC/FAC(A) selects the IPs/BPs based on enemy capabilities, target orientation, friendly location, weather,aircraft capabilities, and fire support coordination requirements. IPs are normally located from 5 to 15 nautical miles (nm) from the target for FW aircraft ... For PG munitions drop I usually set it at 10nm. I normally don´t use the ME ones so I just made a quick mission to check and JTACs referal to the IP (heading, distance to target) worked just fine. The "no mark" glitch came with the last patch I think and I could get a WP having an AFAC A-10 overhead loaded with WP. Got the "no mark" using a IFV at around 1nm distance. Maybe the unit now actually needs to have them loaded, tho the A-10 did not make an attack run to employ the WP - smoke did just pop up ... Cheers TC
Bahger Posted March 14, 2013 Author Posted March 14, 2013 (edited) Thanks, TC. The WP I have after the IP is to get the two flights to anchor either side of the AO after they have finished their enroute tasking. I'm wondering whether it's better to delete this WP to make the JTAC AI work properly or whether to ignore it... EDIT: Before I make the change and eliminate the orbit WP after the IP, can anyone tell me what the AI A-10s will do after they have finished attacking targets if they have no WP after the IP? I do not want them to RTB. Should I make an orbit command at the IP as #3 in priority to the other two prior orders? Edited March 14, 2013 by Bahger
Recommended Posts