# Strange flight path **URL:** \ **Category:** General\ **Created:** [June 24, 2006, 12:17am UTC](https://discussions.flightaware.com/t/strange-flight-path/1622 "2006-06-24T00:17:07Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![anon63817388](https://avatars.discourse-cdn.com/v4/letter/a/958977/32.png) [@anon63817388](https://discussions.flightaware.com/u/anon63817388)\ **Post date:** [June 24, 2006, 12:17am UTC](https://discussions.flightaware.com/t/strange-flight-path/1622/1 "2006-06-24T00:17:07Z")
Check out this trip [flightaware.com/live/flight/WJA9 … /CYVR/PHOG](http://flightaware.com/live/flight/WJA962/history/20060623/0253Z/CYVR/PHOG) And all this travelling was done in just over five hours! ---
**Author:** ![mduell](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/mduell/32/115680_2.png) [@mduell](https://discussions.flightaware.com/u/mduell)\ **Post date:** [June 24, 2006, 12:23am UTC](https://discussions.flightaware.com/t/strange-flight-path/1622/2 "2006-06-24T00:23:02Z")
Looking at the tracklog, somehow that flight was erroneously reported to be within 1 degree of 0lat/0long a few times… sometimes the overwater reporting system has oddities like that. ---
**Author:** ![Boeing7475500](https://avatars.discourse-cdn.com/v4/letter/b/46a35a/32.png) [@Boeing7475500](https://discussions.flightaware.com/u/Boeing7475500)\ **Post date:** [June 24, 2006, 3:45am UTC](https://discussions.flightaware.com/t/strange-flight-path/1622/3 "2006-06-24T03:45:24Z")
Fast jet! ---
**Author:** ![jolsen](https://avatars.discourse-cdn.com/v4/letter/j/85e7bf/32.png) [@jolsen](https://discussions.flightaware.com/u/jolsen)\ **Post date:** [June 24, 2006, 12:41pm UTC](https://discussions.flightaware.com/t/strange-flight-path/1622/4 "2006-06-24T12:41:04Z")
AA73 is showing the same type of flight path on 6/22 and 6/23. Probably for the same reason? ---
**Author:** ![anon63817388](https://avatars.discourse-cdn.com/v4/letter/a/958977/32.png) [@anon63817388](https://discussions.flightaware.com/u/anon63817388)\ **Post date:** [July 4, 2006, 8:05pm UTC](https://discussions.flightaware.com/t/strange-flight-path/1622/5 "2006-07-04T20:05:49Z")
This is still happening on flights over the Pacific. e.g. [flightaware.com/live/flight/DAL1 … /KSLC/PHOG](http://flightaware.com/live/flight/DAL1760/history/20060704/1753ZZ/KSLC/PHOG) Obviously for me or other casual trackers it is just an annoyance but I wonder if this erroneous data is being used in “official” reports and whether there are any safety or security concerns. ---
**Author:** ![CessnaCitationX](https://avatars.discourse-cdn.com/v4/letter/c/e480ec/32.png) [@CessnaCitationX](https://discussions.flightaware.com/u/CessnaCitationX)\ **Post date:** [July 4, 2006, 8:12pm UTC](https://discussions.flightaware.com/t/strange-flight-path/1622/6 "2006-07-04T20:12:48Z")
Welcome to the forum cookie! 8) There is a SEARCH feature in the FlightAware forums. Your question has been answered at least five times in the last month or two. Most of the questions you have, have already been answered. So PLEASE search the forum _before_ you post! When you search the forum, and its answered, you get your answer quickly, and we don’t have to waste posts on questions already answered. Thank you. Also this thread belongs in the Notable Activity forum. Enjoy the forum! 😃 CCX P.S. Check out my blogs, a link to them is in my profile. **Edit:** > [@cookie](#): > > This is still happening on flights over the Pacific. > > e.g. [flightaware.com/live/flight/DAL1 … /KSLC/PHOG](http://flightaware.com/live/flight/DAL1760/history/20060704/1753ZZ/KSLC/PHOG) Good job! You gave us a clickable link and the flight for that day. Thank you! Sometimes people just give the link for the flight number and we sit around looking for the flight he was talking about. …A few days later. ---
**Author:** ![dbaker](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/dbaker/32/97166_2.png) [@dbaker](https://discussions.flightaware.com/u/dbaker)\ **Post date:** [July 4, 2006, 8:39pm UTC](https://discussions.flightaware.com/t/strange-flight-path/1622/7 "2006-07-04T20:39:37Z")
I believe this is a FlightAware interpretation error that will be resolved this week. ---
**Author:** ![dbaker](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/dbaker/32/97166_2.png) [@dbaker](https://discussions.flightaware.com/u/dbaker)\ **Post date:** [July 9, 2006, 12:44am UTC](https://discussions.flightaware.com/t/strange-flight-path/1622/8 "2006-07-09T00:44:29Z")
This was fixed this evening and it should be a non-factor after today. We’ll retroactively correct the errors for past flights in the future. ---
**Author:** ![anon63817388](https://avatars.discourse-cdn.com/v4/letter/a/958977/32.png) [@anon63817388](https://discussions.flightaware.com/u/anon63817388)\ **Post date:** [July 9, 2006, 6:13pm UTC](https://discussions.flightaware.com/t/strange-flight-path/1622/9 "2006-07-09T18:13:27Z")
Thank you, dbaker, for the solution and for keeping us informed. ---
**Author:** ![im4point](https://avatars.discourse-cdn.com/v4/letter/i/e8c25b/32.png) [@im4point](https://discussions.flightaware.com/u/im4point)\ **Post date:** [July 28, 2006, 5:05pm UTC](https://discussions.flightaware.com/t/strange-flight-path/1622/10 "2006-07-28T17:05:05Z")
Here is another weird route… [flightaware.com/live/flight/EGF4 … /KORD/KTVC](http://flightaware.com/live/flight/EGF469/history/20060728/1654Z/KORD/KTVC) ---
**Author:** ![Pat206](https://avatars.discourse-cdn.com/v4/letter/p/76d3ee/32.png) [@Pat206](https://discussions.flightaware.com/u/Pat206)\ **Post date:** [July 28, 2006, 8:46pm UTC](https://discussions.flightaware.com/t/strange-flight-path/1622/11 "2006-07-28T20:46:08Z")
OK, who had today in the Eagleflight sweepstakes ? 😉 ---
**Author:** ![dbaker](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/dbaker/32/97166_2.png) [@dbaker](https://discussions.flightaware.com/u/dbaker)\ **Post date:** [July 28, 2006, 9:10pm UTC](https://discussions.flightaware.com/t/strange-flight-path/1622/12 "2006-07-28T21:10:31Z")
The eagle flight issue is a known issue where they are operating duplicate flight numbers simultaneously.