How airlines display arrival time — local time always
Look at any flight ticket and you'll see a departure time and an arrival time. Both are in local time at the relevant airport — departure in the home airport's zone, arrival in the destination's zone. This convention seems intuitive once explained but trips up first-time international travelers.
For converting between airport zones to verify your ticket math, the time converter handles it.
The basic rule
Departure time: local time at the departure airport, on the day of departure.
Arrival time: local time at the destination airport, on the day of arrival.
Duration: the actual flight time in hours and minutes. NOT calculated from departure and arrival times.
This is universal — every international airline follows this convention.
Why duration is separate
If you only had departure and arrival times in different zones, you couldn't tell flight duration:
Example: Tokyo (UTC+9) to Los Angeles (UTC-8 in winter)
- Departure: 5 PM Tuesday Tokyo time
- Arrival: 10 AM Tuesday LA time
- Calendar shows arrival "before" departure
In actual hours flown: 12 hours (5 PM Tue Tokyo to 10 AM Tue LA, where Tokyo is 17 hours ahead of LA, so 17 - 5 = 12 hours of actual elapsed time).
Tickets show "duration: 12h 5min" or similar to disambiguate. Without duration listed, the calendar would be confusing.
Reading a ticket
A typical international ticket shows:
```
Outbound flight
Tokyo (NRT) → Los Angeles (LAX)
Departure: Tuesday May 19, 2026, 17:00 (5 PM)
Arrival: Tuesday May 19, 2026, 10:00 (10 AM)
Duration: 12 hours 5 minutes
```
To verify: use the time converter. 17:00 Tokyo time + 12 hours 5 minutes = the actual arrival moment in UTC. Convert to LA time to confirm.
The "weird arrival before departure" effect
Two scenarios where the calendar looks wrong:
Eastward trans-Pacific (Asia → Americas)
Tokyo to LA: depart 5 PM Tuesday Tokyo, arrive 10 AM Tuesday LA. The calendar appears to go backward.
This happens because crossing the international date line going east means you "lose" a day on the calendar. The ticket shows local times correctly; the calendar effect is real.
Westward trans-Atlantic (Europe → Americas, same day)
London to NY: depart 1 PM London, arrive 4 PM NY. The arrival "looks" 3 hours after departure but the actual flight is 7-8 hours.
This happens because NY is 5 hours behind London. 1 PM London = 8 AM NY. Add 7 hours flight time = 3 PM NY arrival. Or in your local time: depart 1 PM, arrive 4 PM — looks like 3 hours, was actually 7-8.
Both scenarios are normal. The ticket is right; the calendar effect is the time-zone math.
Why this convention works
Two reasons airline ticket displays use local time:
1. Practical for ground operations. The airport's clocks are local. Boarding announcements, gate calls, taxi clearance — all local time. If tickets used UTC, passengers would constantly need conversion.
2. Familiar for passengers. Most travelers want to know "what time will I arrive?" — meaning local time at destination. They don't usually care about the underlying UTC math.
The trade-off: the calendar can look weird when crossing zones. Tickets include duration to disambiguate.
Practical implications
When reading tickets:
1. Check both dates carefully. A flight departing late Tuesday might arrive Wednesday at destination — make sure you've got the right day.
2. Trust the duration. If departure to arrival looks like 1 hour but duration is 7 hours, you're crossing time zones. The duration is correct.
3. Verify using the time converter. Especially for international flights, paste departure and add the duration to get UTC; convert to destination zone.
4. Pack for arrival's time of day. If you arrive at 10 AM but it's 3 AM your home time, you'll feel like 3 AM. Plan accordingly.
5. Coordinate ground transportation in advance. Don't assume you can grab a taxi at 4 AM.
Specific scenarios
Long flights crossing dateline
NY → Sydney: usually requires a stop. The booking shows two flights, each with its own departure and arrival times. The total duration is sum of segments + layover.
```
JFK → LAX: depart 6 PM Mon NY, arrive 9 PM Mon LA. Duration: 6 hours.
Layover LAX: 2 hours.
LAX → SYD: depart 11 PM Mon LA, arrive 7 AM Wed SYD. Duration: 14 hours.
Total: 22 hours flying + 2 hours layover = 24 hours total.
```
The "Wed" arrival in Sydney is correct — you've crossed the international date line, and your departure date (Monday) becomes Wednesday on the other side.
Connections
For a layover, calculate carefully:
- Time between flights = arrival of segment 1 + layover - departure of segment 2
- These should all be in local time of the connection airport
Most booking systems calculate this for you. Verify if you're tight on time.
Time zone changes mid-flight
For a round-the-world ticket or a complex itinerary, tickets show local times at each segment. The "weirdness" of crossing multiple zones is built into the booking system.
Cancellations and rebooking
If a flight is delayed or cancelled, your new flight may be in a different time zone (e.g., rebooked through a different connection). The new ticket shows new times in new airports' zones. Trust the local times; verify the duration.
When tickets are wrong
Occasionally tickets show wrong times due to:
Booking system errors: rare but real. If you suspect an error, verify with the airline.
Time zone changes: if a country changes DST rules between booking and flight, ticket times might not reflect the change. Airlines usually update.
Schedule changes by airline: airlines occasionally change schedules. Check 24-48 hours before your flight.
If something looks wrong, contact the airline immediately. They have access to the actual schedule.
What about UTC on tickets?
Some specialized tickets show UTC alongside local times:
- Cargo flights: often UTC for operational consistency
- Aviation industry tickets: business class on long-haul sometimes shows both
- Charter flights: depending on the operator
- Military and government: often UTC
For passenger tickets on commercial airlines, UTC is rarely shown — local time is the standard.
What pilots see
Inside the cockpit, pilots and air traffic controllers use UTC ("Zulu time"):
- Pre-flight planning: UTC
- ATC communications: UTC
- Flight plans: UTC
- METARs (weather): UTC
- Aircraft transponder: UTC
The interface between aviation operations (UTC) and passenger information (local time) is at the cabin/gate boundary. Passengers see local time; operations is UTC.
How to plan around tickets
For complex international itineraries:
1. Build a timeline in UTC: convert each ticket's departure and arrival to UTC. Easier to reason about overlaps.
2. Then convert critical times to your home zone: when do you board? When does someone need to pick you up at home airport?
3. Plan for jet lag at destination: not just physical time but also calendar date confusion.
4. Check passport/visa requirements: they're often based on dates and may have UTC implications.
For one-off flights, the local time on the ticket is enough.
Tools that help
Booking sites: most show local time at each end automatically.
The time converter: verify ticket math by converting between airports.
Airline mobile apps: usually show ticket info in local time and adapt to your phone's zone.
TripIt or similar: aggregates itineraries. Useful for travelers with complex schedules.
Phone alarm: set an alarm for boarding time in destination zone (or your home zone, depending on what you want).
FAQ
Why does my flight "arrive before it departs"?
Because of crossing the international date line, the calendar shows the arrival on an "earlier" date. The actual flight takes hours; the local time at the destination just happens to be earlier on the same calendar day.
Should I trust the duration on the ticket?
Yes — duration is the actual flight time. Departure and arrival times are local at each airport.
What if there's a discrepancy?
Contact the airline. They have access to the actual schedule and can verify or correct.
How do I figure out my arrival time in my home zone?
Use the time converter — convert the destination's local arrival time to your home zone.
What about delays?
Delays are typically announced in local time at the airport. A "30-minute delay" at LAX means departure is 30 minutes later in LA time.
Can I just use UTC for everything?
For complex international itineraries, building a UTC timeline helps you reason about overlaps and connections. For everyday travel, local times on tickets are enough.
Bottom line
Airline tickets show arrival time in local time at the destination. Duration is shown separately. The calendar can look weird when crossing time zones, but the local times on the ticket are accurate. Trust the ticket; verify edge cases using the time converter.
For converting between airport zones, the time converter handles them.