Difference between revisions of "907.5 S-HAL"

From Engineering_Policy_Guide
Jump to navigation Jump to search
m
m
Line 1: Line 1:
The HAL Manual (Identification, Analysis, and Correction of High-Crash Locations) was re-titled [[media:907.5 SHAL.pdf|S-HAL (Safety Handbook for Locals)]]. The First Edition of the HAL Manual was published in 1975.  The HAL Manual allowed local, non-MoDOT agencies to
+
The HAL Manual (Identification, Analysis, and Correction of High-Crash Locations) was re-titled [[media:907.5 SHAL.pdf|S-HAL (Safety Handbook for Locals)]]. The First Edition of the HAL Manual was published in 1975.  The S-HAL allows local, non-MoDOT agencies to
 
[[image:907.5 SHAL.jpg|right|375px|thumb|<center>'''[[media:907.5 SHAL.pdf|The S-HAL]] is not MoDOT policy but a supplemental document to the EPG.'''</center>]]
 
[[image:907.5 SHAL.jpg|right|375px|thumb|<center>'''[[media:907.5 SHAL.pdf|The S-HAL]] is not MoDOT policy but a supplemental document to the EPG.'''</center>]]
 
:*Develop a traffic record system (Chap 2)
 
:*Develop a traffic record system (Chap 2)

Revision as of 08:45, 24 November 2015

The HAL Manual (Identification, Analysis, and Correction of High-Crash Locations) was re-titled S-HAL (Safety Handbook for Locals). The First Edition of the HAL Manual was published in 1975. The S-HAL allows local, non-MoDOT agencies to

The S-HAL is not MoDOT policy but a supplemental document to the EPG.
  • Develop a traffic record system (Chap 2)
  • Identify high crash locations (Chap 3)
  • Analyze high crash locations (Chap 4)
  • Correct high crash locations (Chap 5) and
  • Conduct Road Safety Audits (Chap 6).

While the S-HAL was intended for local agencies and law enforcement, it has become a tool for MoDOT personnel as well. The S-HAL is not MoDOT policy, but only a supplemental document to the Engineering Policy Guide (EPG). Any information in the S-HAL that relates to topics in the EPG, the EPG takes precedence.

Additional Information
MoDOT’s safety engineers constantly search for the best practices in the field to improve Missouri roadways’ safety.
Safety Engineering
Safety Engineering

MoDOT has developed a traffic record system focused on the state maintained roadways and is developing the non-state maintained system. MoDOT’s traffic record system is also called the Transportation Management System (TMS). The TMS system uses roadway and crash information to develop High Severity lists for intersections and ranges. Districts are responsible to review these lists to develop their safety program strategies.

While identifying high crash corridors, Chapter 3 of the S-HAL explains some of the types of crash rates used when comparing locations. When comparing locations for a safety analysis, crashes are typically normalized by rate. Some of the rates covered by the S-HAL that are used in MoDOT studies include:

  • Number of crashes
  • Crash severity (EPDO – Equivalent Property Damage Only)
  • Crash rate
  • Number-Rate
  • Severity Rate (EPDO by rate)
  • Number-Quality-Control & Rate-Quality-Control

After high crash locations are identified, Chapter 4 of the S-HAL recommends information to gather to complete a traffic study. The procedure outlined in the S-HAL can be applied to any request for a field study. The first recommendation is to review crashes and complete a collision diagram. A collision diagram (S-HAL, Figure 4-1) is a spot map that shows where crashes are occurring, either within the intersection or along the range. The collision diagram will show the vehicle action, angle of collision and general location of the crash compared to the roadway. Other information important to the crash is included such as date, time of day, roadway/weather conditions, crash severity, etc. The TMS Accident Browser application uses computer software to produce an automated collision diagram for a single intersection. The collision diagram aids in identifying the predominant crash pattern at that location.

Another process in a traffic study is to perform an on-site observation. Depending on the crash history, it may be important to perform the observation both during the day and at night. The location should be driven from each direction. If there is a possibility for pedestrian travel, the location should be walked in order to view the road, as a pedestrian would experience it. The on-site report (S-HAL, Figure 4-2) should identify the location of the observation points, identify potential hazards by making a physical checklist, make notations regarding pedestrian and driver activity, take photos and interview local people for their observations of the location. When identifying potential hazards, it is important to draw a condition diagram (S-HAL, Figure 4-3), a drawing (to scale, if practical), of the existing roadway, control device locations and major features in the nearby environment. The condition diagram may also include physical road conditions, signing, striping, etc. that may be important in determining a countermeasure analysis. Also included when performing a field observation are traffic counts, spot speed studies and sight distance evaluations. The S-HAL has included worksheets to assist in the development of the location analysis (S-HAL, Figure 4-4).

According to Chapter 5 of S-HAL, after the locations have been identified, crashes analyzed and field data gathered, the corrective actions are determined. With most locations, there are potential low cost solutions, medium cost solutions, and high cost solutions.