485BB5, a RV12 with registration PHIIX: could you please add First Flight Date 2020-02-06 and registered in the Netherlands. Thanks for your help.
Announcement
Collapse
No announcement yet.
Data errors in Flightradar24 aircraft database
Collapse
This is a sticky topic.
X
X
-
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)
Comment
-
Originally posted by WayneKing View Post50016F
ICAO EC45
ALL BK-117D are EC45
B-2 been changed to EC45 too :/Posts not to be taken as official support representation - Just a helpful uploader who tinkers
Comment
-
Originally posted by T-EDDL262 View PostModeS/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 :-)
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
Comment
-
Originally posted by _toni View Postis now associated to D-MOIN.3FF768
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....
Comment
-
Originally posted by Oblivian View PostFr24 can't do anything about an owner not reprogramming a transponder.
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......
Comment
-
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 country388B7B 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?
Comment
Comment