reported A/A radar, L&S target shows unreasonable speed tag

[Rongor]

In the attached track, which lasts a few minutes, I play around with locking/undesignating a target.

In several occasions, the speed tag showed thousands and inconclusive numbers. This remained some seconds before returning to Mach values.

shown are examples in RWS with active LTWS

 

target.trk

Edited November 11, 2021 by Rongor

[Tholozor]

Usually happens when the contact has only been scanned by the radar once, as the beam has only obtained a single range data on the hit, it needs a second hit to extrapolate the positional difference to calculate the contact's velocity.

[Harker]

Usually happens when the contact has only been scanned by the radar once, as the beam has only obtained a single range data on the hit, it needs a second hit to extrapolate the positional difference to calculate the contact's velocity.

I've noticed the same thing as well. AFAIK, it simply shouldn't build a trackfile with only one return, prior to obtaining velocity.

[BIGNEWY]

reported

thanks