Aircraft to be added into Flightradar24 aircraft database

[user12345]

N426DX showing on FR24 should be
N426DZ
A330-9
2045
Delta AL

info from FAA database

GTF4J2M

it's miscoded from the factory. Another editor has entered it incorrectly. I've cleared the fields and should update soon.

[pzl104]

This is my first post here, hope that my entry is correct:
I was wondering why the PC-12NGX I uploaded at Jetphotos a week ago doesn't show up here until it occured to me that it might not be in your database at all.
That's the info I can provide:

3D4E36
D-FBWG
PC12
PC-12NGX
2331
Private

[pzl104]

OE-VPU isn't a DA40 anymore as shown on FR24, but a DA50. This is pretty misleading, seeing a DA50 while the text says DA40.

4400A7
OE-VPU
DA50
DA-50C
50.C.A.A.045
Diamond Aircraft Industries

[pzl104]

OE-UDW isn't a DA42 as shown on FR24, but a DA50. This is pretty misleading, seeing a DA50 while the text says DA42.

4401AB
OE-UDW
DA50
DA-50C
N/A
Diamond Aircraft Industries

[trabin]

48A481
SP-KEB
PC12
Pilatus PC-12 NGX
c/n 2326
Private owner
Year of manufacture 2023

[user12345]

OE-UDW isn't a DA42 as shown on FR24, but a DA50. This is pretty misleading, seeing a DA50 while the text says DA42.

4401AB
OE-UDW
DA50
DA-50C
N/A
Diamond Aircraft Industries

It's a Diamond flight test registration. They are not assigned to any specific frame. It's in as a DA42 simply so that it shows a somewhat related icon on the map. Without any type code then it would show as the default 737 icon then everyone would complain about that too. I have changed the full type to Diamond (various models) which will suffice.

[jhicks7]

This is my first post here, hope that my entry is correct:
I was wondering why the PC-12NGX I uploaded at Jetphotos a week ago doesn't show up here until it occured to me that it might not be in your database at all.
That's the info I can provide:

3D4E36
D-FBWG
PC12
PC-12NGX
2331
Private

Added all info and updated completely! Hopefully your photo will link up within the next 48 hours or so!

[pzl104]

It's a Diamond flight test registration.

Thanx a lot for your reply. To be a bit more precise, flight test registrations start with a V. (Versuch) U (Überstellung) are transfer registrations.
Presently there are 3 different airplanes at LOAN with the identical OE-VDR registration. This leads to very serious problems and complaints at Austro Control if 2 are active at the same time, something which definitely shouldn't happen.

[flYellow GmbH]

3D4A70
D-FALC
PC12
Pilatus PC-12NG
1689
Privat
2017-02-01

[user12345]

We are the owner/operators of this aircraft. We do not have it blocked. How can we get it unblocked? Can we use our call sign XLJ612 in place of registration #?

It is logging now . https://www.flightradar24.com/data/aircraft/n612fa

[user12345]

Thanx a lot for your reply. To be a bit more precise, flight test registrations start with a V. (Versuch) U (Überstellung) are transfer registrations.
Presently there are 3 different airplanes at LOAN with the identical OE-VDR registration. This leads to very serious problems and complaints at Austro Control if 2 are active at the same time, something which definitely shouldn't happen.

Thanks. What I was trying to explain (badly, it seems!) is that from our side, these are NOT fixed registrations and are recycled onto other frames as and when needed for flight tests and delivery ferry flights. The registrations and hex codes for them are fixed (thankfully) but the types on them vary, so as we don't have the time nor inclination to be monitoring the Diamond Aircraft Industries activities on a daily basis, we have a couple of realistic (for us) options in how to index them :

1. we can just put the hex code and reg in and leave the type code and model as blank. This would mean that all flights would show as the default 737 icon on the map.
2. we can choose one of their type codes (DV20, DA40, DA42, DA50 etc) and apply it to the reg so that it at least shows a prop icon on the map, although of course if we put DA42 and it's actually a DA40 flying then that wouldn't be right either, but at least it's closer than a 737 !

If you prefer, we can remove the type codes and leave them blank.

[@eb4ewl]

34768B
EC-OFT
P06T
Tecnam P2006T
285
Aerotec
2019

[pzl104]

What I was trying to explain (badly, it seems!) is that from our side, these are NOT fixed registrations

If you prefer, we can remove the type codes and leave them blank.

You didn't explain it badly at all!

Everything is fine the way it is. FR24 is my most used app on my mobile and PC. Great work and thanx for your and the teams effort.

[trabin]

48908F
SP-EEP
M600
Piper M600/SLS
c/n 4698278
Private owner
Year of manufacture 2023

[Gareth Whitehead]

710385
HZ-116
VC-130H
c/n 4915
Royal Saudi Air Force
This aircraft was r/r from HZ-116 to 486 back in 2013. If you can update the reg/serial it would be appreciated.
Many thanks
Gareth