Every flight has two durations. One is the time you actually spend in the air, which is what your body feels. The other is the difference between the clock at the departure gate and the clock at the arrival gate, which is what your calendar sees. On a flight within one time zone they're the same. On anything longer, they can be wildly different, and almost every confusing itinerary comes from mixing them up.
The one rule: tickets use local time at each end
Airlines print departure times in the local time of the departure airport and arrival times in the local time of the arrival airport. Neither is converted to your home zone, and neither is in UTC. So to get from one to the other you need three numbers: the departure time, the flight duration, and the difference between the two airports' UTC offsets on that specific date.
The reliable method is to go through UTC rather than adding and subtracting zone differences in your head:
- Convert the departure time to UTC using the departure city's offset on that date.
- Add the flight duration.
- Convert the result into the arrival city's local time using its offset on the arrival date.
That last detail matters more than it looks. If the flight crosses a daylight saving change at either end, the offset on arrival is not the offset at departure, and a shortcut like "London is five hours ahead of New York" will be wrong by an hour.
Eastbound: the day that disappears
A typical evening flight from New York to London in June leaves JFK at 19:00 and spends about seven hours in the air. In UTC terms it departs at 23:00 and lands at 06:00. London is on British Summer Time (UTC+1) in June, so the arrival board says 07:00 the next morning. Seven hours of flying, twelve hours of clock.
That missing five hours is why eastbound overnight flights feel brutal. You board at what your body thinks is evening, you're given dinner and then breakfast a few hours later, and you land at the start of a working day having slept, at best, four or five hours. The time hasn't been stolen; it's been moved to the end of your trip, when you get it back flying home.
Westbound: the flight that lands before it leaves
Fly the other way and the effect reverses. A flight leaving Tokyo at 17:00 on 31 October 2026 with about ten hours in the air lands in Los Angeles at 11:00 the same day. Tokyo is UTC+9 and Los Angeles is on Pacific Daylight Time (UTC−7) until 1 November, a sixteen-hour gap. Ten hours of flying minus sixteen hours of zone difference means the arrival clock reads six hours earlier than the departure clock.
Nothing strange is happening physically. You took off in the late afternoon in a place that was already well into its day and landed in a place that hadn't caught up yet. But it's why these itineraries trip people up: hotel check-ins booked for the "next day," connecting flights that look impossible, and calendar invites that end before they start.
Crossing the date line
Trans-Pacific flights add a calendar jump on top of the hour shift. Leave Los Angeles on a Friday at 22:00 in early December and fly fifteen hours to Sydney, and you arrive at 08:00 on Sunday. In December, Sydney is on daylight saving time (UTC+11) and Los Angeles is on standard time (UTC−8), so the gap is nineteen hours. Saturday happened, just not to you.
Coming back, you get the day returned: a Sydney-to-Los Angeles flight often arrives earlier on the same calendar date it left. For the full story of why the line exists and where it bends, see the International Date Line guide.
When daylight saving changes mid-trip
Twice a year, flights depart under one offset and land under another. A red-eye that leaves the U.S. West Coast on the night the clocks go back gets an extra hour on the arrival clock; one leaving the night they go forward loses an hour. Because the U.S., Europe and the Southern Hemisphere change on different dates, the gap between two cities can also shift for a week or three even when neither of them is changing that night. The daylight saving guide lists the exact 2026–2028 dates.
Airlines handle this correctly in their schedules, so the times on your ticket are right. Where it goes wrong is when you do the conversion yourself, or when a calendar app converts a flight you typed in manually using today's offset instead of the travel date's.
What "+1" and "−1" mean
Booking sites show a small "+1" (or occasionally "+2" or "−1") next to an arrival time. It means the flight lands one calendar day after (or before) the departure date, in local time. It says nothing about how long the flight is. A "+1" on a two-hour hop just means you left before midnight and landed after it.
Scheduled duration versus actual time in the air
The duration on a booking page is the scheduled block time: gate to gate, including taxiing and a buffer airlines add for congestion. Actual time in the air is often 20–40 minutes less. Jet streams matter too. Eastbound flights across the North Atlantic and North Pacific usually ride a tailwind, which is why New York to London is about an hour shorter than London to New York on the same aircraft.
A worked check you can do on any itinerary
Take a London-to-New York departure at 11:00 on a June morning with an eight-hour flight. London is UTC+1 in summer, so departure is 10:00 UTC. Add eight hours: 18:00 UTC. New York is UTC−4 in summer, so you land at 14:00 local, three hours after you left by the clock. If the airline's printed arrival time matches that within a few minutes, your reading of the ticket is right.
The flight arrival calculator does exactly this, using the real offsets for the travel date, including daylight saving changes and date-line crossings. Enter the departure time and city, the flight length and the destination, and it shows both the time in the air and the time that passes on the clock.
Practical tips
- Book hotels by the arrival date on the ticket, not by counting days from departure.
- Put flights into your calendar with the departure and arrival zones set separately. Most calendar apps support a different start and end zone for one event.
- Check connections in local time at the connecting airport. Both the inbound arrival and the outbound departure are printed in that airport's time, so you can compare them directly.
- For calls on arrival day, use a converter on the actual date. The time zone converter and the meeting planner both apply the offset for the date you pick.