I have notcied lately, on several domestic flights, flightaware will “lose track” of the flight. Like for example, right now, Allegiant # 6050 from LAS to GRB. It is enroute, but the route and info is N/A, and it drops off the map over Utah when it is actually closer to Iowa, about 50 minutes from landing. Is this a glitch in the system?
Bruce
For some reason there were no position reports for that flight for over an hour, then they picked up again and continued to the destination (well, almost, looks like an early arrival message was triggered just after the descent began).
From the tracklog:
16:13 38.33 -110.90 453 31000
16:13 38.33 -110.87 454 31000
16:14 38.38 -110.75 453 31000
16:14 38.40 -110.72 454 31000
17:15 41.45 -101.62 447 33000
17:16 41.48 -101.45 441 33000
17:17 41.53 -101.30 446 33000
I’ll check the logs to see if it is a problem with the feed from the FAA or our parsing of the feed.