Aircraft to be added into Flightradar24 aircraft database

[harsh93]

800D78
VT-SYH
B738
Boeing 737-85R
42799
SpiceJet
SEJ
2014-06-25


800D7E
VT-SYN
B738
Boeing 737-85R
42804
SpiceJet
SEJ
2014-08-29


800D8F
VT-SYS
B738
Boeing 737-8AL
39064
SpiceJet
SEJ
2014-02-09

[nomad77]

A9EA07
N738NZ
SR22
Cirrus SR22
4738
Cirrus Design Corp
2019-00-00

[dedevillela]

C01F5A
C-FLWR
C25C
Cessna 525C CitationJet CJ4
525C0202
Private owner
2015-00-00

[Phil1122]

AC7797
N902LC
EXPL
MD-900 Explorer
900-00118
Airline: Cox Air Care
2007-00-00

AC70FA
N900UM
EXPL
MD-900 Explorer
900-00112
Airline: University of MO Staff for Life
2006-00-00

[Phil1122]

ACF932
N935MC
EC35
Airbus Helicopters H135
0485
Airline: Metro Aviation Corporation
2006-00-00

[bsu3]

39280F
F-GKAP
P28A
Piper PA-28-161 Warrior II
MSN 28-8216072
PRIVATE
1982-00-00

[bsu3]

384684
F-BRUE
P28R
PIPER AIRCRAFT CORP. PA 28 R 200
MSN 28R35364
Aéroclub les Aiglons Lognes
1969-00-00

[bsu3]

38BE1B
F-AZQZ
DHC1
Aircraft: De Havilland Canada DHC-1 Chipmunk T.10
MSN: WZ-878
ARMOR AERO PASSION
1953-00-00

[Edilson.Carlos]

E4954B
PP-VSS
FA7X
Dassault Falcon 7X
142
Private
2011

[AirMe]

872720 is the hex code that both Boeing and ANA have been issued with from the Japan CAA regulators. That is what they have to install on the plane which they have done. The Japan hex:reg algorithm shows that it *should* be using 872812 if it follows in sequence. For reasons unknown, the Japan CAA seem to disagree. We have seen this before with South Africa which suddenly changed the allocation rules so maybe Japan has done the same. There is no obvious typo in either the decimal or binary codes.

The bottom line is that 872720 falls outside of the known Japan hex:reg algorithm so there can never be any conflict, ergo there is no reason whatsoever why the plane cannot be filed under 872720 in the database other than site administrators refusing to apply some common sense and rigidly enforcing the rules "because I say so". If there was potential for conflict with another frame then I would be the first to back them but in this case there is not. Much the same as the recent farce with the Vanilla A320 and JTA 737 which are using each other's hex codes, however common sense did eventually prevail there after 6 months of arguing .

Their next frame JA901A is also using an out of sequence hex code (872742) when if following the known algorithm one would expect it to be 872834. I see that this one is already in the database filed under its "unofficial" code and no-one has questioned it. Again, there is no conflict with anything else so hopefully the resident "expert" database editors in Brazil and Sweden don't delete it and instead apply some common sense otherwise there will be 6 months of forum arguments and repetitive posts requesting this one to be added as well .

I totally agree. It is also not correct because there are users for who pay FR24 to see the aircraft history and now they can't because the aircraft is not on the database.

[AirMe]

48D247
SP-WTH
C172
Cessna R172 Hawk XP II
Private owner
Private owner
MSN: R1722799

A27ECA
N26Y
M20T
Mooney 20TN Acclaim
Private owner
Private owner
MSN: 31-0086

[@eb4ewl]

343206
EC-KQV
P68
Vulcanair P68TC Observer
444-08/OTC
SAETA
2008




A8F5B8
n/a
P68
Vulcanair P68TC Observer
447-09OTC
SAETA
2009

[dedevillela]

A13EF2
N18GJ
LJ45
Learjet 45
45-442
Private owner
2012-00-00

[nomad77]

C8282E
ZK-TBJ
ECHO
Tecnam P92 Tail Dragger UL
1591
Private
2019-05-00

[nomad77]

C8282D
ZK-TNZ
ECHO
Tecnam P92 Eaglet UL
1590
Private
2019-05-00