Aircraft to be added into Flightradar24 aircraft database

[apgphoto]

8A0690
PK-APN
C172
Cessna 172S Skyhawk SP
172S11775
Private
2016

[NorskeTroll]

08008d
5H-NAC
C208
Cessna 208B Grand Caravan
208B-0757
Safari Air Link
1999

[bahamabarbarian]

781666
B-209X
B789
Boeing 787-9 Dreamliner
63983
China Southern Airlines
CSN
CZ
2019-05-17

[bahamabarbarian]

872720
JA900A
B78X
Boeing 787-10 Dreamliner
62684
All Nippon Airways
ANA
NH
2019-02-08

Originally delivered with the hex code 872812, which it used up to May 2nd.

[Oblivian]

Here we go again



Sent from my EML-L09 using Tapatalk

[apgphoto]

3007D3
I-ECJX
B505
Bell 505 JetRanger X
65218
Private
2019

[apgphoto]

4247DE
VP-CHE
A139
Agusta Westland AW139
31475
Private
2013

[apgphoto]

758176
RP-C2954
B350
Beech 350 King Air
FL-393
Private
2004

75828F
RP-C7574
C208
Cessna 208B Grand Caravan
208B2328
Private
2011

[bahamabarbarian]

7816C4
B-308S
A20N
Airbus A320-271N
8981
Air China
CCA
CA
2019-05-16

[bahamabarbarian]

7816B5
B-308M
A359
Airbus A350-941
311
Air China
CCA
CA
2019-05-13

[bahamabarbarian]

7504AF
9M-RAQ
A20N
Airbus A320-251N
8991
AirAsia
AXM
AK
2019-05-20

[40612]

Here we go again



Sent from my EML-L09 using Tapatalk

I've not been following this story, but for the record, JA900A first flew 2019-02-08 using hex 872720 and callsign BOE116.

It's been using 872720 ever since.

872812 hasn't been logged at all, as far as I can see.

Presumably this is miscode by Boeing?

[hexfan]

I've not been following this story, but for the record, JA900A first flew 2019-02-08 using hex 872720 and callsign BOE116.

It's been using 872720 ever since.

872812 hasn't been logged at all, as far as I can see.

Presumably this is miscode by Boeing?

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 .

[40612]

Thanks for the explanation.

[czejen]

[ATTACH=CONFIG]10589[/ATTACH][ATTACH=CONFIG]10590[/ATTACH]

Hello, please add one new aircraft and update one of existing one. Thanks

New one

49C1FC
OK-YAI24
NG5
Bristell ELSA
428/2019
KLIFI sro
White / blue (no ICAO code, picture attached)
LKLB
2019-02-15

Upadte:
49D169
OK-JTV
C182P
Cessna 182P Skylane
Aeroklub Liberec
White (no ICAO, picture attached)
LKLB
1975

49C1FC OK-YAI24 still not visible on radar