Any GPS signals in that region of the world are being jammed, so this is probably a result of that. It’s not actually flying over Ukraine
@52fighters
Because airplane ADS transmitter had lost connection to public ADS ground receivers or simply had been switched OFF.We have also seen this kind of error with the Azerbaijan Airline flight to Grozny which Russia shot. Due to electronic warfare the positions on flightradar didn’t make sense in the early hours, until they reconstructed a more plausible path.
Flight J28243 was scheduled to operate from Baku to Grozny. The aircraft departed Baku at 03:55 UTC. Valid ADS-B position data was received from the aircraft until 04:25 UTC when the flight encountered significant GPS interference. The aircraft stopped sending positional data altogether for the period between 04:25 and 04:37. Between 04:37 and 04:40 the aircraft sent likely erroneous position data. Flightradar24 receivers did not receive data from the aircraft between 04:40 and 05:03 and a second gap from 05:04 to 05:13 . From 05:13 until 06:07 all data received from the aircraft lacked positional information. From 06:07 UTC through the end of the flight at 06:28 position data was received from the aircraft.
This is most likely to be the same kind of error.
Here’s the link-- https://www.flightradar24.com/AFL1367/39528758
The dashed line means the path is a guess. When the plane stopped sending GPS signals, Flightradar draws a straight dashed line to the direction the plane was heading to when losing the contact, and continues the path on the same speed until the real location of the plane is known again.
And then the dashed line moves to go to where the plane has actually gone in that time.
So, the plane hasn’t been there, this is just how Flightradar reacts to the Russia’s GPS jamming.
