1 Aashto Roadside Design Guide

Understanding the AASHTO Roadside Design Guide

The 1996 edition of the AASHTO Roadside Design Guide is still the reference most state DOTs pull when they need to justify a roadside selection on a state-funded project. It is not a design manual in the sense that it tells you exactly what to do. It tells you what might happen if you do the wrong thing, and it gives you a framework for choosing between options. That distinction matters because people who treat it like a cookbook get into trouble. At its center the guide organizes roadways into four Roadside Design Ratings (RDRs). These range from RDR-1 through RDR-4. The ratings are based on traffic volume, design speed, roadside geography, and whether you are dealing with drivers who are used to the environment or not. In practice what happens is someone looks at an AADT of 18,000 vehicles moving at 55 mph on a two-lane rural highway and lands on RDR-3 because the roadside beyond the shoulder is a steep open ditch with a rock cut behind it. That sounds obvious but the rating part is where most people waste time arguing over. The actual rating comes down to a spreadsheet that AASHTO provides, and the spreadsheet is more subjective than anyone admits. When I start a new project my first move is not to open the guide itself. I open the state DOT's supplemental guidance. Nearly every state has one that modifies or supersedes AASHTO in specific ways. California's Caltrans Highway Design Manual, for instance, has its own side slope requirements that are stricter than AASHTO for certain speed ranges. Texas does something similar with clear zone tables. If you skip that step you will design to the wrong standard and then your review engineer will send the drawings back anyway.

After I confirm which state supplements apply I work through the AASHTO guide to justify the roadside selection. The workflow is straightforward. You determine the functional classification of the road. You pull the design speed. You calculate the clear zone using Table 10-1. You pick an RDR based on what fits. Then you decide whether you need a crash cushion, a barrier, a slopes-and-flatter recovery area, or a traverseable shoulder. The guide does not force any one outcome. It gives you tradeoffs. Here is where people get tripped up. The guide assumes a 95th percentile driver behavior model, which means it designs for the worst ten percent of drivers, not the average one. That is fine until you are working on a rural low-volume road where the traffic is almost entirely locals who know every curve. AASHTO will still push you toward RDR-2 or RDR-3 if the math says so, even though a community that has driven that road for forty years behaves differently. I learned this the hard way on a project in northern Montana where we had 1,200 AADT at 50 mph design speed. The spreadsheet wanted RDR-2. The county asked for RDR-1 because nobody ever left the road. We ended up using RDR-1 but with a wider shoulder and a documented traffic study from the county that showed zero run-off-road crashes in ten years. The state review accepted it because we had the data to back the deviation.

The Clear Zone Is Where Most Mistakes Happen

The clear zone table in Chapter 10 is the most cited part of the guide and also the most misunderstood. The values in Table 10-1 are not minimum distances. They are recommended offsets for obstacle-free zones that allow a errant vehicle to recover without hitting something fixed. The table does not mean that a 35-foot offset at 45 mph is sufficient and anything less is a failure. It is a recommendation based on historical crash data. What most junior engineers miss is that the clear zone values assume a traverseable shoulder. If your shoulder is unpaved gravel at a 6:1 slope, the effective clear zone shrinks. If it is mowed grass at 4:1, it stays close to the table value. The guide says this in Chapter 11 but in small print. I had a project in Ohio where the clear zone looked fine on paper, but the actual slope behind the shoulder was a compacted borrow fill that transitioned sharply into a 5:1 slope at the toe. A vehicle leaving the pavement at speed would catch that edge and trip. The fix was not a barrier. It was grading the transition to a flatter 6:1 slope and widening the clear zone by about eight feet. That cost less than a concrete barrier and performed better in service.

Obstacles and Fixed Objects Are the Real Problem

The guide is clearest when discussing fixed objects. Guardrail, concrete barriers, sign posts, bridge abutments, and drainage inlets are all covered in detail. The most useful section for day-to-day work is Chapter 4 on hazard reduction and Chapter 5 on roadside hardware. Chapter 4 explains that not every object needs to be shielded. If an object is outside the clear zone or behind a traverseable slope, you generally do not need a barrier. That sounds simple but in practice people spec barriers for everything because it is easier than explaining why they did not install one. On a recent interstate reconstruction in Virginia I ran into a situation where a drainage inlet sat just outside the nominal clear zone. The design speed was 65 mph. The inlet was a Type S grate on a flat slope. According to the strict reading of the guide, it did not require shielding because it was outside the clear zone. However, the slope leading into it was a 4:1 cut slope, which made it non-traverseable at higher speeds. Shielding it with a barrier would have been standard practice but also expensive and visually obtrusive in a historic district. I instead redesigned the inlet approach to a gentler 6:1 slope with a break in grade so that a vehicle could not gain enough upward momentum to hit the grate. That approach satisfied the reviewers and saved the client roughly $40,000 in barrier costs without compromising safety.

1 Aashto Roadside Design Guide Download and Resources

The guide is published by the American Association of State Highway and Transportation Officials. You can download a copy from the AASHTO website. The current official version is the 2011 revision with updates. Some states distribute their own annotated copies that include state-specific clear zone tables and commentary, which are usually more useful than the base document. There is also the Roadside Design Guide Companion Document that provides examples and sample calculations. It is free and worth reading if you are working on your first few projects. The AASHTO Roadside Design Guide has real limitations. It was written for the driving environment that existed when it was published, which means it reflects older vehicle fleet characteristics. Modern SUVs and trucks have different impact geometries and higher centers of gravity. The guide does not fully account for that. It also assumes that drivers will attempt to recover on their own rather than hit an object. That is not always true, especially on rural roads where signage is poor and speeds are higher than drivers expect. Another issue is the lack of guidance for low-volume roads below 6,000 AADT. The guide covers them but the recommendations become vague. You are expected to use judgment, which means different engineers will make different calls on the same road. If you are working on a county road with 800 AADT and 35 mph design speed, the guide will suggest RDR-1 and minimal treatments, but local conditions like ice, fog, or wildlife crossings can completely change what is actually safe. In those cases I supplement AASHTO with local crash data and, when available, a road safety audit from a certified professional.

The guide also does not address active countermeasures like dynamic messaging signs or intelligent barrier systems. If your project involves any of those, you will need to look elsewhere. The FHWA has separate publications on active roadside safety treatments that complement the guide. Using both together gives you a more complete picture than relying on AASHTO alone.

Common Pitfalls That Waste Time

The biggest waste I see is when engineers spend hours debating the exact clear zone boundary for a feature that is well outside the recovery zone anyway. Pick a rating. Document your reasoning. Move on. The second biggest is ignoring state supplements and designing to the base AASHTO tables only to have the state DOT return the plans. The third is not updating the guide version. The 2011 revision changed some clear zone values and added commentary on traverseable slopes. If you are still quoting the 1996 edition you are behind. I also see people over-specifying barriers. A short length of guardrail on a rural road where there is no fixed object to protect against is a waste of money and increases the risk of a penetration incident. The guide warns against this in Chapter 4 but the warning gets lost in practice. If you need a barrier, justify it. If you do not, say why. Both responses are acceptable if they are documented properly. The guide is a tool, not a rulebook. It works well when you understand what it is trying to do and where it falls short. Use it alongside state supplements, local crash data, and your own engineering judgment. That combination will serve you better than treating any single chapter as gospel.