thanks, flight was on Friday 26th August between 1400 and 1530 utc
I was running PilotAware and was getting lots of alerts (I was NOT using safesky feed)
My co pilot was running SkySafe configured as shown and was also seeing ghosting
Hello, and thanks for the feedbacks. Your SafeSky setup is perfect.
I just checked for your flight, and I can see the traffic from hex code 40651B:
from PilotAware
as MODE-S using multi-lateration
as SafeSky from the app
By design, SafeSky will show the most up-to-date and precise traffic location, regardeless of its source.
There is nothing in our logs that relates to 393F76. Could you please followup with PilotAware, and share with us their findings? Could it be that they do not de-duplicate traffic and were generating ghost alerts in PAW?
I suspect that on SafeSky, there was no alerts, since those 3 sources were you.
Sorry for late reply, but we are on our way to the ultra-light world event in France.
Thanks for copying the reply, it’s pretty clear now. Indeed, to guarantee being anonymous when needed from SafeSky to OGN, we are creating a hash of the internal id. In this specific case, since the PAW id was encoded in safesky (would be the same for an ads-b or mode-s ICAO hex), we should simply respect and pass over the entered id. That way, PAW will receive it and will be able to deduplicate the traffic naturally.
Thanks a lot for raising this point to us, we are going to take an action and fix this.
I’m not sure what you mean by anonymous? Data transmitted on ADSB and mode S carries the proper hex code. It’s a core part of the standards. I think it’s a massive manipulation of the ecosystem if the codes of aircraft are collected from OGN and then scrambled by SS? Do OGN know you’re doing this?
If the intent is to protect the personal identity of the pilot then their ownership details with the aviation authority should be anonymous. Not the call sign.
We are just back from the MULM 2022 in Blois. It’s been a fantastic event, and as an official partner, SafeSky has been used by AFIS agents to securely handle 800 registered aircrafts in and out over the week-end. Second year we are doing this.
That explains my late response…
Forget ly previous message. The issue is different. We are working hand in hand with the OGN team, and we are totally in sync when it comes to bi-directional data exchange. We are happily sharing SafeSky traffic to OGN so that other third party projects can also benefits from this. In return, we strongly advertise for OGN ground station installations so that we can support the project too. Beautiful partnership.
So in short, we are not ‘scrambling’ OGN ids in any ways. The problem was an encoding issue with aircrafts that has entered a custom id in SafeSky transponder. The patch has been applied today.
Thanks a lot for having reported the problem and supported us with this issue.
Please let me know in your next flight if this is working fine (no traffic alerts from your own PAW)
Means that station called “SKY48FD60” coming from the APRS TO-CALL transmission system is “OGNSKY”. This station is transmiting a position for id “48FD60”.
Because it’s coming from OGNSKY with a station starting with SKY, this ID is NOT intended to be a ICAO hex code as defined by ATDB - ICAO 24-bit addresses - Decode
We had some exchange with the team at OGN tonight, and they confirm that when an ICAO hex code is to be used as an official ID, the expected message format is:
In addition, we are going to hash the safesky internal IDs (the one not based on real ICAO as entered by the pilot) so that they will also translate into hex code > F096FF so that they will never match any existing allocated hex codes.
This should retro-fit with any systems, regardless of the “ICA” prefix interpretation.
This message is the confirm that after some exchanges with the OGN team and the PilotAware team, the patch that was deployed last week is addressing the issue reported.
We are going to conduct additional flight tests in the next coming days to confirm with various configurations.