It would appear that the flight log algorithm could use some refinement.
This Sprint flight had an in flight emergency (smoke, but all ok) about 100 miles after takeoff and returned to origin. Correctly logged. But then, the algorithm continued to estimate or approximate travel along the flight plan even though the plane was on the tarmac.
I would think that an unscheduled descent to a landing elevation should trigger a branch in the algorithm.
We currently depend on receiving diversion notices from an authoritative source, rather than attempting to synthetically detect a diversion based on positions alone. Since Mexico is not currently one of our primary coverage areas, and Spirit does not send us full aircraft status, we do not reliably receive flight event messages such as diversions.
Notice that there is a message displayed on screen warning about inaccurate information: “At least part of this flight occurs outside of FlightAware’s primary service area. Learn more about FlightAware’s coverage”