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.
Another one; On 2025-02-04 the ghost-D-AGLO can be seen leaving AMS for BCN.
In the replay D-AGLO takes off at 06:11z in between AUA3NA(OELBK) and LOT7LA(SP-LII) with only a runway-length seperation…way too little.
On LiveAtc again both airliners can be heard getting their take-off clearance but D-AGLO/KAY58 is missing. The archived file should be avialable for the next week or so (listen between minute 09 and 12).
On adsb lol it can be seen flying LBG-MUC around that time!
The flight to BCN seems a copy of leg 1 of PH -BXO (hex 48418A) two days earlier.
Two questions for the engineers; Would it be possible to feed a whole virtual flight through one feeder outside its theoretical range? And would a virtual flight starting before, and probably landing after the real flight obscure that? If e.g. your software rejects data far away from an aircraft that is already live? The real flight on 2025-02-04 LBG-MUC ~0625-0725z fits within the fake AMS-BCN flight ~0611-0757.
Addition: The virtual aircraft “flew” a few days later to MUC, on 2025-02-08, showing BCN-MUC with a flightpath that seems copied from DLH96C, A321 D-AISB 3C6664 a day earlier. Its cruise level FL336 doesn’t make sense either.
On 2025-2-11 D-AGLO flew MUC-BTS, both visible on adsb-exchange and adsb.lol … audio of Bratislava on liveATC confirms its arrival so since a long time this seems like a flight that is normally visible on adsbEx. 2025-2-13 shows a flight from BTS to the Caribbean or south-America. My own SBS picked up this flight so thisi seems to be correct data as well.
The fake-flights keep going. On 01/03/2025 and 04/03/2025 D-AGLO flew LBG-CMF-LBG return-flights, with the fake-aircraft on ADSBex jumping around at LGW. I am convinced fake data is transmitted to ADSBex everytime the real aircraft flies, suppressing its real track.
The data seems correct on adsb . lol and FR24 (anonymous GL7T though).
Besides this, fake flights are injected when the real aircraft is parked…I guess to fool activists, journalists, business analysts etc.
The fake D-AGLO flew LGW-ALG yesterday, 05-03-2025, using the path of A321 G-EUXG (hex 400aff) earlier that day.
Interestingly, ADSBex reception around ALG at low altitude is not good. G-EUXG was lost below 7700ft and the same can be seen with current live traffic. D-AGLO 's track however ends exactly where the FR24-track of G-EUXG stops, a few turns after vacating the runway.
Just speculating, but pressing KML or CMV in the FR24-flighthistory gives a good bit of data to feed a little program on that could feed interpolated fake data to ADSBex.
Can you see if the flight from LGW-ALG is coming from only one feeder?
(hex 3c5d8f 2025-03-05 , I cannot post links here )
I believe this is a fake flight. A lot of data is missing in the left-hand fields of the webpage, like FMS SEL, WIND, SPEED (except ground speed), many DIRECTION fields, etc. This data is available on what I believe is the real flight it was copied from (hex 400aff 2025-03-05 leg 1) .
…and eg. also on a recent real flight the aircraft made 11-2-2025 from MUC to BTS
(hex 3c5d8f 2025-02-11)
The fake aircraft is ‘flying’ now from Algiers to the north. It is currently near Luxembourg. I think the flighttrack is a copy of TUI Belgium B38M OO-TMB, flight TB3465 of 03/03/2025. If so it should ‘land’ in <30m at BRU runway 25L. Say 10:30lt.
Under SIGNAL number of receivers jumps up to ~8…I had expected 1 to be honest.
