Travel tools
What Time Will My Flight Land? Time Zones and the Date Line
An overnight flight can arrive the next morning, while a Pacific crossing can land earlier on the same day. Departure dates, elapsed time, and destination clocks explain both.
Updated
The clock at your destination tells a different story
A flight leaves New York in the evening and lands in London the next morning. Another leaves Tokyo in the afternoon and reaches Seattle earlier on the same calendar day. Neither itinerary tells you its duration just by subtracting the two clock readings.
The reliable method is to start with the departure date and local time, add the actual elapsed journey time, and then show that instant in the destination's time zone. The date matters as much as the hour.
If you already have a ticket, begin with the airline's stated arrival date and time. The calculation is useful for understanding the itinerary and checking your plans; it does not replace the airline's schedule or live flight status.
Keep three pieces of information together
To work out an arrival time, you need:
- The departure airport and local date and time. “Tuesday at 7:30” is incomplete without knowing where that clock is.
- The elapsed duration. Use the scheduled duration for the leg you are calculating, not a distance divided by an assumed cruising speed.
- The destination airport and its time zone. Its UTC offset may depend on the arrival date.
Departure and arrival times in an itinerary normally refer to the local clocks at their respective airports. Check the labels in the booking or calendar app, especially if it can display everything in your current time zone.
For a manual calculation, UTC provides a common clock. Convert the departure to UTC, add the duration, and convert the result to the destination's local time. You do not add or subtract another hour for every time zone the plane crosses along the route.
An overnight flight from New York to London
Consider an illustrative flight departing New York at 7:30 p.m. on September 29, 2026, with a scheduled duration of seven hours. This is a calculation example, not a particular airline service.
On that departure date, New York is four hours behind UTC. The departure instant is therefore 11:30 p.m. UTC. Add seven hours and the result is 6:30 a.m. UTC on September 30. London is one hour ahead of UTC on that date, so the local arrival is 7:30 a.m. on September 30.
| Step | Date and time |
|---|---|
| Leave New York | September 29, 7:30 p.m. |
| The same departure in UTC | September 29, 11:30 p.m. |
| Add seven elapsed hours | September 30, 6:30 a.m. UTC |
| Show the result in London | September 30, 7:30 a.m. |
The itinerary spans twelve hours on the two local clock faces, but the scheduled journey lasts seven hours. The five-hour difference between the cities explains the rest.
A “+1” beside an arrival generally indicates the following calendar day. Read the actual date before booking the first hotel night or arranging a pickup; the small marker can carry more practical importance than the flight's distance.
Arriving earlier on the same day
Now consider a second illustrative flight: Tokyo at 3 p.m. on October 6, 2026, followed by nine hours of elapsed travel to Seattle.
Tokyo is nine hours ahead of UTC, so departure is 6 a.m. UTC. Nine hours later is 3 p.m. UTC. Seattle is seven hours behind UTC on that date, making the arrival 8 a.m. on October 6.
You arrive seven hours earlier by the destination's clock, but you have still spent nine hours traveling. Crossing the International Date Line changes the calendar labels used along the journey. It does not remove time from the flight.
The reverse direction can put an arrival one or even two calendar dates after departure, depending on the route and departure time. Always keep the full arrival date with the time.
Daylight saving makes a fixed offset unreliable
“London is five hours ahead of New York” is useful shorthand for much of the year. It is not a rule for every date. Places change clocks on different schedules, and many do not change them at all.
For a trip planned weeks ahead, use the rules for the departure and arrival dates. A city-based time zone such as America/New_York or Europe/London contains more information than a permanent label of UTC-5 or UTC+0. The IANA Time Zone Database tracks these rules and their changes.
This is also why a map's color bands are an explanation, not enough information to calculate every itinerary. The airport's actual zone and the selected date determine the local clock. A flight that overlaps a clock change needs the offset at arrival, which may differ from the offset at departure.
Use Mapsake's flight arrival planner
The Flight Distance tool in the Mapsake app combines the route with a time-zone view and an arrival calculation:
- Abrir Flight Distance from Tools and add the airports in travel order.
- Activar Time zones in the route map controls. You can explore the route on a flat map or globe.
- In Airport clocks, choose the leg you want to check. These clocks compare the airports at the same selected departure instant.
- Set the departure date and time. The departure control uses the selected origin airport's time zone.
- Enter the scheduled Flight duration. The control moves in 15-minute steps, so treat the result as a planning estimate when your ticket uses a different duration.
- Read the destination's arrival date, local time, and UTC offset in Arrival time.
Mapsake adds elapsed duration first, then formats the result in the destination zone. If it cannot resolve a supported airport's time zone, it says so instead of inventing an offset. The boundary layer is approximate, and the calculation is not connected to a live airline operations feed.
El gratuito browser Flight Distance Calculator is useful for route distances and multi-city mileage. The arrival-planning controls described here are in the app.
A connection adds another duration
For an itinerary with a stop, calculate each flight leg and the time between them. A seven-hour first flight, a two-hour connection, and a three-hour second flight total twelve elapsed hours before accounting for any further delays.
Do not compare the first departure clock with the final arrival clock and call the difference the layover. Compare the first arrival and second departure in the connecting airport's local time, including their dates. Check whether the itinerary changes airports as well; a city name alone does not establish that the connection happens in the same terminal or airport.
Mapsake's leg selector lets you inspect individual routes. It does not automatically validate a connection, add a transfer allowance, or determine whether you can clear immigration and reach the next gate in time.
Distance, flight duration, and arrival are different numbers
Great-circle distance answers how far apart two airports are along Earth's surface. Scheduled duration also reflects routing, winds, and ground time. A current arrival estimate can change again because of conditions on the day.
Use each source for the job it can do: a distance calculator for route comparisons, a time-zone calculation for understanding local dates, and your airline for the operative schedule and current status.
Once the arrival date is clear, the rest of the trip gets easier to plan. You can choose the correct hotel night, tell someone when to meet you, and stop wondering whether an early-looking arrival means you somehow found an unusually short flight.