If you look at trips such as:
uk.flightaware.com/live/flight/E … /EGKK/LXGB
You can see that the track jumps back to near Gatwick where the plane is actually over mountains in Spain.
If you look at the track points:
uk.flightaware.com/live/flight/E … B/tracklog
you can see that, for example, the first rogue point occurs at UTC 18:51:42 where the latitude jumps from 40.3 to 51.0 in ten seconds.
This is due to a switch of ADS-B receiver from LECU/MCV to EGLF/FAB.
Now, it is perfectly reasonable for the Spanish ADS-B receiver in Madrid (if that is what LECU/MCV is) to fail to receive signals fronm the plane as it passes over the mountains. What is not reasonable is for the ADS-B receiver in Farnborough, UK (if that is what EGLF/FAB is) to claim to be receiving signals from a plane that is actually 1270 kilometres away. Even worse, it should not be claiming that the plane’s position is near Gatwick when it’s actually in Spain.
This problem affects many flights across Spain, and not just those from Gatwick.
Why is this happening?
(My server is monitoring aircraft flights over an English national park. These rogue points manufacture multiple fictitious flights over the park. So it seems if the problem cannot be corrected at source, I need to code detection and elimination of these rogue points.)