Got back in the air again over this summer and fall, IPC, etc., after about 2-3 years of little-to-no flying. . .never really paid much attention to ADS-B traffic back then - I was in the DC FRZ and SFRA so much of the time and our airplane was lacking ADS-B in anyway. . .
I'm in coastal NC now, with a lot of traffic and crowded airspace, lot of guys squeezing around MOAs and Restricted areas. Not a lot diffrent than metro DC. . .
So, getting my feet wet in the system again I've noticed that often ADS-B in targets "jump" - like a couple miles, almost instantly. At least once I've eyeballed an airplane that I thought was "missing" on the display, only to see the display suddenly "catch up".
WTF? Software processing delays? latency? Not hitting a tower? An "add on" Skybeacon thingy not getting interrogated and triggering a response? Some shortcoming in my boxes?
I'm in coastal NC now, with a lot of traffic and crowded airspace, lot of guys squeezing around MOAs and Restricted areas. Not a lot diffrent than metro DC. . .
So, getting my feet wet in the system again I've noticed that often ADS-B in targets "jump" - like a couple miles, almost instantly. At least once I've eyeballed an airplane that I thought was "missing" on the display, only to see the display suddenly "catch up".
WTF? Software processing delays? latency? Not hitting a tower? An "add on" Skybeacon thingy not getting interrogated and triggering a response? Some shortcoming in my boxes?