Road Safety Audits: An Overview 2015 Team Conference Henry Brown, P.E. Research Engineer University of Missouri March 11, 2015 1

1

Road Safety Audits: An Overview

2015 Team ConferenceHenry Brown, P.E.Research Engineer

University of MissouriMarch 11, 2015

2

Acknowledgements

• Craig Allred (FHWA)• John Miller (MoDOT)• Dana Ternus (NW Missouri Regional

Council of Governments)• Charlie Nemmers, Carlos Sun, and Praveen

Edara (University of Missouri)

3

Presentation Outline• Overview of RSAs• Procedures for RSAs• RSA Case Studies

4

Basic Concepts

• What is a road safety audit?• Why do we need RSAs?• When do we conduct RSAs?

5

What is an RSA?

• Formal safety performance examination

• Existing or Future Road Segment or Intersection

• Independent, multidisciplinary team

6

A road safety audit also…

• considers the safety of all road users

• considers interactions at the borders or limits of the project

• examines the interaction of project elements• may proactively consider mitigation

measures

7

… a simple standards check for adherence to design guidelines.

… an opportunity to redesign the project.

A road safety audit is NOT…

8

Why do we need RSA?

Road Environment Factors (28%)

Vehicle Factors (8%)

Human Factors (95%)

4%

24% 67%4%

4%

TYPICAL REPORTED CRASH CAUSES

9

Why do we need RSAs?

Relatively few road-related safety issues are identified in collision reports.

Road designs need to anticipate and accommodate common driver errors.

Easier to design and build safer roads than to modify some entrenched driver behaviors.

10

Reduce the number and severity of crashes

Promote awareness of safe practicesProcess to identify and address problemsConsiders human factors and multimodal issuesLow cost

RSA Benefits

11

When do we conduct RSAs?• pre-construction:– planning / feasibility– preliminary (draft) design– detailed design

• construction:– work zones– pre-opening

• post-construction/operational:– existing roads

12

When do we conduct RSAs?

13

The Eight Step RSA Process

Procedures

14

1 Identify project

2 Select

RSAteam

3 Start-up meeting

4Field

reviews

5Analysis

& Report

6 Present findings 7

Prepareresponse

8Implement

findings

Responsibilities RSA Team Design Team / Project Owner

15

1Identify project

2Select

RSA team

3Start-up meeting

4Perform field reviews under

various conditions

5Conduct auditanalysis and

prepare reportof findings

6Present findings 7

Prepareresponse

8Implement findings


1Identify project

1Identify project

16

Step1

Step1

In-service projectDesign stage project

Step 1: Identify the Project

17

High-crash sites

High-profile sites

Changed traffic characteristics

Step1

Step1Candidates for In-service RSAs

18

• Make structural changes on paper instead of in concrete.

• Optimize crash and conflict prevention.

RSAs: Design Stage Step1

Step1

19

1Identify project

2Select RSA team

3Start-up meeting


various conditions



6Present findings 7

Prepareresponse

8Implement

findings


2Select RSA team

2Select RSA team

20

• Independent

• Experienced

• Multi-disciplinary

Step2

Step2Select RSA Team

21

Operations

Step2

Step2

Geometric

Road users/human factors

Select the RSA Team: Core Skills

22

Interdisciplinary RSA Team: Composition and Size

• local agency staff

• exchange staff from another local agency

• consultants

• combination of above

Step2

Step2

23

1Identify project

2Select RSA team 3

Start-up meeting


various conditions



6Present findings 7

Prepare response

8Implement

findings


3Start-up meeting

3Start-up meeting

24

• Crash history

• Traffic volumes

• Aerial photographs

• Design drawings

• Background reports

• Design criteria

Step3

Step3The Start-up Meeting:

Provide Project Information

25

1Identify project

2Select

RSA team

3Start-upmeeting


various conditions



6Present findings 7

Prepare response

8Implement

findings


4Field

reviews

4Field

reviews

26

• Review available crash data

• Arrange transportation

• Designate a secretary and photographer

Step4

Step4Perform Field Review:

Preparation for the Field Review

27

Step4


Common Items to Look For• Sight distance obstructions• Pedestrian and cyclist conflicts• Visual clutter

28

Step4


Common Items to Look For• Roadside Hazards• Driveway Issues

29

Peak and off-peak traffic periods Dry and wet weather conditions Day and night conditions

Step4


Variable Conditions to Observe

30

Perform Field Review:Identify Safety Issues

Safety analysis considers three elements concurrently:

• geometry • operations• user characteristics and interactions

Step4

Step4

31

Identify Safety Issues: Geometry

Use of design standards and guidelines:

• a sound starting point

• cumulative effect of minimum/ maximum values

• supplement with human factors analysis and project-specific concerns (such as maintenance concerns)

Step4

Step4

32

• curve radius

• sight distance + curve + gradient

• hazard in clear zone

Identify Safety Issues: Geometry

Step4

Step4

33

Identify Safety Issues: Operations

• congestion and delay• signal operation• operating speeds• turning movements• queueing• driveways

Step4

Step4

34

Identify Safety Issues: User Characteristics and Interactions

• school buses• farm vehicles• trucks• cyclists• school children• driver age

Step4

Step4

35

Step4


Checklists and prompt lists:

• may provide structure to the site visit

• remind the team what to look for, and help ensure that nothing is missed

36

1Identify project

2Select RSA team 3

Start-up meeting


various conditions



6Present findings 7

Prepare response

8Implement

findings


5Analysis & Report

5Analysis & Report

37

Prioritize Safety Issues

may be based on crash frequency and severity:

• crash history (audits of existing roads)• expected crashes (design stage audits)– qualitative estimate of risk– quantitative estimate of risk

Step5

Step5

38

• Short term solutions include: maintenance, vegetation, changing signage or pavement markings, Enforcement & Education

• Long term solutions include: flattening a curve or modifying a roadway’s vertical alignment, Enforcement & Education

Step5

Step5Mitigate Safety Concerns:

Suggestions Appropriate to Project Stage

39

Early design stage:alignment changes

Later design stage: signing improvements

Step5

Step5Mitigate Safety Concerns:

Design-Stage

40

41

Roundabouts

42

Roundabouts

“If the politicians really go ahead with this, they’ll pay at the ballot box,” driver Turner Lane warned. “What goes around comes around.”

(Winnipeg Sun: April 1, 2013)

43

Short Range

Paint, Signage

Mid-Range

Contour Bank

Long-Range

Realign Skewed Intersection

Step5

Step5Suggested Countermeasures

44

Summarizes the project Identifies team Documents site visits Documents results Identifies and prioritizes

safety concerns May include suggestions for

improvements

Step5

Step5

The RSA Findings: Formal Report

45

Step5

Step5The RSA Findings:

Formal Report

46

1Identify project

2Select RSA team 3

Start-up meeting


various conditions



6Present findings 7

Prepare response

8Implement

findings


6Present findings

6Present findings

47

• Discussion of safety concerns

• Clarify findings and suggestions

• Assist project owner in making best choices

Step6

Step6The RSA Findings Presentation

48

1Identify project

2Select RSA team 3

Start-up meeting


various conditions



6Present findings 7

Prepare response

8Implement

findings


7Prepare response

7Prepare response

49

Inadequate Response

“We will not realign the intersection at Jefferson Road. We do not feel that it is needed.”

Step7

Step7Responses

50

1Identify project

2Select RSA team

3Start-up meeting


various conditions



6Present findings 7

Prepare response

8Implement

findings


8Implement findings

8Implement findings

51

Implementation - may depend on policy, manpower, and/or funding.

Step8

Step8Step 8: Implementation of

Improvements

52

Pre-construction RSAs:

Changes to design drawingsPost-construction RSAs:

Incorporate improvements in

operating budgets or maintenance programs

Step8

Step8Implementation of

Improvements

53

Examples:What to Look For

54

Sight Distance

SR42Before

55

Sight Distance

SR42 Before

56

Sight Distance

SR42 After

57

Sight Distance

SR56 Before

58

Sight Distance

SR56 After

59

Sight Distance

60

Sight Distance

61

Roadside Safety

62

63

64

65

66

67

68

Ph

oto

s: C

raig

Allr

ed

(F

HW

A)

69

70

71

72

73

74

75

Pavement Considerations

76

77

Drainage

78

79

Pavement Markings and Signs

80

81

82

83

84

85

86

87

BEFORE

AFTER

88

89

90

Signalization

91

92

Operations

93

Pedestrians

94

95

RSA Case Studies

96

Case Study 1: US 36 at S. Mitchell Avenue, Chillicothe, Missouri

Chillicothe

97

US 36 at S. Mitchell Avenue: Overview

98

US 36 at S. Mitchell Avenue: RSA Team

•Mo-Kan Regional Council• MoDOT• City of Chillicothe• Green Hills RPC• Delaware Valley RPC• Chillicothe Police Department• Missouri Highway Patrol• Northwest Missouri Regional Council of

Governments

99

US 36 at S. Mitchell Avenue: Statistics

• 21 Reported Crashes 2006-2011 • 2 Fatalities• AADT– US 36: 4,300 vpd–Mitchell Ave.: 1,000 vpd

• Speed Limit– US 36: 65 mph–Mitchell Ave.: 35 mph

100

US 36 at S. Mitchell Avenue: Sight Distance

101

US 36 at S. Mitchell Avenue: Signs

102

US 36 at S. Mitchell Avenue: Operations

103

US 36 at S. Mitchell Avenue: Suggested Improvements

• Increase Size of Essential Signs• Relocate Industrial Park Sign• Paint Yield Line, Stop Bar, Turn Arrows• Increase Lighting• Add Intersection Ahead Signs• Reconfigure Intersection• Extend Turn Lanes• Re-route Truck Traffic to US 65

Interchange

104

US 36 at S. Mitchell Avenue: Suggested Pavement Markings

105

Case Study 2: Bullhead Parkway, Bullhead City, Arizona

• 10.2 miles• 4-lane divided

highway• AADT 10,000 to

15,000 vpd• 50 mph speed limit• 17 intersections (4

signalized)

(FHWA 2012)

106

Bullhead Parkway RSA: Examples of Implemented Countermeasures

• Update Pavement Markings• Install RPMs on Inside Edge

Lines and Lane Lines• Extend Right Turn Lanes• Install Two-Direction Arrow

Signs at T-Intersections• Install Guardrail for

Embankments• Improve Grading at Median

Drainage Structures

(FHWA 2012)

107

Bullhead Parkway RSA: Crash Reductions

(FHWA 2012)

• 54% Total Crashes

• 50% Injury Crashes

• 30% Intersection-Related Crashes

108

Case Study 3: Work Zone RSA I-275 Tampa, Florida

• Two Interchanges• Positive Elements– Good delineation– Signal Backplates– Repeat Exit

Notification• Suggestions– Adding Signing– Crosswalks– Align Signal Heads– Signal Timing

(FHWA 2013)

109

Case Study 4: Design Visualization Burma Road, Rhode Island

• New Corridor• Used 3D Model• Recommended

Roundabout Over Signalized Intersection

• Other Suggestions– Lighting– Large turn

radius for trucks– Extend left turn

lanes

(FHWA 2011)

110

Case Study 5: Safe Routes to School Albany, Georgia

• Suggestions– Sidewalks around school

grounds– Upgrade signs and markings– H.A.W.K. Signal

(FHWA 2010 & 2011, National Center for Safe Routes to School, 2008)

111

Additional Resources• NCHRP Synthesis 336: Road Safety

Audits (TRB)• Road Safety Audit Guidelines (FHWA)• FHWA Website:

http://safety.fhwa.dot.gov/rsa• Bicycle Road Safety Audit Guidelines

and Prompt Lists (FHWA)• RSA Newsletter (FHWA)

112

Questions?

E2509 Lafferre Hall Columbia, MO [email protected]