You promised to arrive by 2 p.m. for a client lunch. Maps says two hours ten minutes, but you also need fuel, a restroom, and you will not average 70 mph through construction. Mental math using “60 mph means a mile a minute” breaks when speeds change and units mix kilometers with miles on rental dashboards. A speed–time–distance check is the three-line habit that keeps commitments plausible before you send the calendar invite.
Pick the unknown before you plug numbers
Given distance and average speed, solve time. Given time and speed, solve distance. Given distance and time, solve average speed. Write which variable you need on paper—prevents solving the wrong thing when tired. Average speed is not peak cruise control; it includes slowdowns you expect.
Example: 180 miles at an average 54 mph (not 60) is 3 hours 20 minutes of driving, before stops. Saying “three hours” without showing the average invites lateness.
Average speed is a story, not a setting
Highway cruise at 68 mph still yields 58–62 mph averages when you include town exits and fuel stops on a 200-mile leg. Build averages from experience on similar roads, not best-case fantasy. Weather and holiday traffic deserve downward adjustment without guilt—planning is about arrival, not bragging rights.
Speed and Time Calculator keeps units consistent when you switch between hours and minutes or mix mile-based distance with km/h on a rental cluster. Speed Converter helps when signage and dashboard disagree during international drives.
Stops belong in a second layer
Compute driving time first, then add stop budget: fifteen minutes per fuel stop, ten for quick restroom, thirty if lunch is on route. Sum driving plus stops for ETA. Calendar alerts should use the sum, not driving-only math.
Meeting buffers: arrive ten minutes early to client sites with parking friction; arrive five for familiar offices. The buffer is not “extra speed”—it is civilized uncertainty.
Distance sources and rounding
Map apps differ slightly; pick one source for the plan and stick to it. Rounding distance down and speed up is how optimism creates apologies. Round distance up slightly for planning when exits add miles.
Connecting to fuel budgeting, pair time checks with Gas Cost Calculator when cost and punctuality share the same trip—same miles, two conversations.
Multi-leg trips and different averages per leg
Split the journey: urban exit 12 miles at 28 mph average, highway 140 miles at 62 mph, final 8 miles at 35 mph. Compute each leg’s time, sum, then add stops. Blending everything into one average speed hides where lateness appears—usually the first urban segment when departure was optimistic.
Trains, shuttles, and last-mile timing
Airport plans often combine driving, parking shuttle, and security. Speed–time math applies per segment with its own distance and pace. Security wait is not a speed problem—give it a fixed block (20–40 minutes) based on airport and day of week, then add to driving math separately.
Communicating ETA honestly
Send ranges to humans (“arrive 1:45–2:05 p.m.”) and point estimates to logistics software if required. Ranges absorb stop variance without eroding trust. If you must pick one time, use driving-plus-stops plus buffer, never driving alone.
Weather and construction as explicit percent penalties
Instead of vague worry, add five to fifteen percent time on legs known for seasonal congestion. Snow regions in March, beach towns in July—name the penalty on the worksheet so teammates see it was planned, not an excuse invented after lateness.
Night driving and visibility
Average speed often drops after dark even on highways—fatigue, wildlife, and cautious pacing. A 62 mph daytime average might be 54 mph at night on the same road. Night departures for “early arrival” sometimes lose the benefit you imagined.
Save your worksheet in the calendar invite description—future you inherits assumptions instead of re-guessing averages from memory.
Carpool pickups add uncertain minutes per extra stop—model each stop as five to eight minutes unless you know the route history.
Trains published as “on time” still need platform walking—treat station arrival and door-to-door arrival as different commitments when promising a client.
Write the planned average speed on the worksheet circle—future trips improve when you compare planned versus actual after GPS logs.
Frequently Asked Questions
Is 60 mph always one mile per minute?
At steady 60, yes. Real trips rarely hold 60 the whole way—use averages.
How do I convert km/h to mph mentally?
Multiply km/h by 0.62 roughly, or use a converter for commitments that matter.
Should I use map ETA instead of calculating?
Maps include live traffic; manual checks teach assumptions. Compare both when stakes are high.
What average speed for city-only legs?
25–35 mph is common in dense cities; lower with snow or events.
Can I solve for departure time instead?
Yes—work backward from arrival minus driving minus stops. Same triangle, different unknown.
Why did we arrive early but feel late?
Stops were undercounted or parking search ate buffer. Track stop time next trip.