Plane overtaking others on approach about livetraffic HOT 2 CLOSED

That's gonna be difficult to analyse without precise data. I see form the Log you ran OpenSky and ADS-B in parallel, that is allowed, but also good for issues.

Imagine (and I did see that also), that OpenSky and ADS-B data are slightly off by a few seconds. The plane would approach at, say, 160kn if reading channel A only. Then a data point from the other channel B comes in placing the plane closer to the runway but with a timestamp not too far away from the last one received from channel A (due to the fact that both channels aren't quite synched as we defined as the precondition). To make up for that LT would need to speed up that plane quite a bit and it overtakes all other planes which are controlled by channel A data only (because maybe they just don't appear on channel B).

Can't be proven from the log. Which, btw, ends on Monday, December 3, 2018 1:33:31.300 PM european time, it doesn't cover 15:00.
(The long number after the text "LiveTraffic" is just a Unix timestamp, which can be converted on web sites like this one.)

Full analysis would only be possible with a network log.

To prepare for better analysis next time you may want to activate "Debug: log a/c positions" already. That places position information into the log for the plane selected in an a/c info window.

If you see something like that again (or any other suspicous plane) then try to identify the plane and open an a/c window for that plane. Then all future positions and decisions are logged into Log.txt. A full network.log would still be better as it would cover the history as well.

from livetraffic.

For better handling of multiple channels see #61.

from livetraffic.