#1
|
||||
|
||||
Flightaware
This is a bit of an off subject but wondering if anyone else experienced the same issue with flightaware. Last week had a flight to MIE in Indiana and back to BTL in Michigan. Two days ago I check flightaware to see how it tracked my flight. I few on an IFR plan. It reflected my flight as it should. However it also showed that two days after that flight my plane was seen in Georga for a 5 Mile track. Has anyone else experienced a misrepresentation like that? My plane is N34EC.
|
#2
|
||||
|
||||
I’ve seen reports of artifact tracks on the day of flight, but not 2 days later!
You could try running an ADS-B performance report https://adsbperformance.faa.gov/PAPRRequest.aspx for both days and see what pops. Also check WAAS notams for both days, perhaps some anomaly there affected the ads b ground systems? I’d be interested to find out what you learn. |
#3
|
||||
|
||||
Jerry
Did you recently have any ADSB work done? If not then is the plane on Flightaware in Georgia listed as your Skymaster or another plane? There has been quite a few mis typed N numbers on new transponders or ADSB registration. It really throws a wrench in the tracking of aircraft
__________________
Herb R Harney 1968 337C Flying the same Skymaster for 47 years |
#4
|
||||
|
||||
I've seen flightaware report my plane as being in the air for a one minute flight when I know it was in the hangar. I also know of this happening to at least one other tail number.
|
#5
|
||||
|
||||
Jerry
The exact reason I asked the question above. I have had this happen also and found the issue in the ADSB set up.
__________________
Herb R Harney 1968 337C Flying the same Skymaster for 47 years |
#6
|
||||
|
||||
Flightaware
No Herb, no repair. Flightaware did show my N number and also a picture of my plane. I sent email it flightaware but never received a reply.
|
#7
|
||||
|
||||
I've seen the same thing happen with my airplane and asked FlightAware the same question. They replied that the primary reason for the issue is controller data entry, which is then corrected to the correct N-Number (the reason the tracks are very short). I can see this happening, especially with a Center controller's initial VFR flight following request. You hear it all the time, the initial call, and the correction.
My N-Number has been flying around Florida for a couple the last couple of days with my airplane firmly on the ground here in Texas. In that case, I suspect the douche has misconfigured his ADB-S Out setup. |