i’ve noticed, that flights for D-EDMJ are not tracked properly / not tracked at all. The last recorded flight is from 2017, however the plane is in active use by a flightschool.
While it was airborne, i’ve seen it on a personal ADSB tracker with the registration D-EFLK (Hex: 3D1304), but the visible callsign was DEDMJ as expected. On FR24 it also appears as D-EFLK.
Why is that so? It seems to me, that it maybe tries to lookup the plane using the ICAO id, but this doesn’t seem to match to the callsign (maybe the transponder got changed between the aircraft?). Is there anything one can to do remediate that issue or does this need fixing in some other database? Or has it to be done by the owner?
I haven’t found any information how that additional data is getting fetched for a flight, as i know, that ADSB only transmits the ICAO id, callsign, altitude, …
The flighthistory for this aircraft is normally present in the flight history overview.
It is seen as D-EFLK indeed.
The D-EDMJ aircraft has crashed 22 october 2012 near Dronten in the Netherlands.
I can only suspect that they recycled the transponder onto the D-ELFK aicraft and thus is showing as the D-EDMJ. I suspect the transponder hasn’t been modified in regard to the registration. That has to be fixed by the aircraft owner.
Transponder is sending the wrong hex id.
Many trackers just look up the hex id in a database and get the registration.
Using the callsign for registration is not feasible as you can imagine.
Either the database is updated or the owner needs to change it.
If it’s the correct hex or maybe even if it isn’t … eventually the databases should get updated if people aks for those changes.
I can definitively say, that there is currently a C152 registered as D-EDMJ and it’s owned by a flight school at EDMJ airport. Interestingly, there seems to have been a C152 with registration D-EFLK up until 2011, also owned by that flight school and as of 2014, the D-EFLK registration belongs to the C182.
D-EFLK also seems to have a healthy life as a C182 in the north of Germany.
So most likely, the registration was transferred after the 2012 crash to a C152 and maybe that C152 was registered as D-EFLK before which now confuses some databases about it’s identity.
@wiedehopf what database is this? something proprietary, that each tracker website fills on it’s own or is there a “common” upstream database like jetphotos/planespotters.net for pictures? From my understanding, it would be perfectly possible, to just fill such a database with data received through ADSB.
If these databases passively filled, i can easily imagine, that FA stored it with the hex / registration combination when it first saw the aircraft and likely these records never get updated unless someone requests a correction. Both FA and the plane are old enough for that possibility
For D-EFLK, the registration was derived from a deterministic allocation pattern used for that particular range (i.e. there is a predictable mapping from ICAO address to registration in this case). If the physical aircraft is not D-EFLK, then either the transponder is misconfigured or the deterministic rule is wrong. D-EDMJ should be using 3D0DD5 according to the rule.
