A ticket prints two local times — the departure airport’s clock and the arrival airport’s clock — and nothing else. That single convention is why a transpacific flight can land on a different calendar day than the one it left, with only a small +1 or +2 beside the arrival time as warning.
Inside the airline, everything runs on UTC. Outside, the passenger gets two disconnected local times and has to reconcile them unaided. Airlines don’t explain this on the itinerary; the arithmetic is left to third-party guides.
Airlines know, to the minute, when a transpacific jet crosses the International Date Line. Air traffic control sees it in UTC. Crew-scheduling software sees it in UTC.
The person holding the ticket sees none of that — just a departure clock set to Los Angeles, an arrival clock set to Sydney, and a small +2 printed beside the arrival.
That gap between what the operation knows and what the itinerary shows is not a formatting lapse. It is the industry’s standard convention: local times at each end of the route, nothing more. The arithmetic a traveler needs to reconcile those two clocks — the time-zone offset, the calendar shift, the true elapsed flying time — is left off the page.
Ask a carrier why it presents flights this way and you will find yourself reading a third-party explainer rather than an airline page. The convention itself is rarely examined; the consequences get passed to the traveler.
The only clock you see is local
Universally, the times printed on a ticket or boarding pass are set to two different clocks. Departure follows the origin airport’s local time. Arrival follows the destination’s.
That is the entire convention, and it hides a great deal inside a small design choice.
Subtract the printed departure time from the printed arrival time and the number you get is not the flight’s duration. Baked into the gap between the two local times is the offset between the two airports — hours that are not spent in the air at all. The only way to recover the real flying time is to express both endpoints in UTC and subtract one from the other.
The point is easier to see on a real transpacific schedule. QF12 leaves Los Angeles at 21:25 and arrives in Sydney at 07:25. The visible difference between those two local times says nothing useful about the crossing.
The listed duration — 15:00 — is the number to trust, because it was already computed from UTC.
What the +1 actually counts
The +1 or +2 trailing an arrival time has nothing to do with a gate or flight number. It counts calendar days — specifically, how many days separate the date of departure from the date the aircraft lands, locally, at the other end.
Cross the International Date Line and the calendar shifts while the clock keeps its own pace. On QF12, the jet pushes back from Los Angeles in the evening and touches down in Sydney two calendar days later — the +2 beside that arrival counts those two days, not any extra hours in the air.
Flight deals
most people never see
Our AI monitors 150+ airlines for pricing anomalies that traditional search engines miss. Air Traveler Club members save $650 per trip per person on average: see how it works.
Each deal saves 40–80% vs. regular fares:
Why the same route prints a different departure a week later
Daylight saving time does not touch the aircraft. It moves the offset values inside the airlines’ automated databases. Change the offset for one city and the same UTC event prints a different local departure on the ground.
The Qantas QF12 schedule shows exactly that. Through March 7, 2026, the listing shows a 21:25 Los Angeles departure against a 07:25 Sydney arrival and a 15:00 duration. From March 8 through March 28, the departure shifts to 22:25, while the arrival, the +2 marker, and the 15:00 duration all stay put.
These rows come from FlightMapper, a schedule aggregator rather than the operating carrier — the best available snapshot from the retrieved material, not a primary-source fix.
| Route and flight | Published local departure | Published local arrival | Date marker | Published duration | Origin/destination offset state | Source |
|---|---|---|---|---|---|---|
| Los Angeles–Sydney, Qantas QF12 | 21:25 LAX | 07:25 SYD | +2 | 15:00 | Los Angeles UTC−8; Sydney UTC+10, according to the retrieved schedule listing | flightmapper.net |
| Los Angeles–Sydney, Qantas QF12 | 22:25 LAX | 07:25 SYD | +2 | 15:00 | Los Angeles UTC−7 after the US transition; Sydney UTC+10 in the cited schedule period | flightmapper.net |
| Source: FlightMapper | ||||||
The shift belongs to Los Angeles, whose offset moves from UTC−8 to UTC−7 after the US transition, while Sydney stays at UTC+10. The duration figure did not budge, because elapsed airborne time does not care whose local clocks just changed.
The clock behind the clock
Inside the airline, a flight is one UTC timestamp with a set of conversion rules wrapped around it. What the traveler sees is that same instant rendered twice — once on the origin airport’s clock for departure, once on the destination’s for arrival — after a time-zone database has converted it. The rules that translate the timestamp into those two readings, daylight saving among them, sit in software databases that carriers and booking systems keep current.
Edit a single rule and the same UTC event shows up as a different local time, even though nothing about the flight itself has changed. The passenger, meanwhile, gets the local clock readings and a +1 to reconcile them with — not the UTC flight time the system already computed.
That absence is the puzzle. Scheduling systems carry an elapsed duration for every segment, yet no standard, easy-to-read chart on airline sites places the UTC duration beside the local schedule. The rationale for local-only display is not spelled out on any carrier page this piece is based on; it is left to third-party guides and forum threads to explain.
Whether that is deliberate economy or simple inertia, no such explanation appears in the public-facing material reviewed for this piece.
What this means for you
Treat the arrival date as carefully as the arrival time. If a +1 or +2 sits next to the landing time, put that date on your calendar before you book a hotel, a connection, or a meeting — and never assume the departure date carries through.
To sanity-check any itinerary, convert both endpoints to UTC and compare that against the duration the carrier lists.
If the numbers don’t line up, trust the UTC version, not the clock arithmetic in your head.
Look over the itinerary again once a daylight saving change has passed, and once more shortly before you fly. DST shifts local printed times without changing elapsed flight time, and multi-leg trips deserve a leg-by-leg look at each arrival date against its own destination zone.
Key terms
- UTC
- UTC, or Coordinated Universal Time, is the single global clock that airlines and air traffic control use as a common reference. It does not shift with daylight saving or local borders, so every flight event can be recorded as one unambiguous instant. On a QF12 listing, the printed local times at each end are two conversions of that same instant, which is why subtracting them does not give the flying time.
- International Date Line
- The International Date Line is the boundary in the Pacific where the calendar date changes by one day. Crossing it shifts the local date while the clock keeps its own pace. QF12 crosses it between Los Angeles and Sydney, so an evening departure lands at 07:25 two calendar days later even though only 15 hours pass in the air.
- Daylight saving time
- Daylight saving time is the seasonal one-hour shift that many countries apply to their local clocks. In airline systems it changes the offset value stored for a city rather than the flight itself. When the US leaves standard time, QF12’s Los Angeles departure prints as 22:25 instead of 21:25, while the Sydney arrival and the 15:00 duration stay the same.
- Time-zone database
- A time-zone database is the software record of each region’s offset from UTC and its daylight saving rules. Carriers and booking systems keep these databases current so that a single UTC timestamp can be converted into the correct local reading at each end of a route. Change one rule in the database and the same QF12 departure prints an hour later in Los Angeles, with no change to the time in the air.
Questions? Answers.
Are flight times always shown in local time?
On passenger-facing documents, yes. Departure is set to the origin airport’s clock and arrival to the destination’s. A QF12 listing, for example, prints Los Angeles and Sydney local times at each end.
Do flight times adjust for time zones?
They don’t convert to a common clock for the passenger. The printed times stay local at each end, so the time-zone offset is baked into the difference between them. The same route can print a different local departure after a daylight saving change without any change to actual duration.
How did the American Airlines traveler’s date mix-up end up being resolved?
The traveler expected a Sunday 4:10 p.m. arrival in Hong Kong, but landed Monday at the same local time, missing Monday meetings. According to the Consumer Rescue account, the carrier refused compensation at first and later offered $1,000 in travel credits. No court decided the matter.
Does the one-hour departure shift on QF12 after the US clock change add an hour of flying time?
No. The post-transition listing shows a 22:25 Los Angeles departure instead of 21:25, but the Sydney arrival stays at 07:25 and the duration holds at 15:00. The only thing that moved was Los Angeles’s local offset.
