Yes, SIL=0 is for uncertified GPS receivers. quite common in ultralight/microlight with for example a Garmin G3X with the GPS antenna directly connected to the back of the screen instead of through a certified GPS receiver like Garmin GPS175 etc.
FR24 seems to choose to use MLAT triangulation as the source for position instead of trusting the ADS-B SIL=0 data.
Anyone know how the Aero tracker sees aircraft with ADS-B SIL=0?
In the case with Garmin for example, the certified units are required to discard such transponders however the uncertified units like the GDL50 etc will show them.
I just looked for that registration using ADS-B EXCHANGE and it appears to be a high quality ADS-B OUT transmission.
I think the issue may have been lack of ground receivers that SafeSky uses in that area.
Maybe the SafeSky engineering team can investigate further to see if the aircraft was decteded, or not, by their systems.
Very occasionally I have seen good ADS-B OUT transmissions near my home which didn’t show up in SafeSky during ground testing. Reason unknown, but a rare incident.
In the UK is a network of Pilot Aware ground stations, to provide services to PAW users. There is also a facility to plot received signals from aircraft to assist with determining if aircraft antenna placement is optimal. Works for transponder, PAW, FLARM and ADS-L transmissions and produces something similar to an RF reception polar diagram. I used that facility to plot my Tracker’s ADS-L OUT signal. That is how I know how well my externally mounted Tracker antenna performed..
SafeSky provides totally unfiltered traffic data, so SIL=0 should be passed though. So if a traffic was visible on a source network, there must be something on our side to be investigated. Any chance you could confirm a date and time for such traffic, like this SE-XTF ?
If you could point me to the date and where the flight you observed was not showing up on SafeSky, we will investigate this further as this is not expected.
I think I figured out what was causing it. The co-owner of the aircraft and I were both logged into the same account. While he was tracking the flight from the ground in SafeSky, it removed my position to prevent what I assume is “ghosting” or duplicate tracking, and as he logged out, I appeared.
However, on the flight on the 29th, the SafeSky app crashed three times during the 2,5h flight. Are there any crash logs available that could help determine what caused it?
