Aircraft locations all weird


#1

Can someone help me understand this –

Some days the PIAware aircraft locations are spot on. They land on the proper runway, they go where they are supposed to go.

Then sometimes…they are all over the place. It shows planes landing in a shopping center 1 mile from the airport, or the ocean (yipes!) or flying in the wrong direction. It can be common for the aircraft track to constantly readjust and shift several miles.

Is there a reason for this?

Thanks.


#2

some planes have their ADSB linked to inertial location systems, the gyros are set at takeeoff - but by the time they land they’re just not quite correct.


#3

Wow. I certainly hope that gets fixed before ADSB replaces radar :slight_smile:
Thanks.


#4

The position messages do include some info about the accuracy of the position - generally if an aircraft loses GPS for whatever reason, it does indicate that it’s reporting an INS position or a degraded GPS position by dropping the accuracy reported, and that position data isn’t going to be trusted when it matters.


#5

Here’s what bothers me -
I fly all over this state and my plane’s GPS/internal nav system is never off by more than a foot or two. There are days when my home ADBS can show 50 planes (as in major airlines) off by miles with the icon suddenly shifting to play catch up. That indicates to me a signal or processing problem.

If my auto pilot took me as far off course as some I’ve seen it would be in the shop immediately.

Thoughts?


#6

Show me some raw messages that show the problem?


#7

Sure, as soon as I figure how how :slight_smile:
I just run the thing and feed FlightAware.

Lemme see what I can do. I’d like to solve this mystery.


#8

You can connect to port 30002 for raw messages, one line per message.
If you capture that output while you see the problem and search for only lines containing the ICAO address of the aircraft that has the problem (DF17 messages, the position messages, include the address directly, so this is a handy shortcut to narrow it down without requiring full decoding), then those should be enough to work out what’s going on.

It should look something like this (here, I filtered for 4CA61B). The longer messages will be the DF17s.



*8D4CA61B601F360654044089844B;
*8D4CA61B99C47F1F60B00BBD752F;
*8D4CA61B601F429A140457D286EC;
*5D4CA61BABEDED;
*8D4CA61B99C4871EE0BC0BC55508;
*5D4CA61BABEDC7;
*8D4CA61B601F6606A2042B527CC5;
*5D4CA61BABED83;
*8D4CA61B204994B6D86360B4F7AF;
*8D4CA61B99C48E1E40C00B9B3F29;
*8D4CA61B601F829A76043C435032;
*8D4CA61B99C4951DC0C00CDF0997;
*5D4CA61BABEDC7;
*8D4CA61B99C4951DC0C00B20D9B3;
*8D4CA61B601FA60700040F74889F;
*5D4CA61BABEDC7;
*8D4CA61B601FB29AC20424575836;