cannot reproduce AGM-88C HARM POS mode SPI targeting vs STPT / HUD Symbology Mismatch

[HeathenHedgehog]

During a flight yesterday I found odd behavior in regard to HARM POS mode. Usually I create a steerpoint where a known SAM is and lauch on that, which has always worked. But on this occasion my original target was destroyed, and I switched to targeting a Patriot battery. The attached screenshots where taken back to back with no changes made. Jet did not have TGP or HTS equiped.

Instead of creating an entirely new steerpoint, I used the FCR to slew my SPI to directly over the site location. Here's where things get wierd though: as you can see in the HUD image, the ASL, TD box, and FCR ranging data (B034.1) all indicate launch and cueing data for the SPI directly off my nose. However the HARM Launch Scale indicates a target much closer that 34 miles, and the carat was actually moving UP the scale as the STPT was at my 5 o'clock and getting furrther away. I tried cycling POS sub modes, TMS up to FTT the target, and cursor zero + re-slewing the FCR to the Patriot. Unfortunately I did not get a screenshot of the FCR, but the SPI was on the Patriot site as shown by the TD box on HUD. There is no HARM FOV box visible in the image, because my screenshot captured in between flashes, it was present and flashing indicating in parameters for launch. When I launched the HARM it pulled hard to the right and went to the steerpoint behind me. 

null

My question is whether HARMs in POS modes can only go to the original STPT, regardless of SPI from other sensors or offsets placed into the system. If so, I completely understand, but in that case I'd ask if the HUD symbology is correct, since the ASL and TD box seem to correlate with SPI/FCR data.

I would attach the trackfile but it was 2+ hours and I dont have a time stamp.

null

[Lord Vader]

Hey @HeathenHedgehog

We understand sometimes tracks can be huge in long missions. But can you try to replicate this in a short track?

There does seem to be a disagreement between HUD and HSD data but we need more information.