Data errors in Flightradar24 aircraft database

[speedbird1960]

The Aircraft is using the wrong Hex code, there is nothing we can do about it as its the Airlines responsibillty to check the Transponders are using the right Hex code.

Remarks: Using incorrect ICAO24 address 3C6313 on mode-S, instead of 3C6303. The registration is showing as D-AHXC
http://www.airframes.org/reg/dahxc

[tom1972]

so far, so good.

The Aircraft is using the wrong Hex code, there is nothing we can do about it as its the Airlines responsibillty to check the Transponders are using the right Hex code.

Remarks: Using incorrect ICAO24 address 3C6313 on mode-S, instead of 3C6303. The registration is showing as D-AHXC
http://www.airframes.org/reg/dahxc

So if this added Pic is korrect, today the D-AHXC flew as DAHXC to MUS, arrived there at 1400Z
and took off 1510Z with the wrong HEX DABKC to CGN....

So sometimes its using the right and the wrong hex?

and yes, sure, i know, nothing FR24 can do about it! ;-)

Best wishes anyway. Maybe someone worked on the case already and can help?

[AirMe]

ModeS: 4BA890
Reg: TC-JDP
Typecode: A33F [no A332]
Type: Airbus A330-243F
Serial number: 1092
Airline: Turkish Airlines Cargo
Icao: THY

[AirMe]

ModeS: 3C6496
Reg: D-AIDV
Typecode: A321
Type: Airbus A321-231
Serial number: 5413
Airline: Lufthansa (Retro livery)
Icao: DLH

[tom1972]

So if this added Pic is korrect, today the D-AHXC flew as DAHXC to MUS, arrived there at 1400Z
and took off 1510Z with the wrong HEX DABKC to CGN....

So sometimes its using the right and the wrong hex?

and yes, sure, i know, nothing FR24 can do about it! ;-)

Best wishes anyway. Maybe someone worked on the case already and can help?

UpDate 02-01-13
It is visual confirmed: it was the D-AHXC. On the leg before she was on FR24 as XC.
But after take off at MUC heading CGN she came up with the wrong reg D-ABKX again.
I am wondering if this is the switch onboard or the database from the EDDK Radar dude.
However. I have one more answer to work with.
Happy New Year everyone.

[CGlobe]

Was the hex code the same on each occasion? If yes, then it's a database error for that hex-to-registration tie-up. Of course, if it's just the callsign that's incorrect, that's user error on behalf of the crew (who probably didn't pay much attention as it wasn't a revenue service)

Finally, if the hex was different each time, then it looks like the three transponder boxes on that aircraft (I think the 737 is the only narrow-body to have three, like the 747/767/777 do?) are each programmed differently.

[AirMe]

ModeS: 7100A6
Reg: HZ-ASF
Typecode: A320
Type: Airbus A320-214
Serial number: 4955
Airline: Saudi Arabian Airlines (SkyTeam livery)
Icao: SVA

[AirMe]

ModeS: 3C49A5
Reg: D-ABME
Typecode: B738
Type: Boeing 737-86J ["One world Livery" not here!]
Serial number: 37766
Airline: Air Berlin (OneWorld Livery)

[Primperam]

Re-posted.

[GraemeH]

A6-EYZ Hex: 8960C2 Etihad has no such aircraft . No B767. The aircraft this tags to is A6-EIZ Hex 8961C2. which shows in the pic! Perhaps it depends which transponder is selected for the flight.

[AirMe]

ModeS: 780212
Reg: B-KPF
Typecode: B77W
Type: Boeing 777-367ER
Serial number: 36832
Airline: Cathay Pacific (Asia's World City livery)

[TCASAlert]

Error with the labelling of a ground station:

Aircraft: Enroute Navaid ()
Reg: TNT-VOR
Hex: 76EB00
Pos: 53.0606 / -1.5456

This isn't TNT VOR. TNT VOR is located here:

http://goo.gl/maps/v5fbv
53°3'14"N 1°40'11"W

The marker in question is in reality a set of radio masts at Alport Heights, which periodically broadcast a MODE-S signal.

[KKS]

new re-registred
UR-AAO (ex Aerosvit) to UR-PSF (Ukraine International)

http://1.bp.blogspot.com/-0zNelig3QP...1600/URPSF.jpg

[littledave]

EI-SLA now fly for mistral air:

Incorrect:
4CA28D
EI-SLA
AT43
ATR42-300
149
Air Contractors
ABR

Correct:
4CA28D
EI-SLA
AT43
ATR42-300
149
Mistral Air
MSA

[fatmirjusufi]

Airline: B&H Airlines (correct Turkish Airlines)
Aircraft: Airbus A319-132 (A319)
Reg: TC-JLR
Source: http://www.airfleets.net/ficheapp/plane-a319-3142.htm