Braking distance

You see a red light or a pedestrian stepping onto the crossing. From a city speed of about 50 km/h you have to stop. Speed does not drop to zero at once: first you react, then the brakes do their job. That is the braking story on the road.

In the basic model, braking is uniformly decelerated motion: speed falls at constant deceleration a > 0 until rest or until a target v_k. It is the mirror of accelerated motion, with a clear “I am slowing down” sign. Same formulas, opposite change in v.

When you brake to zero, v_k = 0. From v_k = v₀ − a·t you get the time:

t = v₀/a

From v_k² = v₀² − 2·a·s you get the bare braking distance:

s = v₀²/(2a)

First numeric intuition from the problem below: v₀ = 13.9 m/s (about 50 km/h), a = 6 m/s². Then s = 13.9² / 12 ≈ 16.1 m and t ≈ 2.32 s. That is only the stretch from pressing the pedal to rest. Work it out by hand, then check in the decelerated-motion calculator.

Why does s grow with the square of v₀? Kinetic energy grows like v², and brake work at constant force grows like s. At twice the speed you need about four times the braking distance at the same a. The gut feeling “a bit faster, so only a bit farther” fails right here.

On a real road the driver reaction time t_r appears. Before the foot hits the pedal, the car still covers s_r = v·t_r at (approximately) constant v. Total stopping distance is:

s = v·t_r + v²/(2a)

Second intuition: with the same numbers and t_r = 1 s the reaction stretch is 13.9 m, the braking stretch ≈ 16.1 m, and the sum ≈ 30 m. Reaction almost matches the brakes alone. That is a different question from “how many meters do the brakes alone take”.

That is why there are two tools. Uniformly decelerated motion computes s and t without t_r. Stopping distance adds reaction time. Do not force t_r into the first tool if the problem is silent, and vice versa. Text with “noticed an obstacle” almost always wants the sum.

Units matter. Always convert km/h to m/s before s = v²/(2a). 50 km/h / 3.6 ≈ 13.9 m/s. Reaction time is often 0.8-1.5 s in illustrative examples: take the value from the problem. Give a in m/s² and distance in meters. If you feed “50” straight into v²/(2a), the distance looks as if it came from another planet.

A dramatic mistake looks like this. You see “noticed an obstacle at 50 km/h”, compute bare s = v²/(2a) ≈ 16 m, and say “enough room”. You forgot the reaction second. In that time the car still covers almost 14 m. At a junction those missing meters decide whether you stop before the line or on it. Another classic error: using s = v·t with initial speed for the whole stop, as if the car kept full city speed until rest.

Bridge to momentum: p = mv must be removed by a force impulse. At constant braking force F and time t, impulse F·t changes momentum. The momentum calculator shows how much momentum you carry into the manoeuvre. Larger m or v means more to remove in the same time, or the same F must act longer.

Bridge to work: W = F·s for a force parallel to the path. At constant a you have F = m·a (here a is deceleration), so W = m·a·s ties to the loss E_k = ½mv₀² when v_k = 0. Same numbers, different language. Use work force-distance. Energy says how much you must “eat”; kinematics says on what distance and in what time.

Sanity-check the magnitude. At 50 km/h and a about 5 m/s²-6 m/s², bare braking is order 15 m-20 m. A 1 s reaction adds about 14 m. The sum is near 30 m. If you get 3 m or 300 m, hunt units or the wrong tool.

Model assumptions: a = const, straight path, tires grip. Rain, ABS and tire choice sit outside the basic formula, though you may still use an effective a from a measurement and treat it as constant. Raising v₀ by 20% raises braking s by about 44% at the same a, because the square acts. A small speed change, a large distance change.

The model is not enough when a clearly changes during the manoeuvre, when there is a skid or a wet surface without a given effective a, or when air drag depends strongly on speed and cannot be hidden inside one constant a. You may still use a constant a from data as an approximation, but that is a deliberate shortcut, not a full tire-and-ABS story.

In the series this is part 3. Next comes gravity in the vertical throw, but the intuition v²/(2a) returns as H_max = v₀²/(2g). Braking teaches the formula on the ground; the vertical throw teaches it in the air. Same skeleton: removing speed under constant acceleration.

Before you compute, name the question: is it bare braking distance, or stopping distance with reaction? Those are two results and two calculators. Then check units and order of magnitude, and only then trust the number on the screen.

It also helps to keep two sign languages apart. You can talk about positive deceleration a and write v_k = v₀ − a·t, or about negative acceleration and insert a < 0 into the accelerated-motion formulas. Both are fine if you do not mix them in one calculation. At first, it is clearer to keep positive a as “how hard you are slowing” and separately remember that v is falling.

If the problem gives the distance to an obstacle and asks whether you can stop in time, compare s_stop with that distance. When s_stop is larger, at the same a you do not stop before the line. Then you either need a larger a (harder braking, better grip) or a smaller v at the start of the manoeuvre. “I will press harder” without a number for a does not close the calculation.