Data errors in Flightradar24 aircraft database

[Oblivian]

In any case and if it can help, I'm private owner of OK-QUA95.
Best,
DIDIER

The 'callsign' in the transpoder appears to be entered incorrectly. Or a previously logged flight plan had the wrong reg entered during logging.
All the wrong references are 'flight' references. Not registration, nor hex - the broadcast callsign from transponder.

The same way when you search a commercial aircraft, the 'flight' varies to their callsign.
https://www.flightradar24.com/data/aircraft/zk-ojs

[apgphoto]

I'm not 100% certain, but hex 49C07A is either being used by both OK-QUA95 and OK-UUA95, or maybe one is using a second-hand transponder from the other aircraft.

It doesn't seem likely, but I suspect the latter, because the latest reports of 49C07A have all been in Italy, and using both callsigns.

Does anyone know the hex for OK-UUA95?

49C07A is OK-QUA95 although the MSN is wrong in the DB its an old demo aircraft and has been using this code since 2011

The Czech registry doesn't list ULM's but OK-UUA95 has been reported as 49C104 in the past. UUA95 was also a company demo so I suspect it may have been miscoded at some time and i would guess its flying with the new dealer in Italy.

[Oblivian]

49C07A is OK-QUA95 although the MSN is wrong in the DB its an old demo aircraft and has been using this code since 2011

The Czech registry doesn't list ULM's but OK-UUA95 has been reported as 49C104 in the past. UUA95 was also a company demo so I suspect it may have been miscoded at some time and i would guess its flying with the new dealer in Italy.

This is odd, given you can only search for one of them that I could see 0.o (searching OK-UUA95 finds no record, but it does list it as a flight sign for QUA)

[apgphoto]

In any case and if it can help, I'm private owner of OK-QUA95.
Best,
DIDIER

Didier you need to speak to TL or their Italian dealer and get them to change the transponder code on the other aircraft

[apgphoto]

This is odd, given you can only search for one of them that I could see 0.o (searching OK-UUA95 finds no record, but it does list it as a flight sign for QUA)

Other sources

[40612]

Hi, the data base currently shows the following:

068BA2
XA-GIM
C680
Cessna 680 Citation Sovereign
680-0231
Private owner

Please note the Mexican hex code is 0D097B. Could you please modify it? Thanks!

Miscode 068BA2 was also being used up until a few days ago. Hopefully, someone has recoded the transponder correctly.

[Oschtan]

ModeS: 155BF2
Type: Sukhoi Superjet 100-95B
Type code: SU95
S/N: 95026
Registration: RA-89074
Airlines: SCAC
Age: Dec 2012

ModeS: 155BFC
Type: Sukhoi Superjet 100-95B
Type code: SU95
S/N: 95027
Registration: RA-89084
Airlines: SCAC
Age: April 2013

[apgphoto]

3C4894
D-ABDT
A320
Airbus A320-214
3422
Air Berlin
BER
2008-02-11

Currently in the DB just as a B738

[SGAviation]

ModeS: 76CD69
Registration: 9V-SKI
ICAO Type code: A388
MSN: 034
Airline: Singapore Airlines
Operator code: SQ/SIA

ModeS: 76CD6A
Registration: 9V-SKJ
ICAO Type code: A388
MSN: 045
Airline: Singapore Airlines
Operator code: SQ/SIA

Both frames are repainted back into standard livery and no longer in (SG 50 Livery).

[Tyke's Aero blog]

Thank you.

If I read you right, RA-89047 carries two transponders: 155BD7 and AC4858; the second is miscoded at aircraft.

- That appears to be the case, yes.

Is AC4858 correct code for N89047? Does this C140 have transporder on board? How this can be checked?

The C140 will have a transponder, yes, although from the past 6 months history it doesn't seem to have been picked up anywhere. I know you could argue that in that case AC4858 should be entered as the Sukhoi as it's the more likely one to be "seen" but FR24 doesn't work like that as it means additional time-consuming database work when the correct owner of the hex starts using it. The exception to this is usually when the registration the hex 'belongs' to is not assigned, but that is not the case here.

[Edilson.Carlos]

Sem título.pngScreenshot_3.png


For a long time we Brazilians tried to request correction of this error, but due to the existence of two aircraft flying with the same hexcode, correction was not possible. But now one of the aircraft has changed its hexcode after changing operator. We would like the error in the database to be fixed.

342457
FAB2802
CN95 (C295)
CASA C-105A Amazonas
031
BRS Força Aérea Brasilieira

The aircraft that belonged to the above hexcode is now flying to LOT - Polish Airlines and had its hexcode changed to 5110D1, thereby releasing hexcode 342457, so there is no more duplicity.

OLD: EC-JTS
HEX: 342457

NOW: ES-ACH
HEX: 5110D1

https://www.planespotters.net/airfra...TS-Air-Nostrum
https://www.planespotters.net/photo/...amazonas-c-295

[Edilson.Carlos]

This aircraft is now flying to new operator... now is SIDERAL AIR CARGO

AA5076
PR-IOC
B727
Boeing 727-264(A)(F)
22984
Sideral Air Cargo
Screenshot_4.png

[lLivien]

49D26C
OK-TVR
B738
Boeing 737-86N(WL)
38018
Travel Service
TVS

[lLivien]

49D341
OK-MNP
B206
Bell 206 B JetRanger III
3814
Private

[Tabbex]

A4E864
N415TH changed to PR-DCD
BE58
Beech G58 Baron
TH-2415
Private owner
built 2014