← Blog

Explainer

Airport Timezones and Why Arrival Times Confuse People

By The Flight Tracker Team · September 14, 2026

Every departure and arrival time on your ticket is shown in the local time of the airport it refers to. Nothing on an itinerary is in “your” time unless you happen to be standing in that timezone. Once you internalise that one rule, almost every confusing arrival time stops being confusing.

It is why a flight can appear to land before it took off, why a “10-hour flight” shows a 3-hour gap on paper, and why a phone that helpfully switches timezones mid-journey can make you doubt an itinerary you read correctly.

The rule: departure time is local there, arrival time is local there

A flight leaving one city at 18:40 and reaching another at 19:10 is not a 30-minute flight. It is a departure at 18:40 in the departure airport’s timezone and an arrival at 19:10 in the arrival airport’s timezone. The actual duration depends on the offset between the two.

The arithmetic that gets you the real duration:

Duration = (arrival local time − departure local time) + (departure offset − arrival offset)

Travelling west, you gain hours on paper, and flights look shorter or even negative. Travelling east, you lose hours, and a short hop can appear to eat most of a day.

Why a two-hour flight can “arrive before it departed”

Fly west across two timezones on a two-hour flight and the clock reads like this:

	Local clock	GMT
Departure	09:00 (GMT+2)	07:00
Arrival	08:00 (GMT-1)	09:00

The aircraft was airborne for two hours. The local clock at the destination went backwards by three, so the printed arrival time is an hour earlier than the printed departure time. Nothing is wrong with the schedule. The two numbers are simply measured on different clocks.

The extreme version happens across the international date line, where a flight can arrive on the previous calendar day. Same principle, larger jump.

Your phone is trying to help and sometimes makes it worse

Modern phones update their timezone automatically from the network. That is usually what you want — and occasionally a trap:

• Mid-journey switches. Your phone may adopt the new timezone as soon as it finds a network on landing, silently reinterpreting calendar entries and alarms you set at home.
• Alarms set before departure. An alarm for “06:00” fires at 06:00 in whatever timezone the phone thinks it is in when the time arrives. For an early connection, that is a real risk.
• Screenshots of itineraries. A screenshot preserves the number but not which timezone it belonged to. Note the airport code beside every time you write down.

The safest habit is to write times with their airport: “22:15 at the departure airport”, not “22:15”.

GMT offsets, and why they are not all whole hours

Offsets are usually expressed relative to GMT — GMT+1, GMT-5, and so on. Two details catch people:

1. Some offsets are not whole hours. Several countries and regions sit on half-hour or 45-minute offsets. Mental arithmetic that assumes whole hours will be wrong there.
2. Country size does not determine timezone count. Some very wide countries run a single national timezone; some smaller ones span several. Never infer an offset from geography — look up the airport.

The daylight-saving traps

Daylight saving is where careful travellers still get caught, for four reasons:

• Not everywhere observes it. Large parts of the world never change their clocks, so the gap between two cities is not constant through the year.
• Hemispheres shift in opposite directions. When one hemisphere springs forward, the other falls back. The offset between them can move by two hours.
• Change dates differ. Even among places that do observe it, the switch dates are not aligned. There are stretches of the calendar where the usual offset between two cities is temporarily different.
• Flights that cross the switch. A flight airborne during a clock change has a printed duration that does not match the elapsed time.

If your trip is within two weeks of a clock change at either end, check the arrival airport’s offset for the specific date rather than for today.

How to read an itinerary without getting caught

• Read each time together with its airport code.
• Convert to GMT once if you need to compare two legs, then stop converting.
• For connections, compute the layover in the connecting airport’s local time — both legs are already quoted there, so the subtraction is honest.
• Set alarms for early departures by wall clock at the airport, and check the phone has the right timezone before you rely on it.

Flight Tracker stores each airport’s timezone alongside its codes, coordinates and contact details, so the times you see are labelled with the place they belong to. Our guide on airport information to check before flying covers the rest of the pre-trip lookups, and how it works explains what the app displays.

Timezones are arithmetic, but schedules are decisions — airlines retime flights, and a retimed flight changes the arithmetic. Before you plan a pickup or a tight connection around a printed time, confirm it with your airline.

---