1. Minnesota Crash Mapping Analysis Tool (MnCMAT) & Crash Data
Mark Vizecky (Va-Sis-Ski)
State Aid for Local Transportation
Program Support Engineer
Sulmaan Khan
State Aid for Local Transportation
Assistant Project Development Engineer
March 2012

2. Agenda Welcome - Introductions Sources of Crash Data
Crash Detail Levels
Methods of Retrieval
Transportation Information System (TIS) (Gen 1)
Excel Spreadsheet (Gen 2)
MnCMAT (Gen 3)
Overview
Case Studies
Demonstration
Analyzing the Data
Green Sheets
Top 200 Intersection/Top 150 Sections
Rates vs Density
Traffic Engineering Fundamentals Handbook
Wrap-up

3. Data Source and Criteria
Sources
Police Accident Report
Paper
Electronic
Citizen (public) Report
Criteria (D-16 manual)
Fatality, Injury or Property Damage >$1,000
Roadway open to the public
Death must be within 30 days for fatality
Intentional and medical caused NOT counted

4. Police Accident Report (PAR)
Overlay
Report

5. Police Accident Report (PAR)
Overlay (Front)
Overlay (Back)

7. Citizen Accident Report
(Front)
Report
(Back)

8. D-16 Manual
“…promote uniformity and comparability of motor vehicle traffic statistics..”

9. D-16: Sample (53 pages)

10. Model Minimum Uniform Crash Criteria (MMUCC)
“…provide a minimum, standardized data set for describing crashes of motor vehicles..”

11. A Crash is NOT a simple event….
PERSON LEVEL
CRASH LEVEL
VEHICLE LEVEL

12. Importance of Data Elements (Top 3)
Education
County/city location
Seat belt usage
Drinking
Enforcement
Corridor location
Time of day
Day of week
Engineering
Location

13. Crash Level data elements
Location
Route System
Route Number
Reference point
(nnn is wild guess)
Interchange element
Reliability
Numbers = DPS only, Alpha = MnDOT
1 or A – Confident (within feet)
2 or B – Less confident (within .25 mi)
3 or C - Best guess (within 1 mile)
4 or D - Wild guess (within county or city)
City
County

14. Route Systems State 01: Interstate 02: US Trunk Highway
03: Mn Trunk Highway
City
05: Municipal State Aid (MSAS)
10: Municipal (M)
County
04: County State Aid Highway (CSAH)
07: County Road
Other
08/09: Township (Organized/Unorganized)
14: State Forest road
23: Airport Roads
24:Private roads (no ref points)
30: Alleys (no ref points)
Etc.

15. Crash Level data elements
Location
Route System
Route Number
Reference point
(nnn is wild guess)
Interchange element
Reliability
Numbers = DPS only, Alpha = MnDOT
1 or A – Confident (within feet)
2 or B – Less confident (within .25 mi)
3 or C - Best guess (within 1 mile)
4 or D - Wild guess (within county or city)
City
County

16. Route Number (8 digits) Trunk Highways (Systems 1 – 3)
Leading zeroes not needed
ISTH 35W (stored as W)
USTH 169 (stored at )
MNTH 7 (stored as )
City Streets (MSAS and MUN)
First 4 digits are city number (NOT state aid number, but census number)
MSAS (Duluth)
MUN (Faribault)
ALL OTHERS
First 2 digits are county number
CSAH (Anoka county)
CR (Dakota county)

17. Crash Level data elements
Location
Route System
Route Number
Reference point
(nnn is wild guess)
Interchange element
Reliability
Numbers = DPS only, Alpha = MnDOT
1 or A – Confident (within feet)
2 or B – Less confident (within .25 mi)
3 or C - Best guess (within 1 mile)
4 or D - Wild guess (within county or city)
City
County

18. Interchange Element Sketches

19. Crash Level Data Elements
Non-Location
When
Date
Time
Day of week
Light conditions
What
Type
Weather conditions
Road Conditions
Speed limit
Work Zone
Etc.
Severity
For CRASH, derived from most severe injury/fatality
Number killed
Number Injured

20. Person Level Data Elements
Who
Non-Public (Name, Address) we do NOT get
Age
Gender
Condition
Alcohol
Drugs
License restrictions/endorsements
Safety Equipment
Seat Belts
Air bags
Helmet
Severity

21. Vehicle Level Data Elements
Vehicle info
Type
Make
Body type
Actions
Contributing factors (up to 2)
Sequence of Events (up to 4)
Pre-accident Action
Most harmful event
Direction of Travel

22. Transportation Information System (TIS)
Created in 1970’s
Mainframe:
User ID
SPF, JCL, TSO, ACF2
#?!#!!!! (not user friendly)
Huge users manual
Reports fixed format

23. Generation 1 – 1970’s and 1980’s List Accidents by Ref Point (paper)

24. Generation 2 – 1990’s Excel spreadsheets
Crash Level
Vehicle/Person Level

25. Pro’s – ALL Methods Important
TIS Mainframe
Traffic/Rate capabilities
Has intersection/section capabilities
Has sophisticated multi file linkages
The only practical option for some analysis
Excel
Easy to use – well known software
Sort and filter
Updated easily
MnCMAT
Mapping
Charting
Filtering

26. Generation 3 – 2000’s MnCMAT

27. Presentation Overview
Development of Program
MnCMAT Features
Case Studies
Gaining Access
Questions and Demonstration

28. Brief History of MnCMAT
Developed in Iowa
late 1990’s – early 2000’s
Iowa DOT & ISU
Original named Crash Mapping Analysis Tool (CMAT)
Introduced to Minnesota in 2006
Via County Engineers
Funded by
Local Road Research Board (LRRB) Project
Research Implementation Committee (RIC)
State Aid for Local Transportation (SALT)

29. Crash Analysis Tool Classification
Macroscopic Tool
Large Area Coverage
Trends and Statistics
Microscopic Tool
Drill Down Capabilities
Filters
Selection Capabilities
GIS Base Mapping Tool
Visual Tool
Charts
Maps
Reports
Data Files

30. Basics of MnCMAT Program
GIS Based Mapping System
MnDOT Mainframe Data
Transportation Information System (T.I.S.)
Location
Crash
Type
Road Condition
Driver Data
XXXXXX
T.I.S. Data is Generated from Law Enforcement and Citizen Crash Reports

31. Basic MnCMAT Crash Analysis Process
Step 1
Select Area to be Analyzed
Step 2
Apply Filtering Criteria
Step 3
Generate Output
Maps
Charts
Reports
Data Files

32. Basic MnCMAT Crash Analysis Process
Step 1
Select Area to be Analyzed

33. MnCMAT Data Covers Entire State
Primary Selection by County, District, Tribal Government, or State
Multiple Secondary Selection Methods
Rectangle
Polygon
Circle
Roadway Segments

34. State Wide Selection

35. MnCMAT Data Covers Entire State
Primary Selection by County, District, Tribal Government, or State
Multiple Secondary Selection Methods
Rectangle
Polygon
Circle
Roadway Segments

36. Single County Selection

37. Multiple County Selection

38. County Selection

39. MnCMAT Data Covers Entire State
Primary Selection by County, District, Tribal Government, or State
Multiple Secondary Selection Methods
Rectangle
Polygon
Circle
Roadway Segments

40. MnCMAT Toolbars

41. MnCMAT Data Covers Entire State
Primary Selection by County, District, Tribal Government, or State
Multiple Secondary Selection Methods
Rectangle
Polygon
Circle
Roadway Segments

42. Selection by Rectangle

43. MnCMAT Data Covers Entire State
Primary Selection by County, District, Tribal Government, or State
Multiple Secondary Selection Methods
Rectangle
Polygon
Circle
Roadway Segments

44. Selection by Polygon

45. MnCMAT Data Covers Entire State
Primary Selection by County, District, Tribal Government, or State
Multiple Secondary Selection Methods
Rectangle
Polygon
Circle
Roadway Segments

46. Selection by Circle

47. MnCMAT Data Covers Entire State
Primary Selection by County, District, Tribal Government, or State
Multiple Secondary Selection Methods
Rectangle
Polygon
Circle
Roadway Segments

48. Selection by Road Segment

49. Select Location with Find Location Selection
County
City
Intersection
Crash Number
XY Coordinate

50. Crash Data Using Stacks

51. Interchange Element Sketches
Question: How many crashes occurred at this interchange?

52. B C A

53. Basic MnCMAT Crash Analysis Process
Step 1
Select Area to be Analyzed
Step 2
Apply Filtering Criteria

54. Filter Selection

55. Filter Categories City Contributing Factor 1 Relation to Intersection
County
Crash Diagram
Crash Severity
Day of Month
Day of Week
Driver Age
Driver Condition
Driver Gender
First Harmful Event
Investigating Officer
Light Condition
MnDOT District
Month
Number of Fatalities
Number of Vehicles
Relation to Intersection
Reliability of Information
Road Design
Roadway Character
Speed Limit
Surface Conditions
System Class
Time of Day
Traffic Control Device
Travel Direction
Tribal Govt.
Type of Crash
Type of Work Zone
Vehicle Action
Vehicle Travel Direction
Vehicle Type
Weather Conditions
Year

56. Filters Within MnCMAT
Select the data applicable to the situation of interest.
Single or multiple filters may be applied.
Each filter provides “AND” logic between filter categories and “OR” logic within each filter

57. Active Filter Selection Statistics

58. Filters Within MnCMAT
Select the data applicable to the situation of interest.
Single or multiple filters may be applied.
Each filter provides “AND” logic between filter categories and “OR” logic within each filter

59. Filters Within MnCMAT OR
AND

60. Basic MnCMAT Crash Analysis Process
Step 1
Select Area to be Analyzed
Step 2
Apply Filtering Criteria
Step 3
Generate Output
Maps
Charts
Reports
Data Files

61. Graphical Outputs

62. View of Crash Incidents in Larger Area

63. Wide Area Crash Locations with Stacks

64. Non-motorized Persons
Were in Douglas County did crash number occur?
What can you tell me about the pedestrian?

65. Data Exports

66. Crash Data Exports as a CSV or Shape File

67. Crash Data Exported as a CSV or Shape File

68. Charts

69. Crash Severity

70. Day of Week

71. Reports

72. Summary Report

73. Detail Report

74. Crash Type Summary Report

75. Driver and Time Summary

76. Top 100 Intersections Report

78. Top 100 Segments Report

79. Crash Severity for Lane Departures Crashes
Case Study No. 1
Crash Severity for Lane Departures Crashes
Q. “What is the crash severity for lane departure crashes in the city of Faribault between ?”

80. Steps Needed for Case 1
Select Crash Data (circle with red, blue and yellow graphic), then select Crash Filters.
Highlight City under Location Filters, then check Faribault.
Highlight Crash Year, then check years
Highlight Crash Diagram and select crash codes pertaining to Run off Road crashes. (sideswipe passing/opposing, Ran off Road-Left/Right and head on)
Click OK.
Select Charts, then select Crash Severity under the dropdown menu, then select Add Chart

81. Lane Departure Crashes by Severity

82. Lane Departure Crashes by Severity
The previous slide illustrates that most crashes between involved property damage followed by possible injury crashes.
There was a total of 264 crashes during this time frame.

83. Case Study No. 2
Q. “What are the most dominant crash types resulting from chemical impairment in the city of Faribault?”

84. Steps Needed for Case 2 Select Crash Data, then select Crash Filters.
Highlight City under Location Filters and then check Faribault.
Highlight Vehicle Contrib. Factor 1 and then check Chemical Impairment.
Click OK.
Select Charts, then select Diagram under the dropdown menu, then select Add Chart

85. Crash Diagram (Type) resulting from Chemical Impairment in Faribault

86. Crash Diagram (Type) resulting from Chemical Impairment in Faribault
The pie chart on the previous slide illustrates that the three most occurring crashes as a result of chemical impairment are rear end, ran off the road (right side) and sideswipe (passing)
There was a total of 56 crashes.

87. Case Study No. 3
Q. “What number of reported crashes involve younger (under 21) distracted drivers (cell phone) that ran off the road in Faribault?”

88. Steps Needed for Case 3 Select Crash Data, then select Crash Filters.
Highlight City, and then check Faribault.
Highlight Driver Age, then check appropriate boxes for Drivers under 21.
Highlight Vehicle Contrib. Factor 1, then select Car Phone/Two-Way Radio, then click OK.
Select Charts, then select Diagram under the dropdown menu, then select Add Chart.

89. Distracted Young Drivers
MnCMAT Version 3.4.0
Online MnCMAT Tool

90. Distracted Young Drivers
Reports generated using both MnCMAT programs confirm the details of the two crashes
The crash reports indicate that there was one right angle and one rear end crash

91. Case Study No. 4
Q. “How many young drivers (<21) were involved in K & A crashes that was a result of disregarding a traffic device within Metro District ?”

92. Steps Needed for Case 4
Select Create New Project, then select the Metro District and click OK.
Select Crash Data, then select Crash Filters, then select Crash Severity and select the appropriate codes for K & A crashes.
Select Driver Age and select the appropriate ages for drivers under 21.
Select Vehicle Contrib. Factor 1 and select Disregard Traffic Device, and click OK.
Select Charts, then select Crash Severity under the dropdown menu, and then select Add Chart.

93. Young (<21) Drivers involved in K & A crashes by Disregarding Traffic Devices in Metro District

94. Young (<21) Drivers involved in K & A crashes by Disregarding Traffic Devices in Metro District
The graphs on the previous slide show that there were a total of 140 K & A crashes involving young drivers
Of the 140 crashes, 114 crashes (over 80%) were incapacitating accidents

95. Summary
The proceeding case studies are very basic examples of use of MnCMAT.
More complicated reports may be run. Even more complicated reports that require information on data not contained in MnCMAT (for example, seat belt use of non-drivers) would require special reports.

96. MnCMAT Distribution Being Supplied by MnDOT – State Aid
No additional software required
No Cost to City or County Agencies or Other Entities Approved by a City or County

97. Approval Form for Use

98. MnCMAT’s Website

99. DISCLAIMER
The State, County and Municipal Transportation Authorities of Minnesota make no representation or warranties, express or implied, with respect to the reuse of the data provided herewith, regardless of its format or means of its transmission. There is no guarantee or representation to the user as to the accuracy, currentness, suitability, or reliability of this data for any purpose. The user accepts that data “as is”, and assumes all risks associated with its use. The State, County and Municipal Transportation Authorities of Minnesota assume no responsibility, actual or consequential damage, as a result of any user’s reliance of this data.
By submitting this form, you are stating that you understand that this application is only a tool and that Engineering Judgment must be used when interpreting all data. You are also agreeing that you understand that the data set used by this program is subject to errors and changes, therefore not to be assumed as absolute. The Minnesota Department of Transportation, State Aid Division maintains all rights to this application and may revoke your privileges of use at any time.

100. MnCMAT Support Contact
Mark Vizecky
Sulmaan Khan

101. Intersection “Green sheets”

102. Section

103. Top 200 Intersections – per location

104. Crash costs – Step 1 Get Minnesota Data
Crashes
Fatalities
Injury A
Injury B
Injury C
Vehicles
Fatal
1,569
1,724
411
555
512
2,730
Severity A
5,674 -
6,636
1,735
1,494
9,991
Severity B
26,975
33,928
6,824
48,788
Severity C
49,894
65,755
96,651
PDO
186,839
340,915
Total
270,950
7,047
36,218
74,585
499,074

105. Step 2 – get current year costs from FHWA
GDP Deflator
Fatal
A injury
B Injury
C Injury
PDO
2003
106.41
$3,065,246
$212,209
$42,442
$22,400
$2,358
2004
109.43
$3,152,240
$218,232
$43,646
$23,036
$2,425
2005
112.74
$3,247,587
$224,833
$44,967
$23,732
$2,498
Step 3 – calculate cost for current year
Severity
Fatal Costs
Injury A Costs
Injury B Costs
Injury C Costs
PDO Costs
Sum Costs
Crashes
Cost per Crash
Fatal
$5,598,840,847
$92,293,939
$24,956,461
$12,150,974 *
$5,728,242,220
1,569
$3,650,887
Severity A
$1,491,991,660
$77,994,561
$35,456,161
$1,605,442,382
5,674
$282,947
Severity B
$1,525,626,673
$161,937,828
$1,687,564,501
26,975
$62,561
Severity C
$1,560,522,001
49,894
$31,277
PDO
$851,654,840
186,839
$4,558
*PDO costs are not shown due to incorporation into other crash severities.

106. Crash Costs Fatal $3,700,000 $6,800,000 Severity A $280,000 $390,000
Crash Severity
Existing Cost
New (2008) Cost
Fatal
$3,700,000
$6,800,000
Severity A
$280,000
$390,000
Severity B
$63,000
$121,000
Severity C
$31,000
$75,000
PDO
$4,600
$12,000

107. Top 150 Sections – per mile

108. Crash Rates Crash Rate = Crash Frequency Exposure/Unit of Time
Determined by dividing observed crash frequency by measure of exposure
Crash Frequency
Crash Rate =
Exposure/Unit of Time

110. Crash Rates Rate = Y/X 9 Short Comings: Assumes a linear relationship
Drives prioritization toward low volume routes 6
Frequency (Crashes/Year) 3 Y X
5,000
10,000
15,000
AADT

111. Crash Density Rates or Density ? For Intersections For Sections
Density = Crashes
For Sections
Density = Crashes/Miles
Rates or Density ?

112. Severity Rates For Intersections For Sections
SR = ((F*5)+(A*4)+(B*3)+(C*2)+(PD))
(EV * Days)
Where EV = Entering Vehicles.
For Sections
(ADT*Length * Days)

113. CRASH FACTS – annual report by DPS
Provides a statistical summary Minnesota’s reported crashes

114. Fundamentals Book

115. Crash Modification Factors (CMFs)

116. Books Worth Reading
The Drunkard’s Walk
Traffic

117. Minnesota 141,000 miles of Roadway 900 miles of Interstate2
900 miles of Interstate
11k miles of Trunk Highway
45k miles of County Road
22k miles of City Streets
62k miles of Township/Other roads
2009 K & A Crashes
421 Fatalities
1,036 Severe Injury Crashes 1 4 3 5 8 7 6

118. HSIP Program Challenge to determine where to focus safety funds
Black spots are infrequent on local roads
Fatal and Severe injury crashes are random on local roads
County Roads
2,089 Severe Crashes
45,000 miles of road
0.05 severe crashes per mile
Trunk Highway
2,168 Severe Crashes
12,000 miles of road
0.18 severe crashes per mile

119. Surrogates Heart Disease Smoking Obesity Cholesterol Blood pressure
Physical activity
Stress
Age/sex/heredity

120. Surrogates Heart Disease Surrogates for severe crashes? Smoking
Obesity
Cholesterol
Blood pressure
Physical activity
Stress
Age/sex/heredity
Surrogates for severe crashes?
Segments, Intersection, Run off Road Crashes…

121. Surrogates for Segments
Traffic Volume
Density of Road Departure Crashes
Curve (Critical Radius) Density
Edge Risk Assessment
Access Density
If surrogate applies to a segment of road 

122.  Surrogates for Curves ADT Range Radius Range Visual Trap on Curve
Intersection on Curve
Severe Crash on Curve
If surrogate applies to a roadway Curve 

123. Surrogates for Rural Thru STOP Intersections
Geometry
Skewed minor leg approach
Intersection on/near horizontal curve
Volume
Minor ADT/Major ADT ratio
Proximity
Previous STOP sign
Railroad crossing
Intersection Related Crashes
Commercial Development in quadrants

124. Questions?