Bearfoot Posted July 7, 2020 Posted July 7, 2020 I have no idea if this is an issue or just coincidence + psychological ascertainment bias. I've noticed that when I have been scanning the airspace on TWS-M, with somewhat extreme offset (altitude, usually, but sometimes azimuth and sometimes altitude+azimuth), and then pick up a contact and fire a Phoenix, almost immediately the contacts get dropped. I started wondering if what was happening is that when firing the Phoenix, we switch automatically to TWS-A, which defaults to centered elevation + azimuth scan volume. As the contact is not easily detected in the default (centered elevation + azimuth) scan volume, it is lost. Jester then switches quickly to RWS for some reason. I fully admit that I could be completely off here and maybe everytime it has happened it just a bunch of poor contacts that coincidentally dtopped right after firing the Phoenix(es). Do you folks see anything similar?
Bearfoot Posted July 7, 2020 Author Posted July 7, 2020 Ok. Just did some controlled experiments with azimuth. Bandit tootling along on far right. Command TWS-M to swing far right. Contact. Launch Phoenix. Switch to TWS-A, with no drop of contact, lock, or change of azimuth. Perfect! Now to see if the same holds true for elevation. A little more tricky to set this one up ...
Recommended Posts