# Bug in FA mapping

**URL:** <https://discussions.flightaware.com/t/bug-in-fa-mapping/17839>\
**Category:** ADS-B Flight Tracking\
**Created:** [January 5, 2016, 6:27am UTC](https://discussions.flightaware.com/t/bug-in-fa-mapping/17839 "2016-01-05T06:27:05Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![N456TS](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/n456ts/32/88612_2.png) [@N456TS](https://discussions.flightaware.com/u/N456TS)\
**Post date:** [January 5, 2016, 6:27am UTC](https://discussions.flightaware.com/t/bug-in-fa-mapping/17839/1 "2016-01-05T06:27:05Z")

</div>

FA web site issue… I have noticed a bug with the plotting of routes on the map of flights. Many times for active flights, when clicking on the flight, the map defaults to the west coast of Africa. There isn’t any plotted paths. If you zoom out and find the flight, it’s in the correct area and reporting “live”. Reloading resolves this and it’s zoomed in to the correct part of the world.

The second issue is almost the same. Old flight( [Example](https://flightaware.com/live/flight/N456TS/history/20160102/2045Z) ). The maps starts in the same west Africa area, but it has an incorrectly plotted path from west Africa to the US. If you reload the page, and the incorrect plotting is gone and everything displays correctly. (The example is a 30 minute flight from KTTA to KHBI). I am 99.99999999999% sure this isn’t a case of incorrect data provided to FA. Everything points to a rendering/display issue. I didn’t take screen shots. This is the best information I can provide at this time.

---

<div class="post-metadata">

**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:** [January 5, 2016, 12:55pm UTC](https://discussions.flightaware.com/t/bug-in-fa-mapping/17839/2 "2016-01-05T12:55:05Z")

</div>

It’s a 0,0 lat,lon issue – we’re working on a huge mapping infrastructure roll-out that should fix this.

---

<div class="post-metadata">

**Author:** ![N456TS](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/n456ts/32/88612_2.png) [@N456TS](https://discussions.flightaware.com/u/N456TS)\
**Post date:** [January 5, 2016, 4:24pm UTC](https://discussions.flightaware.com/t/bug-in-fa-mapping/17839/3 "2016-01-05T16:24:21Z")

</div>

Ok, thanks. Any chance you need someone to test one of the UAT antennas in NC?