Enter your departure and arrival local date, time and time zone to get the exact flight duration and time zones crossed — with correct daylight saving time handling.
Enter your departure and arrival details and click Calculate to see your flight duration
This free flight time calculator works out exactly how long a flight is by comparing your local departure date and time with your local arrival date and time, across two different time zones. It's built for travelers who want the real flight duration rather than the misleading number you get from simply subtracting the two clock times printed on a boarding pass or booking confirmation.
Enter the local departure date, time, and time zone at the origin airport, then the local arrival date, time, and time zone at the destination airport. The calculator converts both moments onto a single UTC timeline using each time zone's real offset on the exact dates you entered — which automatically accounts for daylight saving time — then subtracts departure from arrival to get the exact elapsed flight duration in hours and minutes, plus how many time zones were crossed.
This tool is for anyone who needs an accurate flight duration figure rather than a rough guess: travelers double-checking an airline's stated flight time, people planning connections or pickups, frequent flyers estimating jet lag exposure, travel agents quoting multi-city itineraries, and aviation enthusiasts comparing route times. It works for any pair of the 16 major world time zones it supports, in either direction.
Airlines and booking sites list departure and arrival times in local time at each airport, which makes a quick mental subtraction unreliable — flying from New York to London and subtracting a 9pm arrival from an 8am departure gives the wrong answer unless you account for the 5-hour time difference between the two cities. On long-haul or westbound routes the arrival clock can even show an earlier time, or an earlier date, than departure, which confuses a plain subtraction even more. Getting the actual duration right also matters for planning connections, in-flight sleep, and understanding how much jet lag to expect.
The exact method this calculator uses to turn two local times, in two time zones, into one accurate duration
Each time zone's real UTC offset — including whether daylight saving time is in effect — is looked up for the specific calendar date you entered, not a fixed year-round value. Converting both local times to the same UTC timeline first means the subtraction is always correct, no matter how large or small the offset between the two cities is, and no matter which direction you're flying.
Each of the 16 supported time zones is mapped to its real IANA identifier (e.g. America/New_York), so the browser's built-in time zone database supplies the correct offset for any date.
Because the offset is looked up for the exact date entered, a flight that departs before a daylight saving change and arrives after one is still calculated correctly.
A positive "time zones crossed" figure means the destination is ahead of the origin in UTC offset (typically eastbound travel); negative means it's behind (typically westbound).
From entering your itinerary to reading your exact flight duration
Type the local departure date and time exactly as shown on your boarding pass or booking confirmation.
Choose the time zone that matches the departure airport's real-world location from the dropdown list.
Type the local arrival date and time exactly as shown on your boarding pass or booking confirmation — remember overnight flights may land the next calendar day.
Choose the time zone that matches the arrival airport's real-world location from the dropdown list.
See your exact flight duration, the number of time zones crossed, and both local times side by side.
Two real-world scenarios, worked step by step
Depart New York (ET) at 9:00 AM on July 20, 2026, and arrive London (GMT/BST) at 10:30 PM the same day.
Depart Tokyo (JST) at 5:00 PM on March 15, 2026, and arrive Los Angeles (PDT) at 11:00 AM the same calendar day — an arrival clock time earlier than departure.
Explanation: Both examples show why converting to UTC first is essential. In Scenario 1, naively subtracting "10:30 PM" minus "9:00 AM" would suggest 13.5 hours — far more than the real 8h 30m — because it ignores the 5-hour zone difference. In Scenario 2, the arrival clock time (11:00 AM) is actually earlier than the departure clock time (5:00 PM) on the same calendar date, which would produce a nonsensical negative duration under naive subtraction; converting both to UTC resolves this correctly to a normal 10-hour flight.
What each figure in your results panel actually means
| Result | What It Means | Why It Can Look Confusing |
|---|---|---|
| Flight Duration | The true elapsed time between departure and arrival, calculated on a single UTC timeline | It rarely matches a plain subtraction of the two local clock times shown on your ticket |
| Time Zones Crossed | The difference in UTC offset between the arrival and departure zones, rounded to the nearest hour | It can be negative (westbound) or larger than the number of "real" zone boundaries on a Date Line crossing |
| Departure (local) | The exact date, time and zone you entered for takeoff | Shown only to confirm your input, not adjusted in any way |
| Arrival (local) | The exact date, time and zone you entered for landing | Can display an earlier clock time or date than departure on long westbound or Date-Line-crossing routes |
Elapsed time vs. local clock times: Flight Duration is the only figure that tells you how long the trip actually took. The two local time rows are anchors for your itinerary, not a duration — treat them as reference points, not something to subtract by hand.
Why crossing time zones is confusing: Every time zone you cross shifts the clock without changing the passage of time. A flight can take 8 hours in the air while the wall clock appears to jump forward 13 hours (or even backward), simply because the destination uses a different offset from UTC. This is also the same underlying shift that causes jet lag.
This calculator is a scheduling and duration tool. It reports elapsed time between the two moments you enter — it does not verify flight status, gate changes, or real-time delays.
For expected recovery time after crossing time zones, use the "Time Zones Crossed" figure together with NeftCal's Jet Lag Calculator.
Where an accurate, time-zone-aware flight duration is genuinely useful
Check the real duration of each leg before deciding whether a layover window is realistic.
Work out exactly when you'll land to book calls or meetings with accurate buffer time.
Give clients an accurate total flight time instead of an airline's approximate figure.
Use the time zones crossed figure to anticipate how many days of adjustment to expect.
Tell family or drivers precisely when a flight lands in local time, not a rough estimate.
Calculate each segment of a multi-city itinerary separately for an accurate total travel time.
Compare scheduled block time across airlines or routings for the same city pair.
Know your exact landing time to plan when you'll realistically be reachable again.
Track when international guests land to plan transport and welcome logistics.
Work out realistic arrival windows when booking flights home or to a host country.
Verify that the duration an airline or travel site quotes matches your own calculation.
Knowing the true duration helps decide how much of the flight to spend sleeping versus staying awake.
See why a return flight often shows a different duration than the outbound leg on the same route.
Illustrate how time zones, UTC offsets, and the International Date Line affect travel time.
What this flight time calculator does well, and where it can't replace real-time flight data
Why the same real flight duration can look wildly different depending on the direction of travel
| Direction | Typical Offset Change | Effect on Local Clock | Example Route |
|---|---|---|---|
| Eastbound (offset increases) | Positive "time zones crossed" | Arrival local time appears to jump forward, beyond the real flight duration | New York → London |
| Westbound (offset decreases) | Negative "time zones crossed" | Arrival local time appears to jump backward, sometimes to an earlier hour or date | Tokyo → Los Angeles |
| North-south, same offset band | Near zero "time zones crossed" | Local clock times closely track real elapsed duration | New York → São Paulo (partial overlap) |
| Crossing the International Date Line | Large offset swing (can exceed 12 hrs) | Arrival calendar date can be the same, or even earlier, than departure date | Los Angeles → Sydney |
Summary: This flight time calculator gives you an instant, free, time-zone-aware flight duration and a signed "time zones crossed" figure from any local departure and arrival date/time — a reliable planning tool, not a real-time flight tracker. Pair it with the Jet Lag Calculator and Trip Cost Calculator for a fuller picture of your trip.
Common questions about calculating flight duration
Official references to complement this calculator
Plan the rest of your trip