See my own plane Skydemon/Safesky

why do i see my own plane at the screen.
I have a ADS-B transponder and i put the Hexan code into Safesky


If you are really encode the right ICAO code, the double echo is fixed.
If not, the double echo is active.
Are you certain of your hex code?
Do you have encode your call sign in SafeSky to check your ICAO code? If you erase your hex code and re-enter your call sign, SafeSky fills in automatically the linked ICAO code.
Th other option is that you are using two devices with a different ICAO code.
For example, if you use a pilot aware or a SkyEcho, you need to encode the SAME icao code in these devices, the one certified by the transponder.
One plane = one hexa code = one traffic position

Please check this and get back to me to let me know.

Best regards,

Please give me your call sign I will check your ICAO hex code…


Thank you for the answer. It is the same hex code as at my Transponder.

I tried to erase my hex code at re-enter my call sign, and the same hex code is coming up again.

The weather in Denmark is very bad now, so I can’t try it now.

I will let you know when am flying again.

Wishes Jørgen


Do you have another device transmitting the position of the plane?
Could you please send me a screenshot of the config page of the plane with the hexa code?

No, only Transponder ADS-B out

OY 9363

Hello @jorgen

I don’t find in the different data base the hexa code OACI linked to your call sign.
It seems that something is wrong and for sure the hexa code you inform and the call sign are not aligned.
Normally you should have received an official letter with your ICAO hexa code linked to your registration. Do you have it?
Another way to find your hexa code is to make a screenshot or better, a video of your phone during the flight. When you see the double echo, the second plane (your plane) is marked with an hexa code. This is the right code to use in order to erase the double echo. Another way, but requesting works for us, is to send us information about your last flight with the double echo. Exact Time and location. With those information, we could try to find the history of your flight and check the hexa code.
Please, if you go to the config page of the plane, you can click on lookup my code from call sign, SAfeSky invites you to visit other websites with database to find you ICAO hexa code.

Please keep me posted.
@tristan is in copy of this message.


I have a similar problem when using my Stratux in combination with Safesky.

In the Stratux I have put the Hexcodes of the planes (3 Aquilas) I regularly use as follows:

  • Ownship Mode-S Hex Codes: 4406C9,44075A,3D223D
  • GLD90 bearingless target circle emulation is set to: ON

The same planes with their Callsign and Mode-S Hexcodes are saved in Safesky.

In flight using Skydemon (Use GDL90 Comp. Device => Safesky reading also from Stratux), from time to time (not permanently) I get a circle of 8 planes around me which is obviously a ghost of myself.

Changing in Skydemon to usage of Stratux alone (Use Flarm with Air Connect => Stratux only) this problem does not appear. So I assume the Hexcodes are correct.

Any idea what goes wrong?

Will it help to set in the Stratux the GLD90 bearingless target circle emulation to: OFF?


Hello @Wolfgang

You can’t compare the way to work of SkyDemon AND SafeSky. This is completely different.
The STRATUX sent traffic to SkyDemon AND SafeSky do the same + sharing position.
Si SafeSky voit du double écho cela signifie très vraisemblablement que le code hexadecimal indiqué dans SafeSky, partie transpondeur, ne correspond pas au code hexadecimal de votre avion…
When you said: Changing in Skydemon to usage of Stratux alone (Use Flarm with Air Connect => Stratux only) this problem does not appear. So I assume the Hexcodes are correct. -don’t forget that SafeSky gives also a position and if Hexacode is not correct the double echo appears. Not the case if you are only using Stratux.
You can discover your hex codes when you are filling in the call sign of the plane. Data base will give the right hexapod to use.

Keep me posted, please.

Hi there,

I am using SafeSky in conjunction with SkyDemon (Traffic/Position Data-in feed).
The airplanes I fly all have Flarm and Mode-S TXPDR (no ADSB-out) equipped.
Hence, I configured the planes in SafeSky, such that the Flarm-ID is stored in the aircraft profile, respectively.

Sometimes I get no “false” traffic alert (echo of my own aircraft) and it works as intended. But, especially if I get closer to urban areas, where the Mode-S TXPDR-Signal is taken up by a lot of stations and a bearing of the plane via MLAT (based on Mode-S) is feasible, I still get an echoed-traffic alert of my own aircraft.

The problem, I assume is, that in such urban areas, there exist two aircraft traffic, being fed into the SafeSky “traffic pool”

  • One taken from OGN/Flarm with GPS-Position, the reception of Flarm via OGN from aircraft to ground-station is pretty good in all areas I fly. → This is filtered out, since i added the Flarm-ID to the aircraft-profile.
  • Another taken from MLAT/Mode-S (e.g. adsbexchange), which delivers only sometimes, especially in dense/urban areas a position. This then triggers the echoed traffic alert.

Now the question: Is there any option, where I can store, next to the Hex-ID of my Flarm-Device, the different Hex-ID of my TXPDR, such that the traffic via MLAT can also be filtered out?
Entering both IDs e.g. separated with a comma or semicolon in the aircraft profile does NOT work out @xtof



Thank you to share this message.
The problem is that your FLARM is not configured with the same hexadecimal code than the transponder Mode S.
One and only one rule exists for this. Same Hexa code for all devices in the plane able to transmit your position.
The code that you fill in SafeSky must be the unique hexa code using in your airplanes.
Consider that using 2 different hexa codes means that you transmit the position of two different planes = two spots for the other pilots using a TCAS able to collect Flarm, ADSB and OGN for example.
Very bad idea. The only solution for you is to inform Flarm with the Hexa code of your Mode S transponder. This is the signature of your plane.

I expect that this is helpful.
Don’t hesitate to come back to us if necessary.

FR24 shows a hex code of 45F0AE for OY-9363 (if this helps).
Cave: the 0 is a zero, of course (no letter O in hex).

:+1: Thanks @Gottfried