Flight Time Calculator

How long is that flight, really?

Airline schedules hide a lot of plumbing: winds, airways, slot buffers, turnaround politics. Underneath all of it sits a clean physical baseline — the great-circle distance between two airports and the time a jet needs to fly it. This tool computes exactly that for a curated set of the world's major hubs: air distance in kilometres, miles and nautical miles, plus a gate-to-gate estimate built from an 850 km/h cruise and a 45-minute block for taxi, climb and approach, with the method printed beside the number.

Pick JFK to LHR and you get roughly seven hours of still-air truth; pick Tokyo to Sydney and you feel the Pacific. The estimate is labelled as such because real schedules add the jet stream's opinion — eastbound transatlantics run short, westbound long — and airway routing rarely flies the perfect arc. That makes the tool ideal for sanity-checking a quoted schedule, comparing routing options, or satisfying the window-seat curiosity about what the planet's geometry says. It hands off cleanly to the Nearest Airport finder on one side and the nautical distance tools on the other, completing the small aviation corner of the platform.

Worked examples

• New York → London — measures 5,570 km (3,461 mi) on the great circle, initial bearing 51° — NE, the familiar north-east arc over the Atlantic.
• Tokyo → Sydney — comes in at 7,826 km, bearing 170° (S) — a southern-hemisphere leg that flat maps dramatically misdraw.
• Paris → Berlin — is a short European hop of 877 km where road distance runs noticeably longer; compare the driving calculator to feel the detour penalty (~20% here).

The geometry of distance: why the crow flies in arcs

Distance on a planet is not distance on paper. The shortest path between two points on Earth is an arc of a great circle — a circle whose centre is the planet's centre — and every serious distance tool computes that arc, not a straight line on a flat map. The standard formula, haversine, turns two latitudes and a longitude difference into a central angle and multiplies by Earth's mean radius. On the WGS84 sphere it agrees with survey-grade ellipsoidal geodesics to about three parts in a thousand, which is far tighter than the uncertainty in most real questions, like where exactly 'the city centre' is.

Bearings complete the picture. The initial bearing is the compass angle you would steer at departure; on a great circle it drifts continuously as the route crosses meridians, so the final bearing at arrival is generally different. That drift is why intercontinental flights arc toward the poles on flat charts — they are not detouring, they are taking the shortest path, and the map is what bends. Tools that report a single 'direction' for a long route are hiding this geometry; the honest display shows initial bearing, final bearing and the compass point for humans.

Finally, keep the family of distances distinct in your head: straight-line (the physical lower bound, right for radio and wildlife), road distance (what you drive, always equal or longer), and travel time (road distance reshaped by speed limits and network structure). Comparing the first two tells you how much geography taxes your route — a number that is itself interesting, whether you are planning a commute or pricing a delivery zone.

Tips & common mistakes

Always confirm which distance you need before quoting one: straight-line for physical questions, road distance for driving, and network time for schedules. The three can differ by half again in mountainous or island geography, and quoting the wrong one is the most common distance mistake in reports.

Remember that bearings are true-north by default. If you are transferring a bearing to a magnetic compass, add (or subtract) your local declination — it exceeds 10° in many inhabited regions and flips hemispheres of behaviour.

Use the midpoint tool instead of averaging coordinates when splitting journeys: latitude/longitude averages distort over long legs and fail across the date line, while the spherical midpoint follows the actual path the distance was measured along.

Distance literacy: choosing the right yardstick

Most distance errors are category errors: quoting straight-line where a road is meant, or a road where a schedule is meant. A useful discipline is to name the yardstick aloud in every sentence that uses a number — 'as the crow flies', 'by road', 'at free-flow speeds'. The three form a ladder of realism, each rung adding assumptions: the sphere's geometry, the network's topology, then human speed limits. Crow-flies is reproducible forever from coordinates alone; road distance depends on the mapping vintage; travel time depends on the traffic model. Knowing which rung your decision stands on tells you how much it can move.

The ladder also teaches when disagreement is a bug and when it is truth. If your road distance is shorter than your straight-line distance, something is wrong — topology cannot beat geometry. If two straight-line tools disagree by more than half a percent, one is using flat math or a wrong radius. And if bearings from A→B and B→A don't differ by roughly 180° (convergence aside from exact antipodal oddness), a tool is faking the back-bearing. These consistency checks cost seconds and catch most published nonsense.

How professionals use this

• State the yardstick in every sentence that carries a number; ambiguity is the enemy, not imprecision.
• Use nautical miles and bearings together for anything marine; statute miles and compass points for prose.
• For multi-point studies, export the matrix as CSV and let the spreadsheet hold the single source of truth.
• Check tool sanity with known pairs (Equator quarter ≈ 10,018 km; London–Paris ≈ 344 km) before trusting exotic ones.

Step-by-step masterclass

1. 1. Name the yardstick first — Decide straight-line, road or schedule distance before typing anything; the three form a ladder of realism and mixing them silently is the classic distance error.
2. 2. Enter endpoints at the right grain — City-to-city for comparisons, addresses for logistics, coordinates for datasets — the grain sets the honest precision of the answer you'll quote.
3. 3. Read bearing with the distance — A distance without direction is half a fact; the compass point turns the number into something a human can point at.
4. 4. Cross-check with a known pair — London–Paris ≈ 344 km, a quarter meridian ≈ 10,018 km; two seconds of calibration catches broken tools and broken inputs alike.
5. 5. Export the pair, not just the number — Share the URL or copy both endpoints; a distance without reproducible endpoints is unverifiable folklore.

Great-circle math is universal, but the meaning of 'between two places' varies by mapping culture: US users expect miles and ZIP-to-ZIP convenience, European users think in kilometres and postcodes, marine users in nautical miles — the unit table exists precisely so one calculation serves every convention without rounding arguments.

Related questions people ask

Quick glossary

Great circle

A circle centred on Earth's centre; its arcs are the shortest surface paths.

Haversine

The standard stable formula for great-circle distance on a sphere.

Initial bearing

Compass angle from true north at departure along a great circle.

Geodesic

The ellipsoid-true shortest path; haversine approximates it within ~0.3%.

Back bearing

The bearing from B to A, computed properly rather than assumed ±180°.

Convergence

Why initial and final bearings differ along a great circle.

Honest limits & when to escalate

The honest limits here are about category, not quality: great-circle math is near-exact, but it answers 'how far over the surface', not 'how far as driven, flown or walked'. Airline distances follow airways and winds; odometers follow detours; hikers follow switchbacks. Quoting a straight-line number into a fuel budget is the classic misuse, which is why the tools keep the ladder visible — crow-flies, road, time — and label each rung. A second limit is definitional: 'city to city' means mapped centre to mapped centre, and a suburb-to-airport question is a different measurement wearing the same sentence.

Within those bounds the numbers are durable: reproducible from coordinates alone, stable across tools that use the same radius convention, and accurate to a fraction of a percent of geodetic truth. The escalation path is short and rarely needed — ellipsoidal libraries (Karney's algorithms) for survey-grade millimetres, the routing engine for network truth, and the airline's schedule for invoice truth. Knowing which authority owns which number is the entire craft of distance literacy.

• Survey-grade millimetres → ellipsoidal geodesic libraries, not sphere math.
• Fuel and schedule planning → road routing plus your congestion buffer.
• Airline invoicing → carrier distance tables (airways ≠ great circles).
• Legal boundary lengths → licensed survey, never a clicked polygon.

Data & methodology note

Still-air estimate: distance ÷ 850 km/h + 45 min block. Winds and routing not modelled — labelled as estimate. Distances and bearings use haversine great-circle math on the WGS84 mean sphere (R = 6371.0088 km), accurate to ~0.3% of ellipsoidal geodesics; the methodology page documents the full recipe.

Category context: Distance & Bearing — Measure distances, bearings and midpoints between any two places on Earth. This page is one of the distance & bearing tools on MapForge; the related-tools links below and the header's Tools menu connect every sibling instrument.