Time equals distance divided by speed, so 120 miles at 60 mph takes 2 hours. That only works when distance and speed use compatible units — miles with miles per hour, kilometres with km/h, metres with metres per second. The arithmetic is trivial; the failures come from mixed units, decimal hours, average versus instantaneous speed, and stopping time that never appears in the equation. This guide gives you the formula, the conversion table, five worked calculations, and the specific places where the clean answer breaks.

The Core Formula and What Each Symbol Actually Means

The relationship is t = d / s, where t is time, d is distance, and s is speed. Rearranged, that same equation gives d = s × t and s = d / t, which is why the three appear together on every speed-distance-time triangle taught in school. There's nothing more complicated hiding underneath.

Speed is a rate: distance covered per unit of time. That definition matters because it dictates the units of your answer. Divide miles by miles per hour and the miles cancel, leaving hours. Divide kilometres by km/h and you get hours. Divide metres by metres per second and you get seconds. The unit of the answer is always the distance unit divided by the speed unit.

The formula assumes constant speed across the whole journey. Real journeys speed up, slow down, stop at lights, and wait in traffic. When a problem gives you a single speed figure, it means average speed unless stated otherwise. Average speed is total distance divided by total time — not the arithmetic mean of the speeds you travelled at, which is a separate trap covered later.

One more boundary: the formula answers "how long does the moving portion take." It does not include loading, rest breaks, fuel stops, or queueing. If your real question is "when will I arrive," you need to add those separately. Treat the output of d / s as driving time, not door-to-door time.

Convert Units Before You Divide

Mixing units is the single most common cause of a wrong answer. A distance in miles paired with a speed in km/h produces a number that looks plausible and is completely wrong. Convert first, then divide — never divide and convert afterwards, because it's easy to lose track of which unit the result carries.

From To Multiply by
Miles Kilometres 1.60934
Kilometres Miles 0.621371
Miles per hour Kilometres per hour 1.60934
Kilometres per hour Miles per hour 0.621371
Metres per second Kilometres per hour 3.6
Kilometres per hour Metres per second 0.277778
Feet Metres 0.3048
Knots (nautical miles per hour) Kilometres per hour 1.852

The 1.60934 figure comes from the international definition of the mile agreed in 1959, when the United States, United Kingdom, and other Commonwealth nations standardised the statute mile at exactly 1,609.344 metres. The 3.6 factor is exact arithmetic: one hour is 3,600 seconds, so 1 m/s is 3,600 metres per hour, or 3.6 km/h.

Worked conversion: a driver covers 150 miles at 90 km/h. Convert the distance first — 150 × 1.60934 = 241.4 km. Then 241.4 ÷ 90 = 2.68 hours, roughly 2 hours 41 minutes. Skip the distance conversion and you get 150 ÷ 90 = 1.67, which understates the trip by about an hour.

Aviation and marine work use knots, where one knot is one nautical mile per hour and a nautical mile is exactly 1,852 metres by international agreement. A vessel covering 60 nautical miles at 12 knots takes 5 hours, and the unit cancels cleanly without touching statute miles at all.

Turn Decimal Hours Into Minutes Without Losing Accuracy

A calculator returns 2.5 hours or 1.75 hours. People read those as 2 hours 50 minutes and 1 hour 75 minutes, which are both wrong. The decimal part is a fraction of an hour, so 0.5 hours is 30 minutes and 0.75 hours is 45 minutes. Multiply the decimal by 60.

The reliable method: take the whole number as hours, multiply the decimal by 60 for minutes. If the minutes still carry a decimal, multiply that by 60 for seconds. A result of 2.6833 hours becomes 2 hours plus 0.6833 × 60 = 41 minutes. A result of 3.815 hours becomes 3 hours plus 0.815 × 60 = 48.9 minutes, which rounds to 3 hours 49 minutes.

Small rounding shifts the answer more than people expect. At 65 mph, 100 miles gives 1.53846 hours. Call that 1.54 hours and convert: 0.54 × 60 = 32.4 minutes, so 1 hour 32 minutes. Round instead to 1.5 hours and you get 1 hour 30 minutes — a two-minute error created by one rounding step. Keep four decimal places through the conversion, then round the final minutes.

For navigation and aviation, the convention is often decimal hours carried through the whole flight-planning calculation, because fuel burn is quoted in hours. Converting to minutes mid-calculation doubles the work and adds error. Pick one format, finish the arithmetic, then display.

A Worked Calculation Walkthrough for a Road Trip

Here's the process end to end, using a real-shaped problem. You're driving 280 miles, your satnav's route estimate implies an average speed of 70 mph, and you want arrival time.

1: Confirm units match: 280 miles and 70 mph are both imperial, so no conversion is needed. 2: Divide distance by speed: 280 ÷ 70 = 4 hours exactly. 3: Convert any decimal to minutes: the result is a whole number, so 4 hours 0 minutes. 4: Add non-moving time: a 30-minute lunch stop turns 4 hours into 4 hours 30 minutes. 5: Apply the departure clock time: leave at 09:15, arrive at 13:45.

If the satnav quotes 3 hours 52 minutes for the same route instead of 70 mph, that's a more honest figure — routing engines estimate segment-by-segment speeds from historical traffic data rather than applying one blanket average. Google Maps and Apple Maps both derive their time estimates from aggregated historical and live traffic patterns, so the machine's time is usually closer to reality than your own single-speed assumption.

Failure handling matters here. If you can't match the satnav's implied speed, work backwards: 280 miles in 3 hours 52 minutes (3.867 hours) implies an average of 72.4 mph. That tells you the estimate assumes motorway speeds for most of the route. If your own trip involves town driving at either end, add time rather than trusting the single figure.

Average Speed Is Total Distance Over Total Time

The average speed trap deserves its own section because it breaks the division formula in a non-obvious way. Say you drive 60 miles at 60 mph and return 60 miles at 30 mph. The naive answer is an average speed of 45 mph, since (60 + 30) ÷ 2 = 45. But you spent 1 hour outbound and 2 hours returning: 120 miles in 3 hours is 40 mph, not 45.

The reason is that the slower leg takes twice as long, so it should weight twice as heavily in the average. Arithmetic mean of speeds is only correct when the time spent at each speed is equal. When distances are equal and speeds differ, you need the harmonic mean, which for two speeds a and b is 2ab / (a + b). For 60 and 30: 2 × 60 × 30 ÷ 90 = 40. Same answer, cleaner route.

To calculate time across a multi-leg journey, sum the leg times rather than averaging the speeds. Three legs of 100 miles each — one at 50 mph (2 hours), one at 100 mph (1 hour), one at 25 mph (4 hours) — total 7 hours for 300 miles, giving an average speed of 42.9 mph. Averaging the three speeds gives 58.3, which is 15 mph optimistic.

When a problem gives you average speed and asks for time, use total distance ÷ average speed and don't decompose it. The decomposition only helps when you need to know something intermediate, like where a slower driver catches up.

Same Formula in Physics Homework, Racing, and Cycling

The identical division applies across contexts, but the units shift. In physics problems, speed is usually metres per second and distance in metres. A sprinter covering 100 metres at 10 m/s takes exactly 10 seconds. Convert to km/h by multiplying by 3.6, so 10 m/s is 36 km/h — close to Usain Bolt's peak of around 12.4 m/s (44.7 km/h) during his 100 m world record of 9.58 seconds set in Berlin in 2009.

Cycling uses km/h and often asks for time over a known route. A rider averaging 28 km/h over a 120 km sportive takes 4.29 hours, or 4 hours 17 minutes. Road cyclists commonly quote speed in km/h throughout Europe, while US riders often use mph — the conversion factor of 1.60934 applies the same.

Motorsport and rallying use average speed over a stage. A 22 km rally stage completed in 13 minutes 45 seconds works out to 22 ÷ 0.2292 hours = 96 km/h, since 13 minutes 45 seconds is 13.75 minutes, or 0.2292 hours. Stage times matter more than peak speed here, because acceleration and cornering dominate.

In every case, the mechanical step is division; the only thing changing is the unit set and whether you convert before or after. Keep the formula framed as "distance per unit speed" and the context becomes decoration.

Build a Calculator in a Spreadsheet Without Getting Unit Mix-Ups

Spreadsheets are more reliable than phone calculators for repeated calculations because you can build the conversion in and catch unit errors before they propagate. Lay out columns for distance, distance unit, speed, speed unit, and computed time.

The core trick is to convert everything to a common base first. Put a hidden column that converts distance to kilometres and speed to km/h using IF statements keyed on the unit column: if the unit is "miles," multiply by 1.60934; if "metres," divide by 1,000. Then the time column is simply kilometres divided by km/h, giving hours.

For human-readable output, use TEXT and INT functions to display "4:17" or "4h 17m" rather than raw decimals. INT(time) gives whole hours, and (time - INT(time)) × 60 gives minutes, rounded to the nearest whole number with ROUND.

The failure mode to guard against is unit silence — a cell with "120" and no unit label. Someone enters 120 miles where km was expected and the time comes back 60% too short. Force the unit column to be mandatory (data validation with a dropdown of "miles," "kilometres," "metres," "feet") and you've eliminated most errors before they happen. This is the same discipline routing engines apply internally.

When the Simple Formula Stops Working

Real-world timekeeping diverges from d / s in four situations, and none of them require a more complicated formula — they require separate corrections.

Traffic and variable conditions: urban journeys average 12–20 mph on congested roads in major UK and US cities, which is why the same 10-mile trip takes 30 minutes at night and 55 minutes at 8 a.m. Apply the commuting multiplier rather than the speed-limit figure. According to the UK Department for Transport's annual traffic statistics, average speeds on local 'A' roads in England during weekday morning peaks have hovered in the high teens of mph for years.

Rest breaks and loading: a lorry governed to 56 mph needs mandatory breaks under EU and UK drivers' hours rules — a 45-minute break after 4.5 hours of driving, with additional daily limits. The moving time calculation says 280 miles takes 5 hours; scheduling says it takes 5 hours 45 minutes minimum, more once you add a second break.

Acceleration and deceleration: on very short trips, reaching top speed dominates. A car going 0–60 mph in 8 seconds covers maybe a quarter-mile before hitting cruising speed. For trips under a mile, the formula is nearly useless; use a stopwatch estimate.

Non-constant average speed over long journeys: motorway cruising at 70 mph for 100 miles works cleanly, but a trip through a city using 30 mph limits for 20 miles and 70 mph for 80 miles averages 54.5 mph (100 ÷ 1.835 hours), not 55 by naive averaging — a small gap, but it grows with distance.

Common Mistakes and the Units That Trip People

Five errors account for most wrong answers, and each has a specific fix.

Converting mph to m/s incorrectly: 60 mph is not 60 × 0.2778 m/s. It's 60 × 0.44704 = 26.82 m/s, because the exact factor is miles to metres (1,609.344) divided by seconds in an hour (3,600). Use 0.44704 as your multiplier for mph to m/s and 2.23694 for the reverse.

Confusing hours-and-minutes with decimal hours: 1.5 hours is 90 minutes, not 1 hour 50 minutes. Write out the unit in full when you're checking a result.

Using the wrong unit for the speed: a satnav might quote arrival time in hours and minutes, a physics problem in seconds, and a road sign in minutes and miles. Read the unit as carefully as the number.

Forgetting that speed must be average: a problem giving a speed of 30 mph in a residential area over 5 miles gives 10 minutes, but the actual average including starts, stops, and parking is closer to 15–18 minutes.

Dividing when you should multiply: d = s × t and t = d / s are easy to swap. Sanity-check with a simple case — 60 mph for 1 hour is 60 miles, so time = distance ÷ speed, not the reverse.

FAQ

How long does it take to travel 100 miles at 70 mph?

About 1 hour 26 minutes. The exact result is 100 ÷ 70 = 1.42857 hours, which is 1 hour and 0.42857 × 60 = 25.7 minutes, rounded to 26. Note that most cars don't sustain a true 70 mph average — motorway roadworks and junctions typically knock the real average to the low 60s, stretching the trip to roughly 1 hour 35 minutes.

What's the difference between average speed and instantaneous speed?

Average speed is total distance divided by total time, while instantaneous speed is what the speedometer shows at one moment. The division formula always uses average speed unless a problem explicitly says speed is constant. Because instantaneous speed varies continuously, only the average feeds into the time calculation. A car showing 70 mph at one moment may average 52 mph over the full journey.

Can I use this formula for a flight?

Only as a rough estimate, because aircraft don't fly at a single constant groundspeed. A 3,000 km flight at a cruise speed of 850 km/h gives 3.53 hours airborne, but headwinds or tailwinds can shift that by 30–60 minutes on transatlantic routes. Jet stream winds over the North Atlantic routinely exceed 200 km/h at cruise altitude, which is why westbound flights from London to New York typically take 45–60 minutes longer than the eastbound return.

Why does my satnav say 3 hours when the formula gives 2.5?

Routing engines assume historical traffic, road types, and junction delays rather than a single cruising speed. A route implying 60 mph from d / s often actually includes stretches of 30 mph through towns, which drags the true average well below the cruising speed. The satnav time is closer to reality in almost every case. Trust it over your own division unless you know the road well.

How do I add a rest stop to the calculated time?

Calculate the moving time with d / s, then add the stop duration separately in minutes. A 200-mile trip at 60 mph takes 3 hours 20 minutes moving; add a 30-minute stop and a 15-minute fuel stop for a 4 hour 5 minute elapsed time. For lorry drivers under EU rules, a mandatory 45-minute break applies after 4.5 hours of driving, so a trip of 5 hours moving time requires at least 5 hours 45 minutes.

Does the formula work for walking and running?

Yes, with the pace convention running in reverse. Walking at 5 km/h covers 7 km in 1.4 hours, or 1 hour 24 minutes. Runners often quote pace (minutes per kilometre) instead of speed, and the relationship is time = distance × pace. A 5:30 min/km pace over 10 km is 55 minutes. Convert pace to speed by dividing 60 by the pace figure when you need km/h.

What if I only know miles per gallon and fuel used?

That gives you distance and fuel, not speed, so you need a separate speed figure. If a car covers 300 miles using 10 gallons at 30 mpg, the distance is confirmed but the time still requires an average speed — say 60 mph, giving 5 hours. Fuel consumption and speed are independent inputs. Some trip computers show average speed directly, which is exactly the figure d / s needs.