Safesky produces wrong Hex Code for my plane

English
1

Safesky determins a wrong Hex Code for our plane when doing this:

Settings > My aircraft > Callsign > Turn on the Transponder button-> (type FLARM).

We could figure out that this wrong Hex Code is also wrongly assigned to our plane by flightradar24 while other Flight Trackers like airnavradar etc. use the correct Hex Code.

Our questions:

  1. From where Safesky gets preferred Hex Codes of planes when using your automatic Hex Code determination?
  2. What is your recommendation in this case? Keep the wrong Hex Code as long as flightradar24 uses the wrong Hex Code?

(In flight we feed the Safesky-App on our Smartphone by our Stratux and as interim solution we have put for our plane the wrong AND(!) correct Hex Code in the Stratux-Configuration to not being alerted by the FLARM out of our plane.)

Any suggestions how to handle this?

PS: We use premium app of Safesky.

2

Hello,

We indeed rely on several open databases to map a callsign to the corresponding hex code.

Just to confirm my understanding: are you equipped with both an ADS-B Out transponder and FLARM? If so, we recommend configuring your FLARM identifier to use the ICAO address type with the same hex code. This way, Stratux, SafeSky, and other systems can use a consistent identifier and properly deduplicate the traffic.

Please keep us posted, this is an interesting topic and we’d be glad to follow up.

Fly safe,

Tristan

3

Hi Tristan, in this glider there is only flarm (no ADS-B-Out).
Thanks for caring in advance.

4

Hello,

then in this case, forget about FR24 and simply make sure you set SafeSky with your FLARM ID, and that will be fine: you should not have an echo for yourself in flight with SafeSky App.

Fly Safe,

Tristan