Routing & planning

The International Date Line and flight dates

Why a Pacific crossing can land before it took off, which routes are affected, and how to work out the arrival date you should actually book hotels against.

Published 9 September 2026 · Updated 9 September 2026

Fly from Los Angeles to Sydney and you lose a day. Fly back and you land before you left. Neither is an error on the itinerary, and neither is really about time zones — it is a separate effect, layered on top of them, and the two get confused constantly.

What the line actually is

The International Date Line runs roughly down the 180° meridian, opposite Greenwich, with detours around inhabited territory so that island groups are not split across two calendar dates. It is not a treaty or a law; it is a convention, which is why countries have moved themselves across it — Samoa did so in 2011 to align its working week with Australia and New Zealand.

Crossing it changes the calendar date by one full day, independently of how many hours you have been flying.

  • Westbound across it, you lose a day. Depart Monday, arrive Wednesday.
  • Eastbound across it, you gain one. Depart Sunday morning, arrive Sunday — earlier that same morning.
How the International Date Line changes the calendar on a Pacific crossing Flying west from Los Angeles departing Monday evening, the aircraft crosses the date line and arrives in Sydney on Wednesday morning — Tuesday never occurs for the passenger. Flying east from Sydney departing Sunday morning, the aircraft arrives in Los Angeles earlier the same Sunday morning, so the passenger experiences part of Sunday twice. WESTBOUND · LAX → SYD MONDAY TUESDAY WEDNESDAY depart 22:30 arrive 06:45 about 15 hours in the air Tuesday never happens EASTBOUND · SYD → LAX SUNDAY depart 10:00 arrive 06:30 — same day
Crossing the line changes the calendar date by a full day, on top of any time-zone shift. It is why a westbound Pacific flight can skip a date entirely, and an eastbound one can land before the hour it departed.

Why this is not the same as a time-zone change

A time-zone change shifts the clock. The date line shifts the calendar. On a long Pacific flight both happen at once, and the combination is what produces the results that look impossible.

Take Los Angeles to Sydney, one of the five date-line routes in this site’s route directory:

Depart  LAX  Mon 22:30   (UTC−7)
Flying time  about 15 hours
Arrive  SYD  Wed 06:45   (UTC+10)

Fifteen hours of flying, but the calendar moves two days. Roughly seventeen hours of that is the time-zone offset; the rest is the date line. Tuesday simply does not occur for you.

Now the reverse, Sydney to Los Angeles:

Depart  SYD  Sun 10:00   (UTC+10)
Flying time  about 13 hours
Arrive  LAX  Sun 06:30   (UTC−7)

You land three and a half hours before you took off, by the clock. You have still been in the air for thirteen hours.

Which routes cross it

Any route whose great-circle path passes through the ±180° meridian. In practice that means flights between East Asia or Oceania and the Americas. Of the forty airport pairs in the route directory, five cross it:

Each of those pages draws the great-circle path, and the arc visibly leaves one edge of the map and re-enters at the other — which is the date line, drawn.

Routes between Europe and Asia do not cross it, however long they are. London to Singapore is nearly 11,000 km and changes no calendar date beyond what the overnight departure implies.

The mistakes this causes

Hotel bookings on the wrong night. The single most common one. You book the arrival night from memory — departure date plus one — and on a westbound Pacific crossing that is a day early. The room sits empty on Tuesday while you arrive Wednesday.

Visa and immigration forms with the wrong entry date. Some applications ask for your date of arrival. Copying the departure date, or guessing, produces a date that does not match your boarding pass.

Connections that look impossible and are fine, or look fine and are not. A connection time computed by subtracting a departure date from an arrival date, rather than reading the times as printed, goes badly wrong here.

Anniversaries and deadlines. If something is due on a given date and you cross the line, “the day before I land” may not be a day you experience.

How to get it right

The itinerary is authoritative. Both times on it are local to their own airport, and the dates shown are the dates you will actually be there. Do not adjust them.

If you are planning rather than reading — deciding which night to book, or which date to put on a form — compute it rather than estimating. The flight time zone planner takes a departure airport, date and time plus a destination, and returns the local arrival time, the offsets in force on that date, and an explicit flag when the calendar day changes. On a date-line route it will tell you that you are arriving two days later, or earlier the same day.

For a multi-leg trip the effect compounds, because each leg’s arrival date is the next leg’s baseline. The multi-city trip planner chains them so one wrong date does not propagate through the whole plan.

The 24-hour trick that fails

A rule of thumb people reach for: “add the flying time and the zone difference, then adjust by a day if you crossed the Pacific.” It mostly works and fails in exactly the cases that matter, because daylight saving changes the zone difference at different times of year in each hemisphere — and the southern hemisphere shifts in the opposite months to the northern one.

Between March and April, and again in October, the gap between Sydney and Los Angeles is not what it is for the rest of the year. Any arithmetic that assumes a fixed offset will be an hour out, which occasionally is enough to move the date.

Resolving offsets for the actual travel date rather than a remembered constant is why the tools here work from each airport’s IANA time zone. See flight time zones explained for the full treatment.