Stopping Sight Distance
A driver travels a long way before even touching the brake.
Before this Lesson
- Constant-Acceleration Motion · Dynamics
- Stations and Grades · Surveying
At 60 mph, a car covers 88 ft every second. Highway design allows the driver 2.5 s to notice a stalled truck ahead, decide it matters, and get a foot onto the pedal. In that time the car goes 220 ft, most of a football field, at full speed with the brakes untouched. Only then does it start to slow down.
So a road has to let the driver see a good deal farther than the brakes alone would need. How much farther depends on the speed and the grade, and by the end of this Lesson you'll be able to compute it.
Stopping happens in two phases
Run the scene in your head. The truck comes into view, and for a while nothing happens to the car at all. The driver sees it, works out what it means, and moves a foot, and the whole time the car rolls on at full speed. That's the perception-reaction phase, and its distance is plain speed times time, .
Then the brakes go on, and the speed falls steadily to zero. That's the braking phase, and you've met its distance before: , with the size of the deceleration. Drawn as speed against time, the first phase is a rectangle and the second is a triangle, and the area under the line is the distance.
From Constant-Acceleration Motion: put into , and a car braking steadily stops in , with the speed in ft/s and 1 mph = 1.467 ft/s. This Lesson's braking distance is that .
Add the two areas and you have the stopping sight distance, or SSD: how far ahead a driver has to be able to see an object to stop short of it. In geometric design, design speed is the governing input, and this is the first number it sets. Later Lessons on curves take it as the sight distance they have to provide.
Design work needs a number for the driver and a number for the brakes. AASHTO, whose guide sets U.S. highway design practice, uses a perception-reaction time of 2.5 s and a deceleration of 11.2 . Both lean cautious. About nine drivers in ten react faster than 2.5 s, and about nine in ten can brake harder than 11.2 on a wet road and still keep the car in its lane. The Handbook prints neither number, so they're yours to carry, though most problems state them anyway.
Those are the values in the figure. At 88 ft/s, the car goes reacting and braking, 566 ft in all. Nearly 40% of the distance is gone before the brakes do anything.
A hill works on the brakes, not on the driver
Stop on a hill and you can feel which way gravity is pulling. Going up, it helps the brakes. Going down, it fights them. Only the part of gravity along the road matters, and on the gentle slopes of real roads that part is simply the grade: on a 5% grade, about 5% of points along the road. So a grade , written as a decimal, is worth a deceleration of , added to the brakes' on the way up and taken off on the way down.
Put that total into the braking distance and pull out :
Now look at what sits in the parentheses. is the brakes' pull as a fraction of gravity. is the hill's pull as a fraction of gravity. They're the same kind of thing, so they add, and a hill acts exactly like a bit more or a bit less braking. The reaction distance has no slope in it at all, so the grade only ever touches this one term.
One more step makes it ready for a speedometer. Write the speed as , with in mph and 1 mph = 1.467 ft/s rounded. With , the leading constant is , which rounds to . So the 30 isn't a fact about roads. It's gravity and a unit conversion packed into one number. That gives the equation printed in the Handbook's Stopping Sight Distance section:
The first term is the reaction distance and the second is the braking distance, names the Handbook leaves off. It defines as the design speed in mph, as the driver reaction time in seconds, as the deceleration in , and as the percent grade divided by 100, with an uphill grade positive. Two habits keep this equation honest:
- stays in mph. The 1.47 and the 30 already hold the conversion, so a speed in ft/s gets converted twice. It's the plain that wants ft/s.
- is a signed decimal, set by the direction of travel. Read the as one rule: write and let carry its sign, positive when this driver is climbing. A 3% downgrade is . A plan's grade in Stations and Grades is signed by the stationing instead, so traffic running against the stations flips it.
On level ground, our 60 mph car gets : the same 566 ft, so the rounded constants cost you nothing.
Braking distance alone
Some questions stop at the second term: how far does the car travel once the brakes are on? Drop the , and that's the answer.
They may also describe the brakes by a friction coefficient rather than a rate. Sliding tires push back on the car with a friction force of times its weight, which is from the Handbook's Friction section in Dynamics. Divide that force by the car's mass, , and you get , so . The same slot in the denominator takes either one:
The Handbook prints only the first form and gives no friction values for pavement, so the problem supplies . A friction coefficient goes in as it is. A rate in gets divided by 32.2 first.
Reading speed from skid marks
Now run that term backward. An investigator measures a set of skid marks, tests the pavement's friction, and wants the speed. If the car skidded to a stop, solve the braking distance for :
Often the car didn't stop. It hit something, and the crash gives an estimate of the impact speed . Now the skid only carried the car from its starting speed down to . Start from in the Handbook's Constant Acceleration section, make the same moves as before, and you get:
Notice what adds up here: squares, not speeds. A skid of a given length on a given road removes a fixed amount of , whatever speed the car had, for the same reason friction over a fixed distance burns a fixed amount of energy. So you put back what the skid took, on top of what the car still had when it hit.
The marks begin where the wheels locked, so is the speed when braking began, not the speed at impact. The Handbook has no skid-mark equation. This is all the braking term, rearranged.
The fastest safe speed for the road you can see
Now let the road set the limit. A crest or a parked truck means the driver can see only so far. How fast can they go and still stop in that distance? Set SSD equal to the distance available and solve for .
appears twice, to the first power in the reaction term and squared in the braking term, so simple algebra won't pull it out. Move everything to one side and you have a quadratic:
Use your calculator's polynomial solver or the quadratic formula. One root is positive, and that's the speed. The other is negative and belongs to no car. Any rounding goes down, because a higher speed needs more road than the driver can see.
What each change does to the distance
Many questions skip the arithmetic and ask what a change does. For those, keep the two terms apart, because they care about different things.
- The reaction distance, , is proportional to and to . Grade and deceleration aren't in it.
- The braking distance is proportional to . Grade and deceleration act on it through the denominator, and isn't in it.
The straight line and the parabola trade places at about 38 mph. Below that, the driver's reaction uses up more road than the brakes do. Above it, braking takes over, and its lead keeps growing.
One road, two directions
On a two-way road, one steady slope is a climb for one direction and a descent for the other. Both directions have the same design speed and the same driver, so the reaction distances match and cancel.
So "how much longer for downgrade traffic?" needs just two braking distances and a subtraction. Here it's , and the reaction time never enters.