Are Flight Times Local Time? How Airlines Show Times

Yes. Flight departure and arrival times on tickets, booking confirmations, boarding passes and airport screens are given in the local time of each airport: the departure time is the local time where you leave, and the arrival time is the local time where you land. Airlines say so in their own help pages. Transavia: “All departure and arrival times are shown in the local time” (Transavia). Iberia: “the times shown refer to local time at the airport in question” (Iberia). The catch is that the two times are on different clocks, so subtracting one from the other does not give the flight’s length, and on some routes the arrival looks earlier than the departure. This guide explains the rule, the one formula you need, worked examples that include Canada’s new 2026 time rules and a clock-change night, and why pilots work in a different time altogether. Facts are as of November 2026.

Key facts (as of November 2026)

  • Published flight times are local at each airport; the arrival date is the date at the destination.
  • Flight length = arrival (local) − departure (local) − (destination’s UTC offset − origin’s UTC offset).
  • Airline schedules are exchanged under IATA’s Standard Schedules Information Manual, whose Appendix F covers “UTC-Local Time Comparisons” and “Daylight Saving Time Information for 2026-2027 and 2028” (IATA).
  • Air traffic control works in UTC: US controllers state time as “The four separate digits of the hour and minute/s in terms of UTC” (FAA JO 7110.65, 2-4-17).
  • Since 2026, a 1-hour winter flight from Vancouver to the Seattle area lands at the same clock time it took off (our calculation).

Why airlines use local time

Local times are what you need at each end: when to be at the gate and when someone should meet you. Behind the scenes the industry keeps both clocks. IATA’s Standard Schedules Information Manual (SSIM), the standard airlines use to exchange schedules, includes an appendix of “UTC-Local Time Comparisons and ISO Two letter Country Codes”, and its current update covers “Daylight Saving Time Information for 2026-2027 and 2028” (IATA SSIM). That is how a booking system knows that a 9:00 AM departure from Vancouver is 16:00 UTC, and what local time to print for the arrival.

In the cockpit and the control tower it is the other way round. The FAA’s air traffic order says time is stated as “The four separate digits of the hour and minute/s in terms of UTC”, that “The term ‘ZULU’ may be used to denote UTC”, and that “the word ‘local’ or the time zone equivalent must be stated when other than UTC is referenced” (FAA JO 7110.65, 2-4-17). Passengers never see this, but it explains why a flight-tracking site may show “Z” times. See UTC vs GMT and our military time chart for reading them.

The formula for real flight time

Take the clock difference between the printed times, then remove the time-zone difference:

Flight time = (arrival local − departure local) − (destination UTC offset − origin UTC offset)

Example: Vancouver (UTC−7) 8:00 PM to London (UTC+0 in January) 12:30 PM next day. The printed times are 16 h 30 min apart. London’s offset is 7 hours higher, so the flight takes 16:30 − 7:00 = 9 h 30 min. Flying west, the offset difference is negative, so subtracting it adds time back.

Worked examples

These use sample flight lengths, not any airline’s actual schedule, and were computed with Python zoneinfo on IANA tzdata 2026f.

Example route (sample flight time) Departs (local) Arrives (local) Clock difference
Vancouver → London (9 h 30 min) Fri Jan 15, 8:00 PM Sat Jan 16, 12:30 PM +7 h
London → Vancouver (9 h 45 min) Thu Jul 15, 1:00 PM Thu Jul 15, 2:45 PM −8 h
Los Angeles → Sydney (15 h) Fri Jan 15, 10:30 PM Sun Jan 17, 8:30 AM +19 h
Sydney → Los Angeles (13 h 30 min) Sun Jan 17, 11:00 AM Sun Jan 17, 5:30 AM −19 h
Vancouver → Seattle area (Pacific time) (1 h) Fri Jan 15, 9:00 AM Fri Jan 15, 9:00 AM −1 h
Vancouver → Seattle area (Pacific time) (1 h) Thu Jul 15, 9:00 AM Thu Jul 15, 10:00 AM 0 h
Calgary → Vancouver (1 h 25 min) Fri Jan 15, 9:00 AM Fri Jan 15, 9:25 AM −1 h
New York → London (US–UK mismatch week) (7 h) Sat Mar 20, 7:00 PM Sun Mar 21, 6:00 AM +4 h
Los Angeles → New York overnight, clock-change night (5 h 15 min) Sat Nov 6, 10:00 PM Sun Nov 7, 5:15 AM +2 h

What the table shows:

  • Long-haul east (Vancouver–London) arrives the next day at lunchtime even though the flight is under 10 hours.
  • Across the date line (Los Angeles–Sydney) you skip a calendar date: a Friday-night departure lands on Sunday morning. Coming back, an 11:00 AM Sunday departure from Sydney arrives at 5:30 AM on the same Sunday in Los Angeles, before it “left”. See the International Date Line explained.
  • Canada’s new rules: British Columbia now stays on UTC−7 all year (BC Government), while Washington State still changes. In winter, Vancouver is an hour ahead of Seattle, so a 1-hour hop departing 9:00 AM lands at 9:00 AM. In summer the two clocks match and it lands at 10:00 AM. Alberta’s UTC−6 (Government of Alberta) puts Calgary 1 hour ahead of Vancouver all year.
  • Mismatch weeks: between March 14 and 27, 2027, New York is only 4 hours behind London, because the US has changed its clocks and the UK has not, so a 7:00 PM departure arrives an hour earlier on the London clock than it would in January.
  • Clock-change night: on the night of November 6–7, 2027, New York falls back at 2:00 AM. A Los Angeles red-eye leaving 10:00 PM Saturday with a 5 h 15 min flight time lands at 5:15 AM on Sunday, +2 h on the clock instead of the usual 3, because the clocks in New York went back an hour during the flight.

Practical checks before you fly

  • Read the arrival date, not only the time. Overnight and date-line flights often arrive one or even two calendar dates later. Booking sites often mark this with “+1” or “+2”.
  • Connections are shown in local time at the connecting airport, so the gap between your two flights is a straight subtraction there.
  • Hotels and car rentals also run on destination time; book them using the printed arrival date.
  • Your phone normally switches zones by itself after landing if the automatic time zone setting is on (on iPhone, Settings > General > Date & Time; on Android, in the Clock app settings).
  • Jet lag depends on the offset difference, not the flight length: see jet lag by time difference.

How we checked

Every example was computed with Python zoneinfo on IANA tzdata 2026f by converting the departure to UTC, adding the sample flight time and converting to the destination zone. A second calculation applied the formula above to the printed local times and had to give back the same flight time; all nine matched. We then checked every offset used, every half hour through 2027, with a second reader of the same data (the system C library’s localtime()), with no mismatches. Airline, IATA and FAA pages were read on November 9, 2026.

Sources

Frequently asked questions

Are flight times in local time?

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

Are flight arrival times local time?

Yes, the arrival time and date are those of the destination airport, which is why an overnight or date-line flight can show a later (or earlier) date.

How do I work out how long a flight really is?

Subtract the departure time from the arrival time, then subtract the destination’s UTC offset minus the origin’s. For a westbound flight that second number is negative, so the flight is longer than the printed times suggest.

Why does my flight arrive before it leaves?

Eastbound across the International Date Line, the clock goes back about a day. A Sydney–Los Angeles flight can land on the morning of the same date it departed.

What happens if the clocks change during my flight?

The arrival time is still printed in local time at the destination, so it already includes the change. On the night clocks fall back, the printed gap between departure and arrival is an hour shorter than usual for the same route.

Similar Posts