CALPSAFltSkeds From United States of America, joined Dec 2006, 2912 posts, RR: 8
Reply 3, posted (6 years 3 weeks 1 day 7 hours ago) and read 11513 times:
If you click on the "track log", you'll see that the aircraft is traveling eastward on every report. The aircraft seems to be traveling about -0.14 longitude per minute at cruise. It looks like a bad report over the ocean at 2230 as it only traveled under 4 degrees of longitude in 50 minute, followed by nearly 7 degree in the following 30 minutes. My guess is a bad report to OAK Oceanic at 2230, which might have created the thick line over the Pacific..
Transpac787 From United States of America, joined Jul 2007, 3251 posts, RR: 15
Reply 4, posted (6 years 3 weeks 1 day 5 hours ago) and read 11285 times:
They most definitely did *not* turn around. On eastbound HNL-US flights, the ETP (equal time point) is only about 2 hours outside of HNL. As you can see, at the point in question, it would have been a LOT quicker to just continue onward to the mainland, both in distance and duration, if some in-flight problem had come up.
So yea, it's definitely a FlightAware mistake. The ETOPS equal time point was long passed, and they would have just continued to SFO/OAK/SJC for divert.
GothamSpotter From United States of America, joined Jan 2005, 586 posts, RR: 0
Reply 5, posted (6 years 3 weeks 21 hours ago) and read 10027 times:
FlightAware routinely messes up flight paths on overseas flights. Note the disclaimer on many flights: "At least part of this flight occurs outside of FlightAware's service area. Information on this page may be unreliable."
Borism From Estonia, joined Oct 2006, 431 posts, RR: 0
Reply 6, posted (6 years 3 weeks 20 hours ago) and read 9799 times:
While FlightAware routinely messes up flight paths outside N. American airspace, this particular glitch is due to Oakland Oceanic ODAPS position report being less precise than those of radar covered areas. I've seen this happening in even weirder ways to Hawaii-Alaska flights.