Yesterday (29-01-2025) adsb-exchange showed D-AGLO landing at 21:35z at AMS from LGW. Tracks look very normal but the real aircraft is nowhere to be found. The aircraft is not known in the airport’s systems. On a replay it landed in between A20N OE-LSN and B38M PH-TFN . My own SBS-3 logged both airliners but not the GL7T… On liveATC both airliners can be heard getting their landing clearance on 118.28 but no aircraft in between.
Today the GL7T still pings in a hangar at Schiphol-east, while at a competing website it is flying LBG-CIA… Also FR24 shows an anonymous GL7T on that flight.
My own SBS logged this aircraft once at AMS this year, 21-08-2024, also using VDL-2, landing 0713z rwy27 and departing 1137z rwy22. On the Scramble forum it was announced before landing as it was entered in the airport’s systems.
On adsb-exchange however, it flew HAJ-MAD-HAJ that day!
Assuming the picture’s date here is correct, here another mismatch, at LTN on 08-09-2024:
On adsb-exchange it flew BRU-BCN-AMS (I doubt that).
And at DMK 20-11-2024 :
So it shows up on adsb-exchange were there is no real aircraft , and were the real aircraft is there is nothing on adsb-exchange (no other hexcode either) .
Any ideas what is going on? It is almost like someone is sending out fake data to hide its flights.
Here a possible case of blocked data, AMS 21-08-2024:
I had to reconstruct the arrivals of my SBS-3 from a compressed log. TGZ651 did not transmit a position so is only visible in the list on the right. D-AGLO was perfectly visible…but is completely missing on ADSB-exchange!
I’ve also had a report of someone seen it land at LBG at 21-07-2024 ~2015lt without any trace on ADSB-exchange.
thank you. is there other detail from the other posts (hidden to me) regarding where these bogus tracks appeared and for what day? If I check the history on this reg#, the last flight track was Jan 29 ADS-B Exchange - track aircraft live
I tried posting a couple of flights but with max 2 urls per post I made 3 quick consecutive posts which is probably why now all my posts are flagged as spam.
So without urls:
First I posted a screenshot of my SBS showing D-AGLO landing at AMS 2024-08-21 0711z, ahead of PH-EZX, and a screenshot of a replay of ADSB-exchange where it was missing.
Then I found a couple of flights were D-AGLO flew an almost exact copy of a flight of an airliner a few hours earlier on the same day:
Have a look at D-AGLO 's flight on 2025-01-29 LGW-AMS, it seems an exact copy of A320 G-EJCE EZY45XC/6371 hex 407E61 .
And before that, 2025-01-29 BCN-LGW looks like OE-LKK EJU8062 hex 44061B
Further back, 2024-07-21 AMS-FLR flew exactly like PH-EXY KLM63V/1651 hex 485875. That day I logged the aircraft at LTN and I have reports of people seen it land at LBG in the evening without it being visible on ADSB-exchange.
Hard to believe but it seems the aircraft’s real flights are blocked and are replaced by copying flights of other aircraft. Flighttime, speeds and groundtracks are not the same but the airborne path is!
Thank you. I had another look at both LGW-AMS flights of 2025-01-29. The data-points are not the same but both aircraft need exactly 9m43s to reach top-of-climb at FL230 north of Maldon from the end of the runway. Speeds transmitted by D-AGLO are about 40% higher though…it must have made a Concorde-like take-off at 200+ kt halfway the runway, going faster and faster at low altitude, reaching 390kt at FL100. (ok groundspeed, but until here max 250kt indicated is allowed).
Own data of D-AGLO’s visit of AMS 2024-08-21, and the last GL7T departure at AMS (OE-LSS at 2025-01-31) show more modest, A320-like speeds.
Weight, wind and acceleration-procedures will cause varying figures but those LGW-speeds are unrealistic, and can not lead to the same vertical profile in time as the A320.
