Aircraft to be added into Flightradar24 aircraft database

[dedevillela]

A023EE
N108RL
H25B
Raytheon Hawker 800XP
258619
BISON AERONAUTICS LLC
2003-00-00

[dedevillela]

A02C73
N110CP
CL60
Bombardier CL-600-2B16 Challenger 605
5801
PRUITT CORP
2009-00-00

[dedevillela]

A32087
N300NJ
CL30
Bombardier BD-100-1A10 Challenger 300
20013
PUNTA PACIFICO I LLC
2004-00-00

[dedevillela]

A515AB
N427AL
B429
Bell 429 Global Ranger
57025
SOUTHERN AVIATION SYSTEMS LLC

[dedevillela]

ABE21C
N865HC
C525
Cessna 525 CitationJet CJ1+
525-0616
HOLLINGSWORTH INTERGALACTIC LLC
2006-00-00

[vader696]

4895EF
SP-FPP
PA31
Piper PA-31-350 Navajo Chieftain
31-8152010
MGGP Aero
1981

[swifty]

7C7BC2
VH-YQC
C152
Cessna 152
15283703
Eastern Air Services pty
Year 1979

[vader696]

49D34E
OK-CHR
C172
Reims Cessna F172N Skyhawk II
1571
Aeroklub CR Chrudim
1977

49D0F1
OK-AKJ
R22
Robinson R22 Beta II
3569
LPS
2004

[swifty]

Aircraft Change
N907WS
GL5T
BD700 Global 5000
9176
N907WS Aviation llc
Year 2005
EX N720WS

A2603D
N252PM
PAY2
PA31T Cheyenne 2
31T8120056
Aircraft Guaranty Corp Trustee
Year 1981

[F-KRNT2]

Further to my last post regarding submitted content being deliberately changed to incorrect data in the database, it's been pointed out to me that this amateur blogging website is the source of the problems. I have just looked through the pages and I haven't found one yet which is not full of errors. In addition to my earlier post regarding Aeroflot 737 VQ-BHC I note that is it shown inccorrectly on that blog site as VP-BHC too so that presumably explains why the database here still shows it incorrectly as VP-BHC despite my making the correction for a second time some days ago, even though the tie-up was posted here correctly well in advance of it even flying.

Furthermore, the most recent Ryanair frame to fly - EI-GJN - is in the database already under hex code 4CACC7 yet this hex code does not even exist! Once again, a check of the aforementioned blog site and we find the source! If the database editor(s) had bothered to perform even the most basic level of research they would have found within a few minutes on the playback function that the correct hex code for the frame is in fact 4CACDB. It is quite clear that 4CACC7 was posted as nothing more than a guess based on the previous frame EI-GJM being 4CACC6.

I question once again why these sub forums even exist if the site owner and database editor(s) completely ignore submissions from contributors, most of whom have clearly done their research before posting and/or have close connections to the manufacturers/hex code issuing bodies and other reliable sources. Again, if the database editor(s) know better than at least have the courtesy to make a post here stating that user contributions are no longer required and save us the time and bother.

The deathly silence emanating from the site owner(s) on this matter speak volumes in itself. At the very least the database editor(s) responsible for this should be immediately removed from the team before any lasting damage is done.

[vader696]

48FEE9
SP-SMYK
WT9
AeroSpool Dynamic WT9 NG
DY310/2009
private owner
2009

49D346
OK-CVR
C172
Reims Cessna F172H Skyhawk
0294
private owner
1977

[Xanderix]

A0EEA3
E145
Embraer ERJ-145
145056
6V-AJC
Transair

A1161E
E145
Embraer ERJ-145
145045
6V-AJB
Transair

Both still use their US registration hex#

[arion]

Further to my last post regarding submitted content being deliberately changed to incorrect data in the database, it's been pointed out to me that this amateur blogging website is the source of the problems. I have just looked through the pages and I haven't found one yet which is not full of errors. In addition to my earlier post regarding Aeroflot 737 VQ-BHC I note that is it shown inccorrectly on that blog site as VP-BHC too so that presumably explains why the database here still shows it incorrectly as VP-BHC despite my making the correction for a second time some days ago, even though the tie-up was posted here correctly well in advance of it even flying.

Furthermore, the most recent Ryanair frame to fly - EI-GJN - is in the database already under hex code 4CACC7 yet this hex code does not even exist! Once again, a check of the aforementioned blog site and we find the source! If the database editor(s) had bothered to perform even the most basic level of research they would have found within a few minutes on the playback function that the correct hex code for the frame is in fact 4CACDB. It is quite clear that 4CACC7 was posted as nothing more than a guess based on the previous frame EI-GJM being 4CACC6.

I question once again why these sub forums even exist if the site owner and database editor(s) completely ignore submissions from contributors, most of whom have clearly done their research before posting and/or have close connections to the manufacturers/hex code issuing bodies and other reliable sources. Again, if the database editor(s) know better than at least have the courtesy to make a post here stating that user contributions are no longer required and save us the time and bother.

The deathly silence emanating from the site owner(s) on this matter speak volumes in itself. At the very least the database editor(s) responsible for this should be immediately removed from the team before any lasting damage is done.

Hi


https://www.flightradar24.com/data/aircraft/vq-bhc *** I have already updated this information again.

I have added this aircraft correctly as VQ-BHC and someone is changing not only these several more information erroneously.

B-1235 and B-1253 ***Same thing happened to these aircraft.

VQ-BHC
VQ-BHD

[vader696]

4701C9
HA-ARP
C172
Cessna 172R Skyhawk II
17280336
RivAir
1998

[arion]

A0EEA3
E145
Embraer ERJ-145
145056
6V-AJC
Transair

A1161E
E145
Embraer ERJ-145
145045
6V-AJB
Transair

Both still use their US registration hex#

Hi

Message from Mike/Administrator

All hex codes starting with Axxxxx are US registrations and they will always remain with US N-registration in our database.
It's up to the aircraft owner to fix the correct transponder ID when transferring the aircraft to new registry.

https://forum.flightradar24.com/threads/1871-Data-errors-in-Flightradar24-aircraft-database?p=103256#post103256