Flight times across time zones: UTC, local time and next-day arrivals

On a ticket or itinerary, every time is local: the departure time is the clock time at the departure airport, and the arrival time is the clock time at the arrival airport. Nothing is converted for you. Once you know that, the odd-looking numbers make sense: a flight that “takes” three hours on paper may really take eight, and one that lands before it took off hasn’t broken any laws of physics.

To do the arithmetic for any pair of airports, use the time zone planner.

Why the times look wrong

Take a flight from Lahore to London leaving at 10:00 on 15 January and flying for 8 hours (an illustrative duration). It lands at 13:00 London time. On paper that’s three hours; in the air it’s eight. Lahore is five hours ahead of London in January, so five hours “disappear” from the clock.

Fly the same route in July and it lands at 14:00. Pakistan doesn’t change its clocks, but the UK moves to summer time, so the gap shrinks to four hours. Same flight, same duration, different arrival time.

Working out the real flight time

You need three things: both local times and the time difference between the airports on that date.

1. Convert the departure time to the arrival airport’s time by adding (or subtracting) the difference.
2. Subtract that from the arrival time.

For the January example: 10:00 in Lahore is 05:00 in London. Arrival is 13:00 London time. 13:00 − 05:00 = 8 hours.

Many itineraries also print the duration, which saves the sum. If they disagree with your calculation, check the date; the cause is usually a next-day arrival or a clock change.

Next-day arrivals: “+1”

An arrival marked +1 lands the next calendar day, local time. Overnight and eastbound long-haul flights often do:

Departs	Flight time	Arrives
London 21:00, 20 January	7 hours	Dubai 08:00, 21 January (+1)

Dubai is four hours ahead of London in winter, so the clock jumps forward four hours on top of the seven in the air. Book the hotel, transfer and any onward flight for the arrival date. Our annotated sample itinerary shows how a +1 arrival looks on a booking.

Arriving “before” you left

Westbound flights across the Pacific cross the International Date Line, and the calendar goes back a day. A flight leaving Tokyo at 18:00 on 10 May and flying about ten hours lands in Los Angeles at around 12:00 on 10 May: six hours earlier by the clock, on the same date. Going the other way, you lose a day. Itineraries mark this with −1 or +1 on the arrival.

Clock changes on the day you travel

Many countries move their clocks forward in spring and back in autumn, on different dates. In the UK, clocks go forward on the last Sunday in March and back on the last Sunday in October (in 2026, on 29 March and 25 October). Other countries, including Pakistan and the United Arab Emirates, don’t change their clocks at all.

That means:

• the time difference between two airports can change during the year, as in the Lahore–London example;
• a booking made months ahead can show a different gap from the one you see today;
• a flight on a changeover weekend may look an hour longer or shorter than usual.

The time zone planner uses the rules for the date you enter, so it accounts for these changes.

UTC, “Z” and the 24-hour clock

Airlines and air traffic control run on UTC (Coordinated Universal Time), sometimes written with a “Z”. Passenger documents almost always show local times instead, in the 24-hour format: 00:40 is twenty to one in the morning, and 12:40 is lunchtime. If you see UTC on a document, convert it before planning anything.

A quick checklist for any itinerary

1. Read each time as local to its airport.
2. Check every arrival for +1, +2 or −1.
3. Use the arrival date for hotels, transfers and onward flights.
4. Re-check time differences if you travel near a clock-change date.
5. Allow for the time change when planning connections and sleep.

For a full walk-through of reading an itinerary, see what a flight itinerary is and how to read one. To build time zones into a whole trip plan, see planning a flight itinerary, step by step.

Questions people ask

Are flight times shown in local time?

Yes. Departure times are local to the departure airport and arrival times are local to the arrival airport.

Why does my flight seem shorter one way than the other?

Partly time zones (clocks move the opposite way on the return), and partly winds: flights with a tailwind are genuinely faster. The printed duration tells you the real time in the air plus taxiing.

Does my phone change time automatically on landing?

Usually, if it’s set to update automatically. Your booking won’t change, so plan with the local times printed on it.