Flight Arrival Time Calculator

What time will I land?

Enter when you leave, your flight's duration, and both time zones. This tool works out your exact local arrival time — and shows how many hours actually pass on the clock, which is rarely the same as your time in the air. Already know both times? Switch to How long was my flight? to get your real time in the air.

Looking up a specific flight? This calculator uses the scheduled departure time and flight length from your booking, so it gives the planned local landing time. For live status, delays or gate changes, check the flight number in the airline's app or on the arrival airport's website. If your departure is delayed, enter the new time here for the updated landing time.

Time in the air
Clock time that passes

Runs entirely in your browser using your device's IANA time zone data; nothing you enter is sent anywhere.

What time will I land? The quick rule

Arrival time = departure time + flight length + the time difference between the two cities. The time difference is positive when the destination is ahead of you (usually flying east) and negative when it is behind (usually flying west). For example, a 7-hour flight leaving New York at 7:00 p.m. lands in London at 7:00 p.m. + 7 hours + 5 hours = 7:00 a.m. the next day, London time. The calculator above does the same sum for any two time zones and any date, including daylight saving changes.

Typical landing times on popular routes

These examples use January dates and typical nonstop flight lengths. Your own flight length is on your booking; enter it above with your real departure time for an exact answer.

RouteTypical flightLeave (local)Land (local)
New York → Londonabout 7 h7:00 p.m.7:00 a.m. next day
New York → Parisabout 7 h 15 m6:00 p.m.7:15 a.m. next day
Chicago → Londonabout 8 h6:00 p.m.8:00 a.m. next day
New York → Los Angelesabout 6 h8:00 a.m.11:00 a.m. same day
London → Dubaiabout 7 h9:00 p.m.8:00 a.m. next day
London → Singaporeabout 13 h9:00 p.m.6:00 p.m. next day
New York → Tokyoabout 14 h1:00 p.m.5:00 p.m. next day
Los Angeles → Tokyoabout 11 h 30 m12:00 p.m.4:30 p.m. next day
Los Angeles → Sydneyabout 15 h10:30 p.m.8:30 a.m. two days later

How long was my flight? Working it out from two local times

If you know when you left and when you landed but not how long you were in the air, switch the calculator to How long was my flight? and enter both local times with their time zones. It converts both to UTC and subtracts, so the time zone change drops out of the answer.

For example, say you left Chicago at 5:20 p.m. on September 8 and landed in London at 7:30 a.m. on September 9. Chicago is on Central Daylight Time (UTC−5) in September, so you left at 10:20 p.m. UTC. London is on British Summer Time (UTC+1), so you landed at 6:30 a.m. UTC. The flight took 8 hours 10 minutes, even though the clocks moved on by 14 hours 10 minutes.

A note on "CST": many people say Central Standard Time all year, but from mid-March to early November Chicago, Dallas and the rest of US Central Time are on Central Daylight Time, one hour ahead of standard time. Pick the city rather than the abbreviation and the calculator applies whichever one is in effect on your date.

Time differences for popular routes

Add these to your departure time plus the flight length. Some routes change by an hour during the year because the two cities switch to daylight saving time on different dates, or only one of them uses it at all.

RouteJanuaryJuly
New York → London+5 hours+5 hours
New York → Paris+6 hours+6 hours
Chicago → London+6 hours+6 hours
New York → Los Angeles−3 hours−3 hours
London → Dubai+4 hours+3 hours
London → Mumbai+5½ hours+4½ hours
London → Singapore+8 hours+7 hours
New York → Tokyo+14 hours+13 hours
Los Angeles → Tokyo+17 hours+16 hours
Los Angeles → Sydney+19 hours+17 hours

Flights across the Pacific show why the calendar can jump: leaving Los Angeles on a Tuesday evening for Sydney, you land on Thursday morning, because 19 hours of time difference plus a roughly 15-hour flight add up to more than a full day. Coming back, you can land in Los Angeles on the same calendar day you left Sydney, apparently before you took off.

Checking someone else’s flight

Picking someone up from the airport? Enter their departure airport’s time zone, their scheduled departure time and the flight length from their booking. The result is the landing time in the destination’s local time, which is the time shown on the airport’s arrivals board. Allow extra time for taxiing, immigration and baggage, which often add 30 to 60 minutes on international arrivals.

Why "hours in the air" and "hours on the clock" don't match

A flight's duration is a fixed span of real time — a 6-hour flight takes 6 hours no matter where it goes. But the clock reading when you land depends on how many time zones you crossed, not how long you flew. Fly east and the destination clock has already moved further ahead, so it can look like you arrived "later" than 6 hours suggests. Fly west, and the opposite happens: the clock can show you arriving earlier than you left, even though you spent real hours in the air. Neither is a trick — it's the same arithmetic behind any time zone conversion, just applied across a journey instead of a single moment.

Doing it by hand

The reliable method is to route everything through UTC, the same way any time zone conversion works. Take your departure time, convert it to UTC using your origin zone's offset, add the flight duration in hours and minutes, then convert that UTC result into the destination zone's local time using its offset on the arrival date (not the departure date — this matters if a daylight saving change falls between the two). This calculator does exactly that, using your browser's own time zone database so the offsets are always current.

Common flight-duration pitfalls

A worked example

Suppose you depart New York at 7:00 p.m. on a Tuesday, and the flight to London takes 7 hours. New York is UTC−5 in winter, so departure in UTC is midnight Wednesday. Add 7 hours: 7:00 a.m. UTC Wednesday. London in winter is UTC+0, so you land at 7:00 a.m. London time — meaning the clock moved 12 hours forward even though you were in the air for only 7, because you crossed five time zones eastward while you flew.

Frequently asked questions

What time will I land?

Enter your departure date and time, the time zone you leave from, the time zone you land in and the flight length, then press Calculate. The result is your arrival time in the destination’s local time, with the date.

Can this tell me if my flight is delayed?

No. The calculator works from the scheduled departure time and flight length, so it gives the planned local landing time. For live status, delays or gate changes, look up the flight number in the airline’s app or on the arrival airport’s website. If the departure is delayed, enter the new departure time here to get the updated landing time.

How do I work out what time someone else’s flight lands?

Use the same steps with their details: their departure time and airport time zone, the destination time zone and the scheduled flight length. The answer shows the destination’s local time. To see what that is on your own clock, convert it with the time zone converter.

Is the arrival time on my ticket in local time?

Yes. Airlines show each departure and arrival in the local time of that airport, which is why a ticket can show you landing before you took off on a westbound flight. This calculator gives the same kind of answer.

Does this account for daylight saving time?

Yes. It uses your browser's built-in time zone database, which applies whichever offset is actually in effect for the departure and arrival dates you enter — including any DST transition that happens to fall between them.

Why does my arrival date sometimes jump forward by two days?

This happens on long westbound flights that cross the International Date Line, most often on transpacific and trans-Tasman routes. The date line adds a full calendar day independent of the time zone shift, so a 13-hour flight can still show a two-day date change.

Can I use this for a multi-leg trip with a layover?

Calculate each leg separately: use your layover airport's arrival time as the departure time and zone for the next leg, and repeat.

Why is "clock time" different from "flight time"?

Flight time is how long you're actually in the air, unaffected by geography. Clock time is the difference between the two local readings at departure and arrival, which shifts with every time zone you cross — see the explanation above for why they diverge.

How long was my flight if I know when I left and when I landed?

Switch the calculator to “How long was my flight?” and enter the departure and arrival dates, local times and time zones. It converts both times to UTC and subtracts, so the answer is your real time in the air, not the gap between the two clock readings.

Is CST the same as Central Time in the summer?

Not exactly. Central Standard Time (CST) is UTC−6 and applies from early November to mid-March. The rest of the year Chicago and the US Central zone use Central Daylight Time (CDT, UTC−5), although many people still call it CST. Choose “US Central — Chicago” and the calculator uses whichever one is in effect on your date.

Need to double-check a specific time zone conversion instead of a full flight? Use the time zone converter. Comparing two cities' clocks side by side? Try the world clock.

Worked examples: what time will I land?

The calculator above does this for you, but here's how it works on real routes — including overnight flights, the International Date Line and daylight saving time.

Local landing time = departure time + flight length + time difference (destination minus origin)

I leave London at 8:00 PM Friday on a 4-hour flight to Moscow. When do I land?

3:00 AM Saturday, Moscow time (winter). 2:00 AM in summer.

In winter London is on GMT (UTC+0), and Moscow is UTC+3 all year. 8:00 PM + 4 hours of flying + 3 hours of time difference = 3:00 AM the next day. In summer London is on BST (UTC+1), so the difference is only 2 hours and you land at 2:00 AM.

I leave Los Angeles at 11:00 AM Monday on a 12-hour flight to Tokyo. When do I land?

3:00 PM Tuesday, Tokyo time (summer). 4:00 PM in winter.

Tokyo (UTC+9) is 16 hours ahead of Los Angeles in summer (PDT, UTC−7) and 17 hours ahead in winter (PST, UTC−8). Flying west across the International Date Line skips most of a day: 11:00 AM + 12 hours + 16 hours = 3:00 PM the next day.

I leave Tokyo at 5:00 PM Tuesday on a 10-hour flight to Los Angeles. When do I land?

11:00 AM Tuesday, Los Angeles time (summer). 10:00 AM in winter.

Flying east across the date line, you land earlier on the clock than when you took off: 5:00 PM + 10 hours − 16 hours = 11:00 AM the same day.

I leave New York at 7:00 PM on a 7-hour overnight flight to London. When do I land?

7:00 AM the next morning, London time.

London is normally 5 hours ahead of New York: 7:00 PM + 7 hours + 5 hours = 7:00 AM. Watch the daylight saving gap: the US and UK change their clocks on different dates, so for a few weeks each spring and fall the difference is only 4 hours. Between Oct 25 and Nov 1, 2026, for example, the same flight lands at 6:00 AM.

My flight from Chicago to Los Angeles takes 4 hours 30 minutes and I need to land before 10:00 AM Pacific. When should I leave?

By 7:30 AM Chicago time.

Work backward. Los Angeles is 2 hours behind Chicago all year, so 10:00 AM Pacific is 12:00 PM Central. Subtract the 4 h 30 min flight and you get 7:30 AM Central.

I left Dallas at 5:20 PM on Sept 8 and landed in London at 9:30 AM on Sept 9. How long was the flight?

10 hours 10 minutes.

Convert both times to UTC. In September Dallas is on CDT (UTC−5), so 5:20 PM = 10:20 PM UTC. London is on BST (UTC+1), so 9:30 AM = 8:30 AM UTC. From 10:20 PM to 8:30 AM the next day is 10 hours 10 minutes. The flight duration calculator on this page works this out for you.