How do you read a time-zone change on an itinerary?
Read a time-zone change by taking every printed time as local to the airport or station beside it, then using the UTC offsets on that date if you need to know how long the trip actually takes. The gap between the departure clock and the arrival clock is not the duration. It is two different local clocks. The worked numbers below are illustrative. They are not a route, and they are not a substitute for the offset on your ticket date.
Two local times, one elapsed trip
A confirmation shows “depart 22:00” and “arrive 07:00” because each of those is the civil time at that end. RFC 7808 describes a time zone as the past and predicted future timekeeping of a set of clocks that are meant to agree. It also says the phrase does not mean “a region on one UTC offset, maybe with daylight saving.” Several named zones can share a label in ordinary speech and still differ.
To get the elapsed time:
- Write the departure local time and its offset from UTC on that date.
- Convert departure to UTC by subtracting the offset. An offset of UTC+2 means you subtract two hours. An offset of UTC−5 means you add five hours.
- Do the same for arrival.
- Subtract UTC departure from UTC arrival. If you crossed midnight in UTC, count that date change. The result is the duration.
- The hotel date is the arrival’s local date, whatever the arithmetic did to the calendar.
IANA publishes the time zone database that software uses for those offsets, including daylight-saving rules. The public page listed version 2026f, released 27 October 2026, when this guide was written. The database is updated because governments change boundaries, offsets, and daylight-saving rules. IANA’s theory notes say the database is not authoritative and that anyone who needs an official answer should check the national standards body. For a ticket you already hold, the carrier’s printed local times are the operational times. The offsets explain them. They do not overrule the ticket.
A labeled eastbound example
Every city and offset in this section is made up. Do not apply the numbers to a real trip.
Depart Northport Tuesday 22:00, offset UTC+1. Arrive Eastport Wednesday 16:00, offset UTC+8.
Departure in UTC is Tuesday 21:00, because you subtract one hour. Arrival in UTC is Wednesday 08:00, because you subtract eight hours. From Tuesday 21:00 UTC to Wednesday 08:00 UTC is 11 hours. That is the elapsed time.
The clock faces moved from 22:00 to 16:00 the next calendar day, which is eighteen hours on a single clock and the wrong duration. Eleven hours is the flight. The local arrival at 16:00 is the afternoon the itinerary can use.
What counts as a travel day calls Tuesday a travel day in this picture, and Wednesday an arrival day if 16:00 local plus the ride to the hotel eats the rest of it. How to plan around jet lag applies because the shift is seven hours east, which is more than the three zones on CDC’s page. The time-zone line and the jet-lag line are different jobs. One tells you when you land. The other tells you how heavy to make the next days.
A labeled eastbound date-line example, with a date that does not advance
This is the eastbound crossing, not a short westbound hop. Depart Eastport Friday 10:00 at UTC+12. Arrive Westbay Friday 06:00 at UTC−10. Again, these offsets are invented for the arithmetic. A westbound crossing, such as UTC−8 to UTC+9, moves the arrival calendar forward instead.
Departure in UTC is Thursday 22:00, because UTC+12 at 10:00 Friday is 22:00 Thursday in UTC. Arrival in UTC is Friday 16:00, because UTC−10 at 06:00 Friday is 16:00 Friday in UTC. Elapsed time is 18 hours.
Locally, you left at 10:00 Friday and landed at 06:00 Friday. The hotel night is Friday in Westbay. You did not gain a free city day on Thursday. Thursday was still home, or it was a UTC date in the middle of the flight. When a ticket shows an arrival on the calendar day before departure, use the ticket’s local dates. The city-day count uses the mornings you are actually in the city.
Daylight saving and same-name zones
A March trip and a November trip between the same two cities can show different clock gaps, because one end, or both, may have changed offset. IANA records those transitions as rules, and the rules themselves change. Before you subtract, read the offset for the travel date, not the offset you remember from a previous season and not the offset printed on a map of “standard time.”
Places that share a traditional zone name can disagree. IANA’s theory page uses America/Denver, which observes US daylight saving, and America/Phoenix, which does not. During the part of the year when Denver is on daylight time, those clocks differ by an hour. If an itinerary says only “mountain time,” it has not told you which clock. The airport’s local time on the confirmation has. A saved screenshot of that confirmation is the backup when a phone has not updated. What works offline covers what the screenshot can and cannot do. It will not show a gate change.
What to write on the itinerary
Next to each hop, write four fields: departure local time, arrival local time, both offsets on that date, and the elapsed time you computed. Add the local arrival date in words if the calendar does something that looks impossible. “Lands Friday 06:00 Westbay local, 18 hours after a Friday 10:00 Eastport departure” keeps the next reader from “correcting” the date.
Use the local arrival date for the hotel. A room booked for the UTC date, or for the date you still had at home, is a room on the wrong night. Use the local departure time for the alarm that gets you to the station. An alarm set on a phone that has not switched yet will ring at the home-time equivalent, which may be the middle of the night or hours after the train.
Connections inside one airport stay in that airport’s local times. Judge the gap with how much layover time you need. Convert to UTC when the two ends are different places and you want elapsed time or the size of the zone change. An overnight train that crosses a zone uses the same four fields. How to use an overnight train reads the arrival as local morning.
An illustrative misread, and the repair
Sam’s invented confirmation: depart 23:10 local, arrive 06:40 local the next day. Sam subtracts the clock faces and decides the flight is 7 hours 30 minutes, then books a museum for 10:00. The departure offset on that date is UTC+1 and the arrival offset is UTC−5. Departure is 22:10 UTC. Arrival is 11:40 UTC the next day. Elapsed time is 13 hours 30 minutes. The museum is a little over three hours after a long landing, with immigration and the ride still ahead. The repair is the four fields written on the hop, the museum moved to a later city day, and the arrival morning labeled as travel.
Keep both clocks on the same trip
Forward the confirmation to [email protected], or paste it, and the local departure and arrival from that email sit on one itinerary. Add a note with the offsets and the elapsed time you checked, especially when the arrival date looks earlier than the departure date. Itineraries can sync for offline use, which is useful on the aircraft when you want the printed local arrival and not a mental subtraction. Live gates, airline boarding passes, and maps you never saved still need a connection.
Frequently asked questions
Are the times on a ticket in my home time zone?
No. A departure time is the local time at the departure airport or station, and an arrival time is the local time at the arrival airport or station. Your phone may still show home time until it updates. The itinerary and the boarding screen use the local times.
Why is the arrival clock only a few hours after departure when the flight is long?
You crossed into a later offset, so the destination clock did not advance as much as the hours you were traveling. Subtract the offsets from a single reference, such as UTC, if you want the elapsed time. Subtracting the two local clock faces gives the wrong duration.
Can I land on the calendar day before I departed?
Yes, when you fly east across the International Date Line and the local clocks say so, for example from Asia or Oceania toward Hawaii or the Americas. Flying west across that line, such as from the Americas toward Asia, moves the calendar forward a day. The arrival date on the ticket is the date at the destination. Your hotel night and your city-day count use that local date, not the date you still had at home.
Do two cities in the same named zone always share a clock?
A traditional zone name can hide different rules. IANA's time-zone theory uses the North American mountain zone as the example: America/Denver observes US daylight saving, and America/Phoenix does not. On a date when those rules differ, the two cities do not share a clock. Read the offset for each place on the date you travel.
Related guides
- How do you plan the first days around jet lag?
Plan the first days around jet lag by keeping important events off the arrival and the day after a large time-zone change, and by using the destination's day and night once you land.
- What counts as a travel day?
A travel day is a date spent mainly on moving between places. It stays on the calendar and comes off the count of days you can give an anchor.
- How do you use an overnight train inside an itinerary?
Use an overnight train as both the night's lodging and a travel block that covers the evening you board and the morning you arrive. Keep the first anchor off that morning.
Sources
- IANA, Time Zone Database (accessed 2026-11-20)
- IANA, theory and pragmatics of the tz database (accessed 2026-11-20)
- RFC 7808, Time Zone Data Distribution Service (accessed 2026-11-20)