# Unusual flight path

**URL:** <https://discussions.flightaware.com/t/unusual-flight-path/48855>\
**Category:** General\
**Created:** [April 20, 2019, 3:07pm UTC](https://discussions.flightaware.com/t/unusual-flight-path/48855 "2019-04-20T15:07:48Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![kathiea1](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/kathiea1/32/38330_2.png) [@kathiea1](https://discussions.flightaware.com/u/kathiea1)\
**Post date:** [April 20, 2019, 3:07pm UTC](https://discussions.flightaware.com/t/unusual-flight-path/48855/1 "2019-04-20T15:07:48Z")

</div>

Good morning, I’m currently (4/20/19 at 11am eastern) tracking American Airlines 4975 from CLT to ROA. Is it possible this is a software thing or did this plane really go the “wrong” way then turn around? There is another small airport in the general vicinity where it did that reversal.

 ![Screenshot_20190420-110112_FlightAware](https://us1.discourse-cdn.com/flex019/uploads/flightaware/original/3X/6/2/62fc1289023a2c1aa0120fc49c3fffc6ef509627.jpeg)

---

<div class="post-metadata">

**Author:** ![kathiea1](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/kathiea1/32/38330_2.png) [@kathiea1](https://discussions.flightaware.com/u/kathiea1)\
**Post date:** [April 20, 2019, 3:11pm UTC](https://discussions.flightaware.com/t/unusual-flight-path/48855/2 "2019-04-20T15:11:50Z")

</div>

Update - takeoff time has how been updated and it seems this flight did take the normal amount of time… just interesting that there is what seems to be an incorrect trail leading to another airport and back. 🙂

---

<div class="post-metadata">

**Author:** ![wiedehopf](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/wiedehopf/32/114045_2.png) [@wiedehopf](https://discussions.flightaware.com/u/wiedehopf)\
**Post date:** [April 20, 2019, 3:18pm UTC](https://discussions.flightaware.com/t/unusual-flight-path/48855/3 "2019-04-20T15:18:27Z")

</div>

Somehow the flight to ROA got combined with the flight to PGV the aircraft made before.  
The way back from PGV to CLT wasn’t tracked properly.  
Now there is another flight that is the actual CLT to ROA leg:

[https://flightaware.com/live/flight/N633AE/history/20190420/1431Z/KCLT](https://flightaware.com/live/flight/N633AE/history/20190420/1431Z/KCLT)

Viewing by airframe gives you a good overview that there is some data gone haywire.  
Probably because of canceled flights in the system.

---

<div class="post-metadata">

**Author:** ![kathiea1](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/kathiea1/32/38330_2.png) [@kathiea1](https://discussions.flightaware.com/u/kathiea1)\
**Post date:** [April 20, 2019, 3:36pm UTC](https://discussions.flightaware.com/t/unusual-flight-path/48855/4 "2019-04-20T15:36:04Z")

</div>

Thanks! I was wondering what could make that happen.

---

<div class="post-metadata">

**Author:** ![wiedehopf](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/wiedehopf/32/114045_2.png) [@wiedehopf](https://discussions.flightaware.com/u/wiedehopf)\
**Post date:** [April 20, 2019, 3:45pm UTC](https://discussions.flightaware.com/t/unusual-flight-path/48855/5 "2019-04-20T15:45:06Z")

</div>

I’m not sure either but that’s my guess at least.

Flightaware get’s flightplan data from the FAA and if they get multiple flight plans because of changes due to the weather the system might get confused.

Also sometimes the callsign isn’t correctly set in the ADS-B transponder.  
So they might have set the callsign for the flight to ROA when they flew to PGV.