Data errors in Flightradar24 aircraft database

[AirMe]

A42323
N366FR
Frontier (Kit the Kermode Bear Livery)

A426DA
N367FR
Frontier (Austin the Northern Mockingbird Livery)

4CAAF1
EI-EIK
Aer Lingus
2006-09-28

34214A
AT75
ATR 72-500(F)
CNF

702078
S2-AIJ
2006-06-22

0200F8
CN-RGJ
Royal Air Maroc (Oneworld Livery)
RAM

4D00F6
LX-LGU
B738
Luxair (Sumo Artwork's Livery)

Aircrafts to be blanked:

AsiaCargo Express: 9M-GSB (7502D1)

Regent Airways: S2-AIJ (702078)

TAG Aviation: G-TCSX (406BE7)

China Southern: B-20E8 (78188A) stored at VCV with BOE code

Paranair: ZP-CRN (E88024)

[Oblivian]

50016F
ICAO EC45

ALL BK-117D are EC45

https://www.flightradar24.com/data/aircraft/zk-ivb
B-2 been changed to EC45 too :/

[T-EDDL262]

ModeS/Hex-code - correct 3FF768 --> wrong 3FECC3
Registration D-MOIN
ICAO Z602
Type code - Microlight Roland Aircraft Z602
Type Microlight

Identification was transfered by acquiring new plane (D-MOIN) but Hex Code was changed from 3FECC3 to 3FF768
FR24 still shows all flights under DMOIN with Hex Code 3FECC3 and does not list any on 3FF768

This causes the issue that there are now two planes "using" 3FECC3 (DMNHA, maybe correct now, and DMOIN now wrong as registered with 3FF768)

Please correct :-)

O;,
thanks to the Team for fixing the HexCode. :-)

However still there is a wrong identification connected to the HexCode 3FF768 and is obviously a plane flying in the southern part of Germany.....
DMNHA is a different Aircraft and so owner.
Please remove DMNHA from the HexCode 3FF768
it might be that DMNHA is now using the old Hex 3FECC3 but this is out of my knowledge.


Thanks

[_toni]

3FF768

is now associated to D-MOIN.

[WayneKing]

https://www.flightradar24.com/data/aircraft/zk-ivb
B-2 been changed to EC45 too :/

And also to Airbus H-145

[WayneKing]

320035
VF-84 or I-DFVE as you prefer
Agusta A109E Power

[40612]

Spam reported

[Spola27]

440554
OE-AAC
C152
Reims F152
F15201940
Private owner


440267
OE-AAD
C152
Cessna 152
15285432
Private owner

[T-EDDL262]

3FF768

is now associated to D-MOIN.

I know, but still there is another registration (D-MNHA) that is nothing to do with 3ff768 which is D-MOIN
As I am the owner of D-MOIN I don't like to see another registered aircraft on the same Transponder Code! In case of any legal misshaps of the owner of D-MNHA I do not want to get associated with this....

[Oblivian]

Fr24 can't do anything about an owner not reprogramming a transponder.

[T-EDDL262]

Fr24 can't do anything about an owner not reprogramming a transponder.

Dear Oblivian,

You did not understand the issue, right? Did you? You already wrote that once but later deleted your post after I replied that I am pretty convinced the problem is on your side as I am the owner of D-MOIN.......

The Problem is not the Owner, the problem is the way FR24 takes care of the Database!
Simply you mix history with current situation.....

Previously HEX 3FECC3 WAS!!!! the HEX code of D-MOIN

D-MOIN was de registered (due to sale, registration did not go to the new owner and he registered as D-MTTM Hex 3FF738.) and the HEXCode 3FECC3 was deleted by authority!

Then D-MOIN was new registered (as it is a new Airplane now, coming from Luxembourg) and HEX Code 3FF768 was new assigned to it by authority!

All records beginning 2019 of D-MOIN have used 3FF768 then, all flights prior 2019 of D-MOIN have used 3FECC3

The authority obviously decided to assign the old HEX Code 3FECC3 now to D-MNHA.

I do not know the owner, nor am I affiliated as owner of D-MOIN to D-MNHA.

All I am telling you is, that your database entry is false and you are not filtering correctly.

My demand is to simply erase D-MNHA from Transponder HEX Code 3FF768 as D-MNHA is using 3FECC3 obviously now.......

it is the same you would use the same Number plate for two different cars, one in Sweden one in France......

[WayneKing]

To the DB editor that has no idea about country to hex tie ups

388B7B is a French code its not Italian https://www.flightradar24.com/data/aircraft/i-miat

Please refer to Oblivian's handy guide that translates hex to country 388B7B is ferry reg F-WTAJ

Why are all these miscodes being added to the DB has their been a change of policy? Or should we just look at my first sentence?

[Oblivian]

All I am telling you is, that your database entry is false and you are not filtering correctly.

No. Don't understand.

Perhaps take screenshots of what you think needs changing on the records to describe better.

Using the URLs they are as you describe.

https://www.flightradar24.com/data/aircraft/D-MNHA = 3FECC3 (no history)

https://www.flightradar24.com/data/aircraft/d-moin = 3FF768 (merged history)

https://www.flightradar24.com/data/aircraft/d-mttm = 3FF738


You obviously saw the deleted replies email and information. That was intended. Posts like these trying to over-complicate explain things and not like the required data format on page 1 are not allowed.

Editors don't chang historic flight data under a HEX from these threads

Only adjust the registration, owner and type information on a plane record against a HEX (the primary key) it sends. Not the flight data.

If you find any errors in FR24 aircraft database you can post the errors and correct data here. It could be wrong registration, wrong plane type, wrong airline or any other aircraft data error.

Feeders send received information to the server: HEX. Callsign from transmitter if present, altitude and position. Not reg.

The server then matches the HEX to saved owner/registration record for live display. And saves copy for historic playback.
It cannot easily tell when transponder->registration swaps happen while keeping same country range.

And if 2 send the same HEX (where the new owner of an old airframe does not recode) for a period. There is no way to tell which registration is right. And the history/flight data often gets merged

[_toni]

No. Don't understand.

Perhaps take screenshots of what you think needs changing on the records to describe better.

Using the URLs they are as you describe.

https://www.flightradar24.com/data/aircraft/D-MNHA = 3FECC3 (no history)

https://www.flightradar24.com/data/aircraft/d-moin = 3FF768 (merged history)

https://www.flightradar24.com/data/aircraft/d-mttm = 3FF738


You obviously saw the deleted replies email and information. That was intended. Posts like these trying to over-complicate explain things and not like the required data format on page 1 are not allowed.

Editors don't chang historic flight data under a HEX from these threads

Only adjust the registration, owner and type information on a plane record against a HEX (the primary key) it sends. Not the flight data.



Feeders send received information to the server: HEX. Callsign from transmitter if present, altitude and position. Not reg.

The server then matches the HEX to saved owner/registration record for live display. And saves copy for historic playback.
It cannot easily tell when transponder->registration swaps happen while keeping same country range.

And if 2 send the same HEX (where the new owner of an old airframe does not recode) for a period. There is no way to tell which registration is right. And the history/flight data often gets merged

Oblivian and @T-EDDL262 Please stop all discussion here, there are threads designated for discussion. All future posts will be deleted.
FR24 cannot control if some aircraft is miss coding or using its former transponder hexcode. What can happen in that case that flights of both AC will be logged under one registration, which is the case here.

[_toni]

To the DB editor that has no idea about country to hex tie ups

388B7B is a French code its not Italian https://www.flightradar24.com/data/aircraft/i-miat

Please refer to Oblivian's handy guide that translates hex to country 388B7B is ferry reg F-WTAJ

Why are all these miscodes being added to the DB has their been a change of policy? Or should we just look at my first sentence?

You are correct, I-MIAT was definitely added by mistake, as many non matching hex codes are posted here in the thread.

NOTE to all forum and database editors: Please refer here in order to check that the registration is matching hexcode country range: http://www.mantma.co.uk/icao_country_codes.html

Thank you.