Discussion about Flightradar24 database

[zaibi]

When will the correct icons be set for the various types? There are hundreds, like T38, M600, HDJT, and SF50, still using the UNID icon. Since the proper icons already exist, can’t they just be applied? The UNID icon should be reserved strictly for unidentified frames—using it for everything makes it hard to sort, especially in the U.S. where it's overused.

[arion]

Please change type in the database from R44 to EC35 for the following aircraft
PH-PXA Eurocopter Deutschland GmbH EC135 P2+
PH-PXB Eurocopter Deutschland GmbH EC135 P2+
PH-PXC Eurocopter Deutschland GmbH EC135 P2+
PH-PXD Eurocopter Deutschland GmbH EC135 P2+
PH-PXE Eurocopter Deutschland GmbH EC135 P2+
PH-PXF Eurocopter Deutschland GmbH EC135 P2+
See the pictures

All helicopters that use OGN/FLARM are displayed as being an R44, even if the information is correct in the database, this is not an error, it is intentional on the part of the admin, do not expect this to be corrected at some point.

Please note that these helicopters use another HEX.


PHPXB.png

If you want a standard answer:
support@fr24.com

[ASBvS]

Please change type in the database from R44 to EC35 for the following aircraft
PH-PXA Eurocopter Deutschland GmbH EC135 P2+
PH-PXB Eurocopter Deutschland GmbH EC135 P2+
PH-PXC Eurocopter Deutschland GmbH EC135 P2+
PH-PXD Eurocopter Deutschland GmbH EC135 P2+
PH-PXE Eurocopter Deutschland GmbH EC135 P2+
PH-PXF Eurocopter Deutschland GmbH EC135 P2+
See the pictures

[Greek Aviator]

Hello everyone!

Not sure if I'm on the right channel, but I have recently seen that the Hellenic Air Force icon doesn't appear like other airlines logo appear. (1st photo is how it should be)

[VOHY]

D-EESO is operating under the HEX 3D111A. End of last year D-EESO got a new Transponder, the old Transponder (from D-EESO) was built into D-EDHU.
Both aircraft were now operating under the same HEX 3D111A with different Callsign ID's.

I requested a new HEX for D-EDHU from the German authorities and got assigned HEX 3D0D5.
My avionics guy changed the faulty HEX of D-EDHU for the newly assigned one.

I know that you can't change the HEX, both aircrafts are now individual.
(as of Callsign ID and HEX Code)

If I understand right, D-EDHU should be on display at FlightRadar24 with all the correct information after the next Flight with the new HEX?

"When you have completed a fresh flight in D-EDHU and D-EESO, write here again and the logs can be checked."

[albertmsyring]

There are no records of 3D0D5E active anywhere. 3D111A last record was on 18 May from Kolleda Germany , but transmitting DEDHU, not DEESO.

Again, I ask have you actually hired an avionics guy to recode the transponders on the planes? You keep saying that the German authority have changed your codes, but the German authority does no such thing. All they do is ISSUE you with the paperwork which tells you what your code is, then you have to hire an avionics guy to reconfigure the transponders on the planes to those codes. It's not some magical remote process that the German authority use, nor Flightradar24. All FR24 does is display the hex code being transmitted and received from the plane, then the frame details are displayed for it on the map ONLY if an editor has added those details to the FR database. Germany uses an algorithmic reg > hex code system, so regardless of what info you write here or put in the callsign ID on your transponders, FR will ALWAYS show D-EESO against 3D111A and D-EDHU against 3D0D5E. These can never be changed or overridden because it's a fixed algorithmic system.

When you have completed a fresh flight in D-EDHU and D-EESO, write here again and the logs can be checked.

D-EESO is operating under the HEX 3D111A. End of last year D-EESO got a new Transponder, the old Transponder (from D-EESO) was built into D-EDHU.
Both aircraft were now operating under the same HEX 3D111A with different Callsign ID's.

I requested a new HEX for D-EDHU from the German authorities and got assigned HEX 3D0D5.
My avionics guy changed the faulty HEX of D-EDHU for the newly assigned one.

I know that you can't change the HEX, both aircrafts are now individual.
(as of Callsign ID and HEX Code)

If I understand right, D-EDHU should be on display at FlightRadar24 with all the correct information after the next Flight with the new HEX?

[VOHY]

Okay, I'm going flying now!
Thank you very much, I will reach out if it worked or not!

There are no records of 3D0D5E active anywhere. 3D111A last record was on 18 May from Kolleda Germany , but transmitting DEDHU, not DEESO.

Again, I ask have you actually hired an avionics guy to recode the transponders on the planes? You keep saying that the German authority have changed your codes, but the German authority does no such thing. All they do is ISSUE you with the paperwork which tells you what your code is, then you have to hire an avionics guy to reconfigure the transponders on the planes to those codes. It's not some magical remote process that the German authority use, nor Flightradar24. All FR24 does is display the hex code being transmitted and received from the plane, then the frame details are displayed for it on the map ONLY if an editor has added those details to the FR database. Germany uses an algorithmic reg > hex code system, so regardless of what info you write here or put in the callsign ID on your transponders, FR will ALWAYS show D-EESO against 3D111A and D-EDHU against 3D0D5E. These can never be changed or overridden because it's a fixed algorithmic system.

When you have completed a fresh flight in D-EDHU and D-EESO, write here again and the logs can be checked.

[albertmsyring]

Aircraft is already in the database and it takes about 24 hours for the data to be visible in the search field, but if the aircraft in question does not have the correct data in the transponder it will be useless to have the data in the database. And since this aircraft has not yet made any flights apparently using this new HEX.

Okay, I'm going flying now!
Thank you very much, I will reach out if it worked or not!

[arion]

The aircraft D-EDHU isn't registered yet in the FlightRadar24 database - not found on the search function on the website.
I got the HEX for D-EDHU (assigned by the German authorities) -> 3D0D5E

I want this aircraft with its corresponding HEX to be included in the database for easier locating and tracking.

D-EESO should have no relevance for this change, since it's a different aircraft and D-EDHU was falsely operating under D-EESO HEX. No changes needed for D-EESO!


3D0D5E
D-EDHU
C150
Reims Cessna 150H
0236
Private
1967-05-00

P.S. Unknown Paint code and no Operator code

These are all the correct information for D-EDHU.
I hope you got all informations needed for the database registration for D-EDHU.

Best regards Albert M.

Aircraft is already in the database and it takes about 24 hours for the data to be visible in the search field, but if the aircraft in question does not have the correct data in the transponder it will be useless to have the data in the database. And since this aircraft has not yet made any flights apparently using this new HEX.

https://www.flightradar24.com/data/aircraft/d-edhu

[albertmsyring]

Just one question, does the aircraft already have the correct HEX on the transponder, which was designated by the German authorities?
3D0D5E>D-EDHU

The aircraft D-EDHU isn't registered yet in the FlightRadar24 database - not found on the search function on the website.
I got the HEX for D-EDHU (assigned by the German authorities) -> 3D0D5E

I want this aircraft with its corresponding HEX to be included in the database for easier locating and tracking.

D-EESO should have no relevance for this change, since it's a different aircraft and D-EDHU was falsely operating under D-EESO HEX. No changes needed for D-EESO!


3D0D5E
D-EDHU
C150
Reims Cessna 150H
0236
Private
1967-05-00

P.S. Unknown Paint code and no Operator code

These are all the correct information for D-EDHU.
I hope you got all informations needed for the database registration for D-EDHU.

Best regards Albert M.

[albertmsyring]

Just one question, does the aircraft already have the correct HEX on the transponder, which was designated by the German authorities?
3D0D5E>D-EDHU

Correct, D-EDHU 3D0D5E.
The HEX was assigned to the Transponder today.

[arion]

D-EESO with HEX 3D111A is correct.
D-EDHU needs a complete new FlightRadar24 registration with the newly assigned HEX 3D0D5E.

Just one question, does the aircraft already have the correct HEX on the transponder, which was designated by the German authorities?
3D0D5E>D-EDHU

[albertmsyring]

You cannot just swap the transponder from one plane to another if it's a different registration (in the case of Germany). The transponder hexadecimal value needs reprogramming by an avionics technician to the correct hex - in this case 3D0D5E for D-EDHU. As of yesterday the transponder was still transmitting invalid hex 3D111A. Also, one of the transponders is still transmitting the old callsign DEESO so this needs reprogramming by the pilot. The 2nd transponder is correctly transmitting DEDHU, but both devices are still configured with invalid hex codes.

D-EESO with HEX 3D111A is correct.
D-EDHU needs a complete new FlightRadar24 registration with the newly assigned HEX 3D0D5E.

[albertmsyring]

You cannot just swap the transponder from one plane to another if it's a different registration (in the case of Germany). The transponder hexadecimal value needs reprogramming by an avionics technician to the correct hex - in this case 3D0D5E for D-EDHU. As of yesterday the transponder was still transmitting invalid hex 3D111A. Also, one of the transponders is still transmitting the old callsign DEESO so this needs reprogramming by the pilot. The 2nd transponder is correctly transmitting DEDHU, but both devices are still configured with invalid hex codes.

I think I figured it out.

There are two aircrafts, D-EESO and D-EDHU. D-EESO recently got a new transponder. D-EDHU got the old Transponder from D-EESO. At that time both were operating under the same HEX. Recently I got assigned a new HEX for D-EDHU from the German authorities (3D0D5E).
D-EESO is fine - no changes needed!
D-EDHU is in need of a complete new FlightRadar24 registration with HEX (3D0D5E) - since it's a brand new HEX.

Sorry for my confusion - I think now it is clear?

[VOHY]

Okay, I think I am misunderstanding. The Transponder was just changed from the aircraft D-EESO to D-EDHU. The old HEX 3D111A (D-EESO) got changed today for the new assigned by the German authorities 3D0D5E (D-EDHU).

You cannot just swap the transponder from one plane to another if it's a different registration (in the case of Germany). The transponder hexadecimal value needs reprogramming by an avionics technician to the correct hex - in this case 3D0D5E for D-EDHU. As of yesterday the transponder was still transmitting invalid hex 3D111A. Also, one of the transponders is still transmitting the old callsign DEESO so this needs reprogramming by the pilot. The 2nd transponder is correctly transmitting DEDHU, but both devices are still configured with invalid hex codes.