Flight Time Zones Explained: Arrival Dates, UTC & Date Changes

Every airline itinerary shows departure and arrival in the local time of each airport. This one convention explains almost every confusing thing about flight times.

Why local time

Because it is what you need at the airport. Your flight leaves at 08:35 by the clocks in the departure hall and arrives at 11:35 by the clocks in the arrivals hall. Neither number needs converting to be useful.

The cost is that you cannot subtract them to get a duration. LHR 08:35 → JFK 11:35 is a seven-hour flight, not a three-hour one, because New York is five hours behind London.

Computing a duration properly

Convert both to UTC, then subtract:

Departure  08:35 London (UTC+1)  =  07:35 UTC
Arrival    11:35 New York (UTC−4) =  15:35 UTC
Duration                          =   8h 00m

Or take the shortcut: duration = clock difference + time-zone difference, being careful with signs. Westbound, the zone difference adds; eastbound, it subtracts.

The time zone planner does this for any airport pair, including the offsets in force on the date you choose.

Why arrival dates shift

Two forces act at once. A flight takes real hours, and the clock jumps at the destination.

Eastbound long-haul usually gains a day. London to Singapore departs at 21:30 and arrives at 17:30 — the next day. The flight is 13 hours; Singapore is 7 hours ahead.

Westbound long-haul often arrives “before” it left. Tokyo to Los Angeles departs at 17:00 and arrives at 10:00 on the same date, having flown 10 hours. Los Angeles is 16 hours behind, so the clock rolls back further than the flight takes forward.

Neither is a printing error. Both are what the clocks say.

The International Date Line

The date line runs roughly along 180° longitude, with detours around inhabited territories. Crossing it changes the calendar date by a full day, independently of the hours flown.

Westbound across it, you lose a day. Los Angeles to Sydney departs Monday 22:30 and arrives Wednesday 06:45. The flight is about 15 hours. Tuesday does not happen.

Eastbound across it, you gain one. Sydney to Los Angeles departs Sunday 10:00 and arrives Sunday 06:30 — earlier the same morning.

This routinely produces hotel bookings on the wrong night, visa forms with the wrong entry date, and missed connections in Auckland. The time zone planner flags date-line crossings explicitly, and the generator computes the arrival date for each leg of a sample itinerary.

Daylight saving

The second trap, and less obvious than the date line because it moves.

Time-zone offsets are not constant. Most of Europe and North America shift by an hour twice a year, on different dates from each other. Most of Asia, Africa and the tropics do not shift at all. The southern hemisphere shifts in the opposite months.

The consequences:

The gap between two cities changes during the year. London and New York are 5 hours apart for most of the year but 4 hours apart for about three weeks in March and one in late October, when the two regions switch on different dates.
A flight crossing the changeover night is an hour longer or shorter on the clock than the same flight the day before.
A connection you calculated in one season may not hold in another.

This is why offsets should always be evaluated for the actual travel date, not today’s. The tools on this site use each airport’s IANA time zone — Europe/London, America/New_York — and resolve the offset for the date in question rather than assuming a fixed number.

UTC offsets that surprise people

Not every zone is a whole number of hours from UTC:

Zone	Offset
India	UTC+5:30
Nepal	UTC+5:45
Iran	UTC+3:30
Newfoundland	UTC−3:30
Marquesas Islands	UTC−9:30
Chatham Islands	UTC+12:45
Kiribati (Line Islands)	UTC+14

The 45-minute zones exist, are in current use, and break arithmetic that assumes whole hours.

Practical rules

Read every time on an itinerary as local to its own airport. Never convert.
Compute arrival dates rather than assuming them, especially eastbound and across the Pacific.
Check the offset for your travel date, not today’s, if the trip crosses a DST changeover.
Book hotels against the arrival date the itinerary shows, not the departure date plus your mental estimate.
Compute connection times using both figures as printed — they are already in the same local time.