Data errors in Flightradar24 aircraft database

[Samish]

ModeS/Hex-code - 502C4C
Registration- YL-LCZ
ICAO Type code - TCX
Type - Airbus A321-211
MSN - 2912
Airline / Owner - Airline: Thomas Cook Airlines (TCX), Operator: SmartLynx (6Y / ART)
Paint code (ICAO) - TCX
Operator code (ICAO) - ART
First flight date - 07/04/2019

[scorp1988]

WRONG!!!
49D3C7
OK-JRG
L410
Let-L410UVP-E20 Turbolet
msn n/a
Aircraft Industries
2018-06
probably L410 testing HEX

RIGHT!!!
49D3C7
L410
Let-L410UVP-E20 Turbolet
MSN 173107
Khabarovsk Avia
2018-06
67061.jpg
67061-2.JPG
67061-3.jpg
Its serial number is even displayed in the Callsign
what other evidence do You need? recording the pilot's conversations with the dispatcher?

[Oblivian]

WRONG!!!
49D3C7
OK-JRG
L410
Let-L410UVP-E20 Turbolet
msn n/a
Aircraft Industries
2018-06
probably L410 testing HEX

RIGHT!!!
49D3C7
L410
Let-L410UVP-E20 Turbolet
MSN 173107
Khabarovsk Avia
2018-06
[ATTACH=CONFIG]10505[/ATTACH]
[ATTACH=CONFIG]10506[/ATTACH]

what other evidence do You need? recording the pilot's conversations with the dispatcher?

It cannot have an RA reg unless reprogrammed

http://hexlookup.epizy.com/hex.php?search=49D3C7&i=1

Russian Federation 100000 - 1FFFFF

Sent from my EML-L09 using Tapatalk

[scorp1988]

We in the Far East all L-410 with factory HEX fly. The case only applied the registration number of the type RA-XXXXX and all.

[Oblivian]

We in the Far East all L-410 with factory HEX fly. The case only applied the registration number of the type RA-XXXXX and all.

Typing it again doesn't make it any better

You have been told. They will not be changed

https://forum.flightradar24.com/showthread.php?p=116442

Sent from my EML-L09 using Tapatalk

[scorp1988]

Oblivian Can you change the data in the database?

[apgphoto]

We in the Far East all L-410 with factory HEX fly. The case only applied the registration number of the type RA-XXXXX and all.

If they all fly with factory hex how do FR24 know which is which aircraft? There are at least two aircraft flying with this hex code.

They need recoding to the correct Russian hex, only that way will FR24 know which are the different aircraft.

[apgphoto]

320027
320028

Can these be unblocked? They are Coast Guard A139 No idea why they have been blocked? Links below show others are not blocked.

https://www.flightradar24.com/data/aircraft/mm81911

https://www.flightradar24.com/data/aircraft/mm81910

https://www.flightradar24.com/data/aircraft/mm81749

https://www.flightradar24.com/data/aircraft/mm81748

https://www.flightradar24.com/data/aircraft/mm81747

https://www.flightradar24.com/data/aircraft/mm81741

[scorp1988]

Then why do you need this forum? In order for users to be able to tell you something! Take my word for it, it's 100% accurate. I personally watch this board almost every day and hear it on Airband. What other evidence do you need to provide?

[Oblivian]

About sums it up. Time to delete incorrect reference totally?.



Sent from my EML-L09 using Tapatalk

[apgphoto]

Then why do you need this forum? In order for users to be able to tell you something! Take my word for it, it's 100% accurate. I personally watch this board almost every day and hear it on Airband. What other evidence do you need to provide?

You are right you are 100% accurate

The aircraft is in the Russian register too!

L410.PNG

Sadly its in the Russian register as RA-67061

OK-JRG is used by Let for flight tests of new L410, its been used many times on many different aircraft. There are at least two "OK-JRG" flying in Russia (sometimes at the same time) because as you say nobody changes the hex code from the default code. Until they do it cant be changed in FR24 because 49D3C7 is OK-JRG

[vader696]

48C484
SP-SEE
msn 2552

[scorp1988]

Unfortunately, I didn't take that into account... that two HEX factories have not been changed. One in Khabarovsk, one in Khanty-Mansiysk. But there is a difference between them: Khabarovsk board has a callsign R3107, Khanty-Mansiysk board has a callsign OKJRG. Maybe there's a way to separate them from each other...

[apgphoto]

43EABB

Operator needs removing, especially as the hex is being miscoded from another aircraft

[hexfan]

Unfortunately, I didn't take that into account... that two HEX factories have not been changed. One in Khabarovsk, one in Khanty-Mansiysk. But there is a difference between them: Khabarovsk board has a callsign R3107, Khanty-Mansiysk board has a callsign OKJRG. Maybe there's a way to separate them from each other...

You are completely IGNORING what people are telling you!

It's very simple :

Each country has its own hex code range. Aircraft registered in that country MUST HAVE A HEX CODE within that range.

498 to 49F = Czech Republic.
140 to 155 = Russia.

Your planes are registered in RUSSIA therefore you need them to have RUSSIAN hex code, not Czech Republic. THERE ARE NO EXCEPTIONS SO STOP ARGUING!

RA-67036 = needs programming with hex code 1505DC
RA-67035 = needs programming with hex code 1505DB
RA-67040 = needs programming with hex code 1505E0
RA-67047 = needs programming with hex code 1505E7
RA-67061 = needs programming with hex code 1505F5

Fix the transponders and they will get added to the database. It is a 5 minute job on each plane. Now go and do it and stop writing angry posts.