Discussion about Flightradar24 database

[AirMe]

Interesting... there are probably a few hundred aircraft that aren't following this rule then, just as a heads up. Many police departments, highway patrols, and other county/state/federal departments. None of the others I have seen adhere to this, except strict military aircraft such as the Army, Air Force, Navy, etc. Which was the only reason I brought it up.

Yes, you're right. The ones that not "follow the rule" is because they were added in the database before it was implemented. Slowly, they all will have the correct name.

[jhicks7]

No, I'm sorry, but "United States" can't be removed. Aircraft who belongs to public authorities or military forces should have the country name before the autority/force with a dash between them. Same as Jetphotos, as you can see. This is a FR24 internal rule, so it can't be changed.

Interesting... there are probably a few hundred aircraft that aren't following this rule then, just as a heads up. Many police departments, highway patrols, and other county/state/federal departments. None of the others I have seen adhere to this, except strict military aircraft such as the Army, Air Force, Navy, etc. Which was the only reason I brought it up.

[AirMe]

A27E80
N26VA
Virginia State Police

The owner has been updated from private owner, but to "United States - Virginia State Police" instead of the originally stated correction. Can you remove the United States portion, please? Otherwise, it potentially seems to imply the US government owns this aircraft. Thanks!

No, I'm sorry, but "United States" can't be removed. Aircraft who belongs to public authorities or military forces should have the country name before the autority/force with a dash between them. Same as Jetphotos, as you can see. This is a FR24 internal rule, so it can't be changed.

[DB Editor]

Could the icon for the Boeing B17 be corrected? Aircraft G-BEDF gets a large following whenever it flies and although the type designator in the database is correct (B17) the icon on FR24 shows a helicopter.

I've raised the issue with the site admin and owner. Nothing I can do here as the icons are coded by the devs There is a big overhaul for all the icons planned before the end of the year but because of how they were originally implemented it's not a quick process and they need reworking from scratch.
Update: Unfortunately it is not possible for any icons to be changed until the rework now.

[Dakkman]

Could the icon for the Boeing B17 be corrected? Aircraft G-BEDF gets a large following whenever it flies and although the type designator in the database is correct (B17) the icon on FR24 shows a helicopter.

[Oblivian]

"Aircraft registration marks in Australia are changing to include a new alphanumeric system.

We use the VH Australian Nationality Mark followed by 3 alpha characters. Soon we will be introducing a 3-character alphanumeric combintion such as VH-2AB, VH-A9B, VH-A22.


Introducing a 3-character alphanumeric system will mean the availability of more than 20,000 additional marks"

[edwinT]

Definition of Operator.
For example Corendon use a lot of wet-leased planes. Sometimes I see as operator Corendon, sometimes AirExploire / DAT etc. (The ACMI Compagny).
What is the definition of ‘ operator’? expect Flightradar24 the ACMI company (e.g. AirExploire) or Corendon as operator in this case?

[DB Editor]

Hex 4BB565 TC-MKE
and 4BB57A TC-MKZ
are NTU by Corendon
but in Flightrader24 they are not grey
as ‘correction’ blog has gone,
and ‘add new plane’ I can not use, because plane is not in use at the moment by new user
how it can be corrected?
#badenglish

TC-MKZ has been blanked. TC-MKE has been updated to its new frame. Changes on the live site will take effect within 24 hours.

[edwinT]

Hex 4BB565 TC-MKE
and 4BB57A TC-MKZ
are NTU by Corendon
but in Flightrader24 they are not grey
as ‘correction’ blog has gone,
and ‘add new plane’ I can not use, because plane is not in use at the moment by new user
how it can be corrected?
#badenglish

[NorskeTroll]

The Russian authorities will no longer publish aircraft data in the public domain. How do administrators plan to validate data? Or will they fly "noname"?

[prospero]

Be advised that Las Vegas McCarran Airport was renamed Harry Reid International Airport Las Vegas on December 14, 2021 but you are still showing the old name on the FR24 map and on any aircraft travelling to and from LAS.

[lake]

Serial Number (MSN) 510-0471 has changed from D-ISSS to N510RP.

[Vroom]

My reference to height was only as a response to a comment that was made almost implying a paramotor wasn’t going to be seen above 1000’ AGL. Also, where you say “what I’m asking for…” isn’t what I’m asking for, it’s what already exists. Unregistered craft with EC devices now number in there figures in the UK and growing. We didn’t ask for it, the CAA wanted us to take it up and incentivised us to do so.
I have no issue with not being on your database but had thought that it might be of interest for users of FR to know why that symbol that looks like a 737 has such an unbelievable groundspeed! I have what I want from my SkyEcho2 which is the direct communication with other aircrafts ADSB in so I show up on their display, that’ll just do fine.

[DB Editor]

I think you have possibly missed my earlier reply above.

While I understand this line has worked fine in the past it is going to leave your database very incomplete as we move forward and find that the drive to mandate electronic conspicuity results in hundreds (and potentially thousands in UK alone) ADSB devices in unregistered machines utilising the full expanse of class G in the middle of all the other traffic. It doesn’t really matter from our perspective as we will still have the device to device communication but it will leave a lot of unknown pain for users of your service. If you have no desire to include then that’s fine but it will be interesting to see what happens as the unrecognised contacts grow in numbers.

I think you are grossly overestimating the number of users that would care. Even if the hex codes were somehow added to the database, the number of users that would be bothered about a paramotor with a completely meaningless fake "registration" could probably be counted in single digits. If the number of contacts did ever reach the thousands that you anticipate, I expect 1 of 2 things would happen :

1. all hex codes in the 425 range would be given a generic ICAO like PARA and the rest of the fields blocked in the editor.
2. all hex codes in the 425 range would be blocked at source and simply not appear on the map.

Unless the CAA decides to give you proper valid registrations and changes the rules so that the transponders must be fixed to that registration and not be transferred to / used in other craft, my prediction is that #2 will probably happen at some point in the future, purely because they'll become too much of a pain in the ass to deal with.

[Vroom]

The site shows the correct range of a reg for the provided hex.

Flight tracker databases are built around.primary keys. HEX and a tied Registration. And correct country allocation/use of them preventing duplication.

So wouldn't be holding hope to see them added anytime soon if that's suddenly the case.

While I understand this line has worked fine in the past it is going to leave your database very incomplete as we move forward and find that the drive to mandate electronic conspicuity results in hundreds (and potentially thousands in UK alone) ADSB devices in unregistered machines utilising the full expanse of class G in the middle of all the other traffic. It doesn’t really matter from our perspective as we will still have the device to device communication but it will leave a lot of unknown pain for users of your service. If you have no desire to include then that’s fine but it will be interesting to see what happens as the unrecognised contacts grow in numbers.