Stopping Sight Distance (SSD) Calculator
Find the clear road a driver needs to see a hazard, react, and stop. Enter a speed and conditions, and get the full AASHTO stopping sight distance, split into reaction and braking distance, adjusted for grade and pavement friction, and checked against the official Green Book design minimum.
Visibility and Braking Tool
Set the speed, method, and road conditions. One click gives you the reaction distance, braking distance, and total sight distance.
Enter a speed and conditions, then press Calculate. Your reaction distance, braking distance, and total stopping sight distance will appear here.
Sight distance across the speed range
What this clear-road measure means for drivers
Picture yourself driving a two-lane highway outside Boise at 60 miles an hour. A deer steps into the road ahead. Between the moment you first see it and the moment your car actually stops, your vehicle covers a surprising amount of pavement, well over the length of a football field and a half. That total distance, from first sight to full stop, is what traffic engineers call stopping sight distance, or SSD. It is one of the most fundamental numbers in road design, because it decides how far ahead a driver must be able to see for a road to be safe at a given speed. It is, in a very real sense, the distance that stands between a close call and a collision.
Every crest of a hill, every curve, every tree line and sound wall along an American highway was checked against this number. If a road cannot give drivers enough clear sightline to stop for a hazard, it is not safe at its posted speed, full stop. That is why SSD sits at the heart of the AASHTO Green Book, the design bible that every state department of transportation follows. This calculator runs the exact Green Book math so an engineer, a plan reviewer, a civil PE exam candidate, or a curious driver can see precisely how far that stopping distance really is and what stretches it.
The two pieces of the distance
Break SSD into its parts and it stops being mysterious. The first piece is the perception-reaction distance. From the instant a hazard appears to the instant the brakes engage, roughly two and a half seconds for most drivers, the car keeps moving at full speed. At 60 mph that alone is about 220 feet, covered before the brakes even bite. The second piece is the braking distance, the ground the car covers while actually slowing to a stop. This is where physics turns unforgiving, because braking distance rises with the square of speed. Double your speed and the braking distance roughly quadruples. That single fact is why a small bump in speed produces a big jump in required sightline, and why speed matters so much for safety.
Understanding both pieces separately is useful, because they respond to different things. Reaction distance depends on speed and driver alertness. Braking distance depends on speed, road grade, and how much grip the tires have on the pavement. A tired driver stretches the first piece. A rain-slicked downhill stretches the second. This tool shows you both numbers so you can see which part of the equation is driving your result. If you are also laying out a work zone on the same road, the cone taper length calculator uses this same stopping distance to size the buffer space between the taper and the crew.
Why engineers, examiners, and drivers all reach for it
SSD is not an academic curiosity. Highway engineers use it to set the minimum length of crest vertical curves so drivers can see over a hill in time. Intersection designers use it to place stop bars and check sightlines. Civil PE and FE exam candidates practice this formula because it appears on the test, tied directly to Green Book equations. Traffic safety analysts use it in crash reconstruction and road safety audits. And any driver who has ever wondered why the speed limit drops before a blind curve is looking at stopping sight distance in action. This calculator serves all of them with one honest, transparent number.
A number with real consequences
It is worth pausing on why this matters so much. When a road fails to provide adequate stopping sight distance, the result is not an abstract code violation. It is a crest where a driver crests the hill and finds stopped traffic with no room to react, or a curve where a fallen branch appears too late to avoid. Sight distance deficiencies show up in crash data as a recognizable pattern, often rear-end and run-off-road collisions clustered at specific geometric features. Road safety audits exist in large part to hunt for these locations, and stopping sight distance is one of the first things an auditor checks. Getting the number right, and then confirming the road actually delivers it, is a direct investment in whether people walk away from a bad moment or do not.
The number also carries legal weight. When a crash leads to litigation, one of the questions that surfaces is whether the road met accepted design standards, and stopping sight distance is near the top of that list. An engineer who can show a design was checked against the AASHTO Green Book values, under the conditions the road actually experiences, stands on solid ground. One who guessed, or who used braking distance alone, or who ignored a known downgrade, does not. This is why transparency matters in a tool like this: it shows every component of the calculation so the result can be explained and defended, not just reported.
How this tool runs the numbers
The engine follows the AASHTO Green Book formula exactly, and lets you swap in real-world conditions.
The core formula
On level ground, SSD in feet equals 1.47 times V times t, plus 1.075 times V squared divided by a. Here V is speed in mph, t is the reaction time in seconds, and a is the deceleration rate in feet per second squared. The first term is reaction distance and the second is braking distance. With the AASHTO defaults of 2.5 seconds and 11.2 ft/s squared, this reproduces the Green Book design table to the foot.
The friction option
Instead of a fixed deceleration, you can model braking through tire-pavement friction. Braking distance becomes V squared divided by 30 times f, where f is the friction coefficient. Dry asphalt is around 0.35, wet drops to 0.30, packed snow to 0.20, and ice near 0.11. This is how you see, in plain feet, why winter driving demands so much more room.
Grade adjustment
On a slope, braking distance becomes V squared divided by 30 times the quantity, deceleration over gravity plus or minus grade. A downgrade subtracts, lengthening the stop. An upgrade adds, shortening it. Enter grade as a percent, negative for downhill. Steep sustained downgrades, like a mountain pass, can add a serious margin.
The AASHTO comparison and crest curve
The tool checks your result against the official Green Book minimum for that speed and flags whether you meet it. It also reports the crest vertical curve length coefficient, so you can multiply by your algebraic grade difference to size a hill, using the standard L equals A times S squared divided by 2158.
Where the AASHTO numbers come from
The values this tool uses are not arbitrary. The 2.5 second reaction time comes from decades of driver studies, chosen because it covers roughly 90 percent of drivers even in moderately complex situations rather than just the quick-reacting average. The 11.2 ft/s squared deceleration rate, about 0.35 g, was selected because it represents braking that is firm but still controlled and comfortable, the level a typical driver can achieve on wet pavement without losing control or locking the wheels. In other words, the AASHTO defaults already bake in a wet-road, average-driver margin, which is why the level-dry table is reasonably conservative on its own.
That history explains a subtlety that trips up newcomers. If AASHTO already assumes a somewhat cautious deceleration, why bother with the friction method at all? The answer is that the built-in margin covers ordinary wet pavement, not snow, ice, or a steep downgrade. When conditions get genuinely harsh, the standard assumption no longer holds, and modeling the actual friction reveals just how much more room a driver truly needs. The two methods in this calculator are therefore complementary: the AASHTO method for standard design, and the friction method for showing what happens when the road turns hostile. Seeing both side by side is the fastest way to build an intuition for how fragile stopping really is once traction disappears.
Where this number shapes the roads you drive
Stopping sight distance is one of those quiet engineering numbers that touches almost every mile of road without most people ever noticing. Once you know what it governs, you start seeing it everywhere on your daily drive. Understanding the full range of where it applies is what turns a formula into a working design tool.
Crest vertical curves
The most common application is the hillcrest. When a road rises and then falls, the top of the hill blocks the driver’s view of whatever lies beyond it. The vertical curve that carries traffic over that crest has to be long and gentle enough that a driver approaching at the design speed can see far enough ahead to stop for a stalled car or fallen debris on the far side. Too sharp a crest and the sightline is cut off before the required distance, which is a design failure. This is why engineers compute the minimum curve length directly from the stopping sight distance, and why a road over rolling terrain has those long, sweeping crests rather than sharp peaks.
Horizontal curves and roadside clearance
Sight distance also governs how far back obstructions must be cleared on the inside of a horizontal curve. A retaining wall, a line of trees, a noise barrier, or even tall grass on the inside of a bend can cut off a driver’s view around the curve. Engineers calculate a clear sightline zone, called the middle ordinate, sized so that the available sight distance around the curve meets the stopping requirement. That is why you often see a mowed or cleared strip on the inside of highway curves. It is not landscaping, it is a safety sightline protected by this exact calculation.
Intersections and driveways
At intersections and driveways, a related family of sight distance checks makes sure a driver approaching or waiting can see far enough to react safely. Stopping sight distance sets the minimum a through driver needs to stop for a vehicle entering ahead. That is why zoning and access-permit reviews so often hinge on sight distance, and why a new driveway on a fast rural road can be denied if the sightline is too short. The same logic places stop bars and controls where crosswalks can safely go.
Work zones and temporary conditions
Sight distance does not only matter for permanent design. When a lane closes for roadwork, the buffer space between the taper and the work crew is sized to roughly the stopping sight distance, so an errant vehicle has room to stop before reaching workers. Temporary conditions like a stopped school bus, a mail truck, or a crossing guard all rely on drivers having enough sightline to react. The same physics that shapes a permanent hillcrest protects a crew patching potholes on a Tuesday morning.
Common mistakes and how to avoid them
The formula is simple, but a handful of errors show up again and again, in student work, in field checks, and occasionally in real designs. Each one is easy to avoid once you know to watch for it.
Confusing braking distance with sight distance
The most frequent mistake is forgetting the reaction phase. Braking distance alone, the ground covered after the brakes are applied, is only part of the story. A driver travels a substantial distance during the two and a half seconds before the brakes even engage, and at highway speed that reaction distance can be over 200 feet. Designing to braking distance alone leaves out that entire chunk and produces a sightline that is dangerously short. Always add the reaction distance, which this calculator does automatically and shows as its own line so the mistake is impossible to make here.
Using posted speed instead of operating speed
On an existing road, drivers rarely travel exactly at the posted limit. The 85th percentile speed, the speed at or below which most drivers travel, is often several miles per hour higher. Checking an existing road at only the posted speed can understate the sight distance drivers actually need, because they are moving faster than the sign says. For a realistic safety evaluation, use the true operating speed, and remember that even a five mile per hour difference moves the required distance noticeably because of the square relationship.
Ignoring the downgrade
Engineers sometimes skip the grade adjustment because the standard model is already conservative, and on gentle terrain that is reasonable. But on a steep, sustained downgrade, gravity meaningfully lengthens the stop, and ignoring it can leave a mountain road under-designed for the conditions drivers actually face in the wet or the ice. When the grade is significant and the road sees rain or snow, run the numbers with both the downgrade and a lower friction value to see the true requirement.
Forgetting that conditions change
The AASHTO level-dry table is a clean baseline, but roads live in the real world of rain, snow, worn tires, and tired drivers. A design that just meets the dry-pavement minimum offers no margin when the pavement is wet or the driver is distracted. Good practice builds in a cushion, either by designing above the bare minimum, by using a conservative friction value where winter weather is common, or by lowering the design speed. The goal is a road that stays safe on its worst normal day, not just its best.
Overlooking sightline obstructions
Finally, a road can satisfy the sight distance formula on paper and still fail in the field if something physically blocks the view. Overgrown vegetation, a poorly placed sign, a parked vehicle, or a sound wall can all cut the actual sightline below the calculated requirement. The number from any calculator is necessary but not sufficient. Someone has to walk or drive the road and confirm the line of sight is truly clear for the full computed distance, in every season.
Verified AASHTO design tables
These are the published federal design values from the AASHTO Green Book. The calculator reproduces the stopping sight distance column to the foot on level, dry ground. Use it as a field cross-check.
| Design speed (mph) | Stopping sight distance (ft) | Decision sight distance, urban stop (ft) |
|---|---|---|
| 20 | 115 | – |
| 25 | 155 | – |
| 30 | 200 | 490 |
| 35 | 250 | 590 |
| 40 | 305 | 690 |
| 45 | 360 | 800 |
| 50 | 425 | 910 |
| 55 | 495 | 1,030 |
| 60 | 570 | 1,150 |
| 65 | 645 | 1,275 |
| 70 | 730 | 1,410 |
| 75 | 820 | 1,545 |
| 80 | 910 | 1,685 |
Passing sight distance on two-lane roads
| Speed (mph) | Passing sight distance (ft) |
|---|---|
| 30 | 500 |
| 40 | 600 |
| 50 | 800 |
| 55 | 900 |
| 60 | 1,000 |
| 65 | 1,100 |
| 70 | 1,200 |
Friction coefficients by surface
| Surface and weather | Approx friction (f) | Effect on stopping |
|---|---|---|
| Dry asphalt or concrete | 0.35 | Baseline design value |
| Wet pavement | 0.30 | Roughly 15 percent more braking |
| Packed snow | 0.20 | Braking distance nearly doubles |
| Ice | 0.11 | Braking distance triples or more |
Three worked examples from US roads
The math makes sense fast when you run it on a real road. Here are three, worked the way an engineer would.
Example 1: A rural highway crest near Boise, Idaho
An engineer is checking whether a hillcrest on a 60 mph rural highway gives drivers enough sight distance. Using the AASHTO defaults, 2.5 seconds and 11.2 ft/s squared, on level dry pavement.
The result lands right on the Green Book minimum, exactly as designed. If the hill cannot provide 570 feet of clear sightline, the curve has to be lengthened or the speed lowered.
Example 2: A wet downhill approach in Seattle, Washington
A safety review looks at a 45 mph arterial that descends a 4 percent grade, often in the rain. Using the friction method with wet pavement at f = 0.30.
This is the case that catches people out. The level-dry table says 360 feet, but a wet downgrade can push the real requirement far higher. The tool shows the true number so the road is signed and designed for the conditions that actually occur.
Example 3: A winter mountain road near Denver, Colorado
A winter operations analyst wants to show why speeds must drop on a 50 mph mountain road when it is covered in packed snow, using f = 0.20.
The snow-covered number is dramatically longer than the dry-road table value. That gap, hundreds of extra feet, is exactly why variable speed limits and winter advisories exist on mountain corridors.
Field tips from highway design engineers
Design for conditions, not the table
The level-dry table is a floor, not a promise. If your road is wet, icy, or downhill, the real requirement is higher. Always design and sign for the worst conditions the road actually sees.
Respect the downgrade
A sustained downgrade quietly stretches every stop. On mountain corridors, combine the grade penalty with a wet or icy friction value to see the true distance, then consider a lower design speed.
Use operating speed on existing roads
When you are checking a road that already exists rather than designing a new one, use the real operating speed, often the 85th percentile, not just the posted limit. Drivers stop for what they actually do.
Add margin for older drivers
The 2.5 second reaction time covers most drivers, but complex urban scenes and older populations react slower. Bumping reaction time gives a more forgiving design where the mix of drivers warrants it.
Watch the eye and object heights
When you turn SSD into a crest curve length, the 3.5 foot eye height and 2.0 foot object height set the geometry. Different object heights, like a stop bar or pavement marking, change the curve you need.
Clear the sightline, not just the pavement
A road can have plenty of SSD on paper and still fail if vegetation, a sound wall, or a parked truck blocks the view. Check the actual line of sight in the field, not only the design drawing.
Quick reference table for road design
| Item | Rule of thumb |
|---|---|
| SSD formula (level) | 1.47 V t + 1.075 V squared / a |
| Reaction time | 2.5 s (AASHTO) |
| Deceleration | 11.2 ft/s squared (about 0.35 g) |
| SSD at 30 mph | 200 ft |
| SSD at 55 mph | 495 ft |
| SSD at 70 mph | 730 ft |
| Eye height / object height | 3.5 ft / 2.0 ft |
| Dry friction | about 0.35 |
| Ice friction | about 0.11 |
| Crest curve length | L = A S squared / 2158 |
Common questions from engineers and drivers
What is the AASHTO formula for stopping sight distance?
On level ground, SSD in feet equals 1.47 times V times t, plus 1.075 times V squared divided by a. V is speed in mph, t is the reaction time in seconds, and a is the deceleration rate in feet per second squared. The first term is the reaction distance and the second is the braking distance. With the AASHTO defaults of 2.5 seconds and 11.2 ft/s squared, this reproduces the Green Book design values exactly.
What is the stopping sight distance for 60 mph?
On level, dry pavement using the AASHTO method, the stopping sight distance for 60 mph is about 566 feet, which rounds to the Green Book design value of 570 feet. Of that, roughly 221 feet is reaction distance and about 345 feet is braking distance. A downgrade or wet pavement pushes the total higher, which this calculator shows directly.
What reaction time does AASHTO use?
AASHTO uses a brake reaction time of 2.5 seconds. This value is deliberately conservative, exceeding the reaction time of roughly 90 percent of drivers in simple to moderately complex situations. For unusually complex environments or older-driver populations, engineers sometimes use a longer time, which is why this calculator lets you adjust it.
How does grade affect stopping sight distance?
Grade changes the braking distance. On a downgrade, gravity works against braking, so the vehicle needs more room to stop and the required sight distance grows. On an upgrade, gravity helps braking and the distance shrinks. The effect uses the term deceleration over gravity plus or minus the grade. Steep, sustained downgrades like mountain passes can add a substantial margin.
Why does braking distance grow with the square of speed?
Because kinetic energy, the energy the brakes must dissipate, is proportional to the square of speed. Double the speed and the car carries four times the energy, so it takes about four times the distance to shed it. Reaction distance only grows linearly with speed, but braking distance grows with the square, which is why small speed increases produce large jumps in required sight distance. A practical way to feel this: going from 30 to 60 mph doubles your speed but roughly quadruples the braking distance, while the reaction distance only doubles. That is the mathematical reason speed is so punishing in a crash and why sight distance requirements climb so steeply on faster roads.
What is the difference between the AASHTO and friction methods?
The AASHTO method uses a fixed comfortable deceleration rate of 11.2 ft/s squared, which represents a driver braking firmly but in control on good pavement. The friction method instead uses a tire-pavement friction coefficient, letting you model wet, snowy, or icy roads directly. On dry pavement the two give similar answers, but the friction method is how you show the dramatic effect of poor traction.
What friction coefficient should I use?
Common design values are about 0.35 for dry asphalt, 0.30 for wet pavement, 0.20 for packed snow, and around 0.11 for ice. These are approximate and vary with pavement type, tire condition, and temperature. For a conservative winter design, use the lower values. The calculator provides these presets and lets you enter a custom coefficient for a specific study.
What is decision sight distance and how is it different?
Decision sight distance, or DSD, is a longer distance used where a driver must do more than just stop, such as at a complex interchange, a toll plaza, or a lane drop. It gives extra time to detect, understand, choose a maneuver, and execute it. DSD values are considerably larger than SSD, and this calculator shows the DSD reference alongside SSD so you can apply the right one for the situation.
How is SSD used to design a hill crest?
On a crest vertical curve, the hill itself blocks the driver’s view of the road beyond. The curve must be long enough that a driver at a 3.5 foot eye height can see a 2.0 foot object at the required stopping sight distance. The curve length uses L equals A times S squared divided by 2158, where A is the algebraic difference in grades and S is the sight distance. This tool gives you the coefficient to plug in your grade break.
Does AASHTO adjust SSD for grade in practice?
The Green Book provides a grade adjustment, but many state DOTs do not routinely apply it for stopping sight distance, because the standard model is already conservative and terrain varies. On significant sustained downgrades, though, the adjustment matters and should be considered. This calculator lets you include grade so you can see its size and decide whether it is material for your project.
What eye height and object height does AASHTO assume?
AASHTO assumes a driver eye height of 3.5 feet and an object height of 2.0 feet, which approximates the taillight height of a passenger car ahead. These heights are used when sight distance is turned into vertical curve geometry. Different applications, such as seeing a pavement marking or a stop line, use different object heights and therefore change the curve length required.
Is stopping sight distance the same as braking distance?
No. Braking distance is only the ground covered once the brakes are actually applied. Stopping sight distance is larger, because it also includes the reaction distance, the ground covered during the 2.5 seconds while the driver perceives the hazard and moves to the brake. Confusing the two is a common error that produces a dangerously short design, since it ignores the reaction phase entirely.
How much does wet or icy pavement increase stopping distance?
A lot. Going from dry pavement at f = 0.35 to wet at 0.30 adds roughly 15 percent to the braking distance. Packed snow at 0.20 nearly doubles it, and ice at around 0.11 can triple it or more. Because the reaction distance does not change, the total sight distance grows sharply on low-traction surfaces, which is the physics behind winter speed reductions and advisories.
Should I use design speed or posted speed?
For designing a new road, use the design speed. For checking an existing road, use the actual operating speed, often the 85th percentile speed, which is frequently a few miles per hour above the posted limit. Drivers stop for the speed they actually travel, not the number on the sign, so evaluating an existing road at its true operating speed gives a realistic safety picture.
What is passing sight distance?
Passing sight distance is the much longer distance needed on a two-lane, two-way road for a driver to safely pull out, overtake a slower vehicle, and return to the lane without conflicting with oncoming traffic. It far exceeds stopping sight distance and governs where passing zones and no-passing pavement markings are placed. This calculator lists the passing sight distance reference so you have it on hand.
Which AASHTO edition do these values come from?
The stopping sight distance formulas and design values come from AASHTO’s A Policy on Geometric Design of Highways and Streets, widely known as the Green Book. The core SSD equations have been stable across recent editions, including the 2011 sixth edition and the current seventh edition. States adopt the Green Book on their own schedules and may add amendments, so confirm the edition your state DOT enforces.
Is this calculator a substitute for a licensed engineer?
No. It is a fast, accurate tool for learning, planning, and field checks, built on the published AASHTO formulas, and it is ideal for estimating sight distance and studying for the PE and FE exams. Any geometric design that goes into construction on a public road must be prepared or reviewed by a licensed professional engineer under your state and agency standards. Site geometry, sightline obstructions, and local policy all matter beyond the formula. Think of this tool as the way to get a reliable first number and to sanity-check a design in the field, while a licensed engineer carries the responsibility for anything that directs real traffic. That pairing, quick transparent math plus professional review, is how good road design actually happens.
Related calculators for road and traffic work
Legal disclaimer and editorial transparency
This stopping sight distance calculator is provided for educational, planning, and field-reference purposes only. It applies the stopping sight distance formulas from AASHTO’s A Policy on Geometric Design of Highways and Streets, commonly called the Green Book, using a default brake reaction time of 2.5 seconds and a deceleration rate of 11.2 feet per second squared, along with an optional friction-based model and grade adjustment. Results are planning-level estimates, not a sealed geometric design.
Any roadway geometry deployed for construction on a public road must be designed, reviewed, and approved by a licensed professional engineer in accordance with your local, state, and federal standards, the AASHTO edition currently adopted by your state department of transportation, and site-specific conditions including sightline obstructions and terrain. USCalculators does not assume liability for design decisions made from these estimates. Always verify against the authoritative sources: the current AASHTO Green Book, the Federal Highway Administration, and your state DOT design manual.
Editorial transparency: Our formulas and reference values are drawn from AASHTO geometric design standards and published state DOT design manuals, and the stopping sight distance output was verified against the AASHTO Green Book design table during development. We update our tools as guidance evolves. If you spot an issue, we welcome corrections so the math stays accurate and the roads stay safe. Our aim is a calculator that a student, a working engineer, and a plan reviewer can all trust on the same problem, with every step of the calculation shown rather than hidden.