Aircraft to be added into Flightradar24 aircraft database

[JamieSteyn]

00937F
ZS-HJI
B06
Bell 206B
3123
NAC Helicopters Cape Town


Sent from my SM-G965F using Tapatalk

[JamieSteyn]

009488
ZS-HTN
FREL
Aerospatiale Super Frelon-SA.321J
169
Executive Helicopters

Sent from my SM-G965F using Tapatalk

[Oblivian]

Yep! I know it is.

A7E0A7 = https://registry.faa.gov/aircraftinq...umbertxt=6065Y

EI/IRELAND 4CA000 4CAFFF Ireland

[JamieSteyn]

0093ED
ZS-HNO
B06
Bell 206B
3294
NAC Helicopters Cape Town

Sent from my SM-G965F using Tapatalk

[JamieSteyn]

00860A
ZS-CGV
B407
Bell 407
53786
NAC Helicopters Cape Town

Sent from my SM-G965F using Tapatalk

[dedevillela]

A00D30
N102LV
GLF4
Gulfstream G-IV
1188
Private owner
1992-00-00

A02D10
N110JW
GLF4
Gulfstream IV SP
1245
Private owner
1994-00-00

[bahamabarbarian]

4074E5
G-DHKT
B752
Boeing 757-233(PCF)
29428
DHL Air
DHK
1998-11-13

[nomad77]

7C338C
VH-KGU
Y18T
YAK-18T
7201613
Private
1977-00-00

[harsh93]

800D2A
VT-MXX
B38M
Boeing 737-8 MAX
60184
SpiceJet
SEJ

2019-01-14

[rik130]

A7E0A7 = https://registry.faa.gov/aircraftinq...umbertxt=6065Y

EI/IRELAND 4CA000 4CAFFF Ireland

Which is Oblivian moderator removing on topic posts from this thread? Explain please.

[Oblivian]

Which is Oblivian moderator removing on topic posts from this thread? Explain please.

I think you mean 'why'

And because 'nope' and a smiley face is in itself off topic without any expanded explanation.

And this post is in itself out of bounds of what Mike requested. Which is clear and concise non overlapping data

There are multiple people, including mashing the report post button continually due to disagreement with others data appearing to use upper-hand tactics and replying without helping educate others. Unlike what I did. Adhering to the first post that
a. requires HEX - which was at first missing totally,
b. Must be a registration within the range matching the designated country hex - in which case yes, is a boeing test hex. And in a month what happens, it needs to be updated to be changed again if it gets entered against this requirement

1 Person already corrected it to add the HEX which was missing. You are the 2nd to point out it can't be added as it is out of country maybe?.. but who knows. It just said 'nope'.
Yet I get called unfriendly to first time posters

Posts are read chronologically by the people entering data. Entering it wrong in the first instance, and quoting the same wrong stuff but and adding minor changes. Rather than go back and edit the first one if the originator. Or remove/blank and leave the corrected one

Pointing out the hex error like I just have, whilst cleaning up the repeated quotations and instances of the same airframe stops anyone else doing a chronological catch up spotting it and doing the same sort of reply as you did.

Everyone goes on about how rubbish the data is and why people are entering the wrong stuff. If multiple posts with the same data adjusted every 3-4 post doesn't exasperate the chance of it, Well. I just don't know.

But by all means. Send off another report/complaint about my actions and apparent abuse of power - but consider my actions this time doing nothing but point out to a new user the data they are providing is not valid to be added at this time as requested.

And at the same time, fine. I'll go back and undelete them now and show everyone else scratching their head reading this how inappropriate the tennis match of single words actually was.

[nomad77]

A8026A
N615MF
C208
Cessna 208 Caravan I
20800615
Missionary Aviation Fellowship
2018-08-00

[nomad77]

7C6B88
VH-VIY
S22T
Cirrus SR22T
1455
Private
2016-00-00

[rik130]

<long reply>

Hi. I don't have any issue with your "actions" whatsoever, not sure where you got that from? But if a post gets deleted then personally I would deem it courteous to at least let the user know why with a good reason, either as an edit in their forum post or via direct mail.

I grant you that my reply to the Glasgow guy was not particularly informative but then I didn't consider it needed to be and was put more as a 'heads up' to Maxi to not change the existing entry which is a fixed Boeing temp reg. He'd have probably realised anyway but I didn't see any harm. If I were to reply to every post submission that is posted with a miscoded or old hex then I'd never get anything else done. Besides, one of the other 'silent' database admins (who I am sure is still Arion/AttentiAllaFretta) seems to round up all the new Boeing hex codes from the Boeing flight test blog site as they're posted and puts them straight in the database without them needing to be posted here so he would have understood what I meant with my short comment as well.

[bahamabarbarian]

781591
B-304L
A333
Airbus A330-343
1893
Hainan Airlines
CHH
2018-08-27