The car's average speed was 54 miles per hour. It covered 162 miles in 3 hours, and 162 divided by 3 equals 54. That is the whole computation: distance divided by time. Two conditions matter for the number to be right, though. The 3 hours is elapsed clock time from 7:30 to 10:30, and 162 miles is total distance travelled, not straight-line distance between the two points. Read those two definitions loosely and the same trip can produce a very different figure.
Why 7:30 to 10:30 Is Exactly 3 Hours, Not 2.5 or 3.5
The single most common error on this problem is a time subtraction slip. From 7:30 AM to 10:30 AM, the minutes match at both ends, so you only need to subtract the hours: 10 minus 7 equals 3. No borrowing across noon is needed, and no minutes carry over.
If the times had been 7:45 AM to 10:30 AM, the arithmetic changes shape. From 7:45 to 10:45 is 3 hours, but you finish 15 minutes early, so elapsed time is 2 hours 45 minutes, or 2.75 decimal hours. Average speed would then be 162 ÷ 2.75, which is about 58.9 mph. A quarter-hour shift in departure moves the answer by nearly 5 mph.
Keep the units straight when you convert. Thirty minutes is 0.5 hours, fifteen minutes is 0.25 hours, and forty-five minutes is 0.75 hours. Mixing a decimal hour with a minute count is where most wrong answers come from, and it produces nonsense like "162 ÷ 3.25 = 54" when the real divisor was 3.
Time zones deserve one line of caution. If point A and point B sit in different zones, the clock reading at arrival has to be adjusted before subtracting. A 7:30 AM departure from Chicago arriving at 10:30 AM in New York is 2 hours of elapsed time, not 3, because Eastern time runs an hour ahead. The problem as written assumes one zone.
The Formula Behind 54 mph and What "Average" Actually Means
Average speed equals total distance divided by total time. That is it. The formula is not a simplified version of something harder; it is the definition. Write it as speed = distance ÷ time, plug in 162 miles and 3 hours, and the quotient is 54 miles per hour.
The word "average" carries real weight here. It does not mean the car held 54 mph on the cruise control. It means the total distance and total time produce that ratio. A car that spent 20 minutes crawling at 15 mph through a town and 2 hours 40 minutes at highway pace can still average 54 mph for the trip, because the slow stretch is folded into the whole.
This is where average speed separates from instantaneous speed. Your dashboard shows instantaneous speed at any moment; the trip average is a summary of the entire journey. A speed camera captures one instant. The average covers every instant between the two points, weighted by how long each speed lasted.
The formula also explains why the answer's unit is miles per hour rather than just miles. Miles divided by hours gives miles per hour by construction. If you ever get an answer in the wrong unit, the division was set up backwards.
The Full Worked Calculation, Step by Step With a Unit Check
Here is the complete chain, spelled out so you can check each link. Run these steps in order and the answer falls out with no guesswork.
1: Record the departure time: 7:30 AM. 2: Record the arrival time: 10:30 AM. 3: Subtract to find elapsed time: 10:30 − 7:30 = 3 hours. 4: Confirm the minutes cancelled cleanly (30 − 30 = 0), so no decimal conversion is needed. 5: Write the distance: 162 miles. 6: Divide distance by time: 162 ÷ 3. 7: State the result with units: 54 miles per hour.
The unit check is the safety net. Carry the units through the division: 162 miles ÷ 3 hours = 54 miles/hour. If you had divided hours by miles, you would get 0.0185 hours per mile, which is a pace, not a speed. Racers and runners sometimes quote pace deliberately, but the question asks for speed, so miles per hour is the target.
Failure case: if a solver converts 3 hours to 180 minutes and then divides 162 by 180, the answer comes out as 0.9 miles per minute. That number is correct in its own units but does not answer the question. Multiply by 60 to return to mph and you get 54 again. The arithmetic is consistent; the unit label is what shifts.
Reversing the Problem: Distance, Time, and Speed Are a Three-Way Trade
The same relationship solves three different questions, and textbook writers exploit that. Know one form and you know all three.
| What you know | What you want | Formula | Example with this trip's numbers |
|---|---|---|---|
| Distance and time | Speed | distance ÷ time | 162 ÷ 3 = 54 mph |
| Speed and time | Distance | speed × time | 54 × 3 = 162 miles |
| Distance and speed | Time | distance ÷ speed | 162 ÷ 54 = 3 hours |
This table is the reason the original question is a one-step problem. The other two versions are equally short. "A car averages 54 mph for 3 hours; how far does it go?" gives 162 miles. "A car must cover 162 miles at 54 mph; how long does it take?" gives 3 hours.
The trade-off shows up in planning. Drivers who want to shave 20 minutes off a 162-mile run need to raise average speed by 54 − (162 ÷ 2.667) ≈ 6.75 mph, which is roughly 60.75 mph. That number is arithmetic from the stated figures, not a road-test claim. The point is that time savings scale non-linearly with speed: the faster you already go, the more speed you need for the same minutes saved.
A reverse calculation also exposes a trap. If someone says "I averaged 60 mph, so the 162-mile trip took 2.7 hours," the "2.7 hours" is 2 hours 42 minutes, not 2 hours 7 minutes. Decimal hours get misread as minutes constantly. Sixty percent of an hour is 36 minutes, and 0.7 of an hour is 42 minutes.
When the 54 mph Answer Is Wrong: Stops, Detours, and Two-Way Trips
The clean answer assumes the 162 miles is the distance actually driven. Change that assumption and the number moves. Three realistic scenarios break it.
First, detours. If the driver took a 12-mile detour to avoid a closed bridge, the odometer shows 174 miles, and average speed becomes 174 ÷ 3 = 58 mph. The clock says the same 3 hours; the distance grew.
Second, stops included in the clock. If the 3-hour window includes a 20-minute fuel stop, the car was moving for only 2 hours 40 minutes, so the moving average is 162 ÷ 2.667 ≈ 60.75 mph, while the trip average over the full window stays 54 mph. Both numbers are defensible; they answer different questions.
Third, round trips. A there-and-back journey of 162 miles each way covers 324 miles, and if it takes 6 hours the average is still 54 mph. But if the return leg is slower because of evening traffic, the blended average drops below the outbound number. A 162-mile outbound at 60 mph (2.7 hours) plus a return at 48 mph (3.375 hours) covers 324 miles in 6.075 hours, an average of about 53.3 mph.
Edge scenario worth flagging: a car that travels 162 miles and returns to point A has a net displacement of zero. Average velocity, which is displacement over time, would be 0 mph, while average speed stays 54 mph for the outbound leg. Physics classes grade that distinction harshly, and it is the difference between a scalar and a vector.
mph vs km/h: What 54 mph Looks Like in Metric and Why the Conversion Matters
If the reader works in metric, 54 miles per hour converts to about 86.9 kilometres per hour. The exact factor is 1.609344 kilometres per mile, so 54 × 1.609344 = 86.9 km/h to one decimal place. The 162-mile distance is 260.7 kilometres by the same factor.
That conversion is not academic on an international road trip. A US driver crossing into Canada or Mexico sees speed limits in km/h, and a 100 km/h limit equals roughly 62 mph. Driving at an indicated 54 mph in an 80 km/h zone (49.7 mph) would be over the limit, which is the kind of detail a plain unit conversion catches and a guess does not.
The metric distance changes too. If someone quotes the same trip as 260.7 km in 3 hours, average speed is 86.9 km/h. Divide 260.7 by 3 and you get 86.9; the ratio holds because both units scaled by the same factor. That consistency is a useful sanity check: convert distance and speed by the same multiplier and the time stays fixed.
Odometer readings in Canada and the US are typically in kilometres and miles respectively, but imported vehicles sometimes show the wrong unit on the gauge. A car with a kilometre odometer reading "162" has actually gone about 100.7 miles, and the mph answer would fall to roughly 33.6. Check the unit printed on the dial before trusting any number.
Reading the Clock Correctly: 12-Hour, 24-Hour, and Midnight Crossings
The problem uses a 12-hour clock with "AM" labels, which most people read without effort. The 24-hour equivalent is 07:30 to 10:30, and the subtraction is identical. Problems get harder when the trip crosses noon or midnight, because the clock face resets.
Crossing noon: 11:30 AM to 2:30 PM looks like "1 hour and 1 hour" if you subtract the digits carelessly, but the elapsed time is 3 hours (11:30 to 12:30, 12:30 to 1:30, 1:30 to 2:30). The fix is to add 12 to any PM hour when working in 24-hour time: 11:30 to 14:30 is 3 hours.
Crossing midnight: a 10:00 PM departure arriving at 1:00 AM covers 3 hours, not "9 minus 10." Convert the arrival to 25:00 or add 24 to the AM hour: 22:00 to 25:00 is 3 hours. A driver who leaves at 11:45 PM and arrives at 2:15 AM has travelled 2.5 hours, and the same 162 miles would give 64.8 mph.
The average-speed formula is indifferent to the clock format; only the elapsed time matters. But the labels on the problem are where errors breed. Always strip the clock to a single timeline before dividing.
Sensory note for anyone who has actually driven a 3-hour, 162-mile leg: the odometer ticks over, the fuel gauge drops by roughly a third of a tank on a typical mid-size car, and the clock on the dash reads a clean 3 hours later. Those small confirmations are how drivers sanity-check a trip average without doing the math twice.
A Fast Mental Estimate: The 50 mph Baseline Trick
Before reaching for a calculator, estimate. At 50 mph, a 3-hour drive covers 150 miles. Our trip is 162, which is 12 miles more, so the average must be a bit above 50. Twelve miles in 3 hours is 4 mph, and 50 + 4 = 54. The answer lands exactly, and the estimate was done in your head.
This benchmark method works for any problem of this shape. Memorize three anchors: 30 mph covers 30 miles in an hour, 50 mph covers 50, and 60 mph covers 60. Then scale. A 162-mile trip at a rough 60 mph would take 2.7 hours, which is 18 minutes short of 3 hours, so the true average sits below 60. How far below? About 6 mph, per the earlier trade-off math.
Distances of 162 miles are close to three round numbers: 150, 160, and 162. A 150-mile trip in 3 hours is exactly 50 mph; a 180-mile trip in 3 hours is exactly 60 mph. The actual answer sits between those anchors, closer to 50, which matches 54.
The mental trick has one failure mode: rounding the time instead of the distance. If you round 3 hours to 3 and 162 to 160, you get 53.3 mph, close enough for a sanity check but not for a graded answer. Use the trick to confirm the exact computation, not to replace it.
Common Mistakes That Produce Answers Other Than 54
Several wrong answers recur on this exact problem, and each has a recognizable fingerprint. Spotting the fingerprint tells you where the setup broke.
162 ÷ 3.5 = 46.3 mph. This comes from misreading 7:30 to 10:30 as 3.5 hours. The minutes matched; there was no half hour to add. 162 ÷ 2 = 81 mph. This comes from subtracting only the hour digits, treating 7:30 and 10:30 as "7 to 10" minus the half hour, or from crossing the 8:30 and 9:30 marks and counting them as the total. 54 × 3 = 162, then reported as 162 mph. The arithmetic is right; the unit is wrong. Speed and distance got swapped. (162 ÷ 3) + a guessed traffic penalty. Inventing a delay that the problem never stated changes the question. Answer the question asked. 162 ÷ 180 = 0.9, reported as 0.9 mph. This is miles per minute, not miles per hour. Multiply by 60.
The unifying theme is a mismatch between the units in the inputs and the units in the answer. A second theme is adding information the problem did not supply, like traffic or a rest stop. A third is arithmetic drift, where 10:30 − 7:30 gets computed as 2.5 because the solver anchors on the ":30" and subtracts it twice.
Anyone grading this problem should reward a clear setup as much as the final 54. A solver who writes "162 miles ÷ 3 hours = 54 mph" has shown the method. A bare "54" with no work is harder to trust.
FAQ
Is 54 mph the same as 54 miles per hour, or is there a difference?
They are the same unit written two ways. Any answer to this problem that reads "54 miles per hour" is correct whether or not the abbreviation appears. The abbreviation saves space; it changes no value.
What if the car left at 7:30 AM and arrived at 10:30 PM instead?
The elapsed time becomes 15 hours, not 3, and the average speed falls to 162 ÷ 15 = 10.8 mph. That is a walking pace, which should prompt a check of the problem statement. A 12-hour error like this produces an answer that looks obviously slow.
Does 54 mph mean the car never went faster or slower?
No. Average speed is a summary ratio, not a record of every moment. A car could legally hit 70 mph on a highway stretch and idle at a red light for a minute and still average 54 mph for the whole trip. The instantaneous speed at any second is a different number.
How long would the same 162 miles take at 60 mph?
It would take 162 ÷ 60 = 2.7 hours, which is 2 hours 42 minutes. That is 18 minutes faster than the 3-hour trip at 54 mph. The 6 mph gain buys 18 minutes over this distance, an arithmetic result you can verify by converting both times to minutes: 180 − 162 = 18.
What is 54 mph in kilometres per hour?
It is about 86.9 km/h, using the standard factor of 1.609344 km per mile. The equivalent distance for 162 miles is 260.7 km. Drivers crossing into metric countries will see those figures on signs and speedometers.
Can average speed ever be higher than every speed the car actually drove?
No, and that is a useful misconception buster. The average of a set of numbers cannot exceed the largest number in the set. If the car never exceeded 54 mph at any moment, the trip average cannot be above 54 either.
What if the car stopped for 30 minutes along the way?
The clock still shows 3 hours, so the trip average stays 162 ÷ 3 = 54 mph. The 30-minute stop reduces the moving average: the car was in motion for 2.5 hours, so 162 ÷ 2.5 = 64.8 mph while rolling. Both figures are correct, but only the trip average answers the question as asked.
Why do some calculators return 0.9 for this problem?
Those calculators divided 162 by 180 minutes instead of 3 hours, producing miles per minute. The 0.9 figure is a valid pace, not a speed in mph. Multiply it by 60 to recover 54 mph and confirm the original arithmetic was sound.