Automatic tracking pulls from the airline’s own operational feed, and most of the time it’s fast: off-blocks, takeoff, touchdown, and on-blocks land in your entry within moments of happening. Occasionally an arrival actual posts later than the flight itself. Here’s what that looks like and what to do.
Why an actual can arrive late
Airline feeds publish actual times as ground and ramp systems confirm them, and that confirmation doesn’t always land the instant the event happens. A touchdown or on-blocks time can post minutes to hours after the fact. Jetlog keeps checking for a short window after a flight lands to catch these, so most resolve on their own. A small share, more common on routes with known coverage gaps (see Supported Airlines), may lag longer or never post at all.
What you’ll see in the meantime
If an actual hasn’t posted yet, the field shows the best estimate Jetlog has: scheduled or estimated, not a blank or an error. Once the real actual arrives, it replaces the estimate automatically. If you completed the entry from the Live Activity’s Complete prompt before a late actual came in, a later update can still refine the time in the background.
If a time looks wrong
Your logbook is always yours to correct. Open the entry, tap the field, and enter the time you actually observed. Automatic tracking never locks a field against a manual edit. Do this whenever a time looks implausible, whenever you have a better source (your own cockpit clock, an ACARS printout), or whenever a flight isn’t covered by automatic tracking at all.
Next
For the full picture of what’s tracked, see How automatic flight tracking works. To report a route or airline you’d like added, send your roster format to support@jetlog.app.
