How Is Flight Time Calculated? The Real Method, Explained

By Lokesh RathoreUpdated 29 May 2026 · 7 min read

You book Delhi to Dubai, the airline says three hours forty-five minutes, and a little voice asks: jets cruise at nearly 900 km/h and the two cities are only about 2,000 km apart, so why isn't this closer to two and a quarter hours? I asked myself the same thing for years before I started building FTCfly. The honest answer is part simple arithmetic and part a few things almost nobody thinks about. Here is exactly how flight time is worked out, the same method the calculator on this site uses, and why no estimate is ever perfect.

The short version

Strip away the detail and the sum is tiny. Flight time is roughly the distance divided by the cruise speed, plus a fixed bit of ground time. Everything interesting hides inside those three numbers, so let us open each one up.

Step 1: the distance is not a straight line

The first surprise is the distance itself. On a flat map the shortest line between two cities looks straight, but the Earth is a ball, so the true shortest path curves. This is the great-circle distance, and it is why a Delhi to New York flight arcs up over the Arctic instead of running flat across the map. We work it out from each airport's latitude and longitude using a piece of spherical trigonometry called the haversine formula. For Delhi to Dubai that comes to about 2,184 km, which is not quite the number you would get by drawing a straight line on a wall map.

Step 2: how fast a plane really moves

A modern airliner cruises at roughly 800 to 900 km/h. But a flight is not all cruise. It spends the first fifteen minutes climbing and the last twenty or so descending, both slower than cruise, and it fights or rides the wind the whole way. So instead of the headline cruise figure, a realistic average speed for the whole journey is closer to 800 km/h. That is the number I settled on for the calculator after checking it against dozens of real schedules. Push it higher and short hops come out too quick; push it lower and long hauls drag.

Step 3: the half hour you never think about

Then there is the ground time. Before the wheels even leave, the aircraft pushes back, taxies out, and waits in the queue for the runway. At the other end it lands, taxies in, and parks. Add the gentle climb and descent and you get roughly thirty minutes that has nothing to do with distance. On a short Delhi to Mumbai hop that half hour is a big slice of the trip. On a fifteen-hour haul to New York it barely registers. The calculator adds a flat thirty minutes to every route to cover it.

What it looks like on real routes

Here is the method applied to a few routes I fly or get asked about, next to what the airlines actually schedule. I worked out the distance and the estimate myself; the typical times are rounded from current nonstop schedules.

Two things jump out. On the shorter routes the estimate sits a little under the schedule, because real flights are routed a few percent longer than the straight line and spend proportionally more time going slow. On the very long Bengaluru to San Francisco run the estimate is actually a touch high, because that flight rides strong tailwinds for much of the way. Across the board the method lands within about fifteen percent of reality, which is about the best a distance-and-speed estimate can do.

Why your boarding pass says something different

If you compare any estimate to the minute printed on your ticket, they will rarely match, and that is normal. Airlines quote block time, measured from the moment the aircraft pushes back from the gate to the moment it parks at the far end, not the pure time in the air. On top of that, three things move the real number:

• Winds. The jet stream blows from west to east, so an eastbound flight gets a push and a westbound flight fights a headwind. The same route can be forty minutes shorter one way than the other. This is why your return flight is often faster than the outbound.
• Routing. Real flights follow airways and steer around certain airspace, so the path is a few percent longer than the pure great circle.
• The aircraft. A newer long-range jet and an older one do not cruise at the same speed.

How to work it out yourself

If you enjoy the arithmetic, take the great-circle distance, divide by 800 to get hours of cruising, then add half an hour. For Delhi to Dubai that is 2,184 divided by 800, which is about 2.7 hours, plus 0.5, giving roughly 3 hours 15 minutes. If you would rather skip the trig, the flight time calculator at the top of this site does all of it in a second, and it also converts the arrival into local time at your destination, shows the time-zone gap, and estimates the jet lag. You can try Delhi to Dubai or type in your own route.

Frequently asked questions

Is flight time the same as time in the air?

Not quite. The figure airlines quote is block time, measured gate to gate, so it includes taxiing at both ends. The pure time in the air is a little shorter.

Why is my return flight longer than the outbound?

Winds. Flying east you ride the jet stream and arrive sooner; flying west you push against it. The distance is identical, the time is not.

How accurate is this estimate?

For a nonstop flight, usually within about fifteen percent of the schedule. It cannot predict the exact winds on your day, and it does not include layovers, so a connecting trip will always take longer.

None of this is guesswork dressed up as science. It is a clear estimate built from the distance, a realistic speed, and the half hour spent on the ground. Where it cannot be exact, the calculator says so. For the full method and its limits, see the disclaimer.