1 Minnesota Crash Mapping Analysis Tool (MnCMAT) & Crash Data Mark Vizecky (Va-Sis-Ski)State Aid for Local TransportationProgram Support EngineerSulmaan KhanState Aid for Local TransportationAssistant Project Development EngineerMarch 2012
2 Agenda Welcome - Introductions Sources of Crash Data Crash Detail LevelsMethods of RetrievalTransportation Information System (TIS) (Gen 1)Excel Spreadsheet (Gen 2)MnCMAT (Gen 3)OverviewCase StudiesDemonstrationAnalyzing the DataGreen SheetsTop 200 Intersection/Top 150 SectionsRates vs DensityTraffic Engineering Fundamentals HandbookWrap-up
3 Data Source and Criteria SourcesPolice Accident ReportPaperElectronicCitizen (public) ReportCriteria (D-16 manual)Fatality, Injury or Property Damage >$1,000Roadway open to the publicDeath must be within 30 days for fatalityIntentional and medical caused NOT counted
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 LEVELCRASH LEVELVEHICLE LEVEL
12 Importance of Data Elements (Top 3) EducationCounty/city locationSeat belt usageDrinkingEnforcementCorridor locationTime of dayDay of weekEngineeringLocation
13 Crash Level data elements LocationRoute SystemRoute NumberReference point(nnn is wild guess)Interchange elementReliabilityNumbers = DPS only, Alpha = MnDOT1 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)CityCounty
14 Route Systems State 01: Interstate 02: US Trunk Highway 03: Mn Trunk HighwayCity05: Municipal State Aid (MSAS)10: Municipal (M)County04: County State Aid Highway (CSAH)07: County RoadOther08/09: Township (Organized/Unorganized)14: State Forest road23: Airport Roads24:Private roads (no ref points)30: Alleys (no ref points)Etc.
15 Crash Level data elements LocationRoute SystemRoute NumberReference point(nnn is wild guess)Interchange elementReliabilityNumbers = DPS only, Alpha = MnDOT1 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)CityCounty
16 Route Number (8 digits) Trunk Highways (Systems 1 – 3) Leading zeroes not neededISTH 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 OTHERSFirst 2 digits are county numberCSAH (Anoka county)CR (Dakota county)
17 Crash Level data elements LocationRoute SystemRoute NumberReference point(nnn is wild guess)Interchange elementReliabilityNumbers = DPS only, Alpha = MnDOT1 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)CityCounty
19 Crash Level Data Elements Non-LocationWhenDateTimeDay of weekLight conditionsWhatTypeWeather conditionsRoad ConditionsSpeed limitWork ZoneEtc.SeverityFor CRASH, derived from most severe injury/fatalityNumber killedNumber Injured
20 Person Level Data Elements WhoNon-Public (Name, Address) we do NOT getAgeGenderConditionAlcoholDrugsLicense restrictions/endorsementsSafety EquipmentSeat BeltsAir bagsHelmetSeverity
21 Vehicle Level Data Elements Vehicle infoTypeMakeBody typeActionsContributing factors (up to 2)Sequence of Events (up to 4)Pre-accident ActionMost harmful eventDirection of Travel
22 Transportation Information System (TIS) Created in 1970’sMainframe:User IDSPF, JCL, TSO, ACF2#?!#!!!! (not user friendly)Huge users manualReports fixed format
23 Generation 1 – 1970’s and 1980’s List Accidents by Ref Point (paper)
25 Pro’s – ALL Methods Important TIS MainframeTraffic/Rate capabilitiesHas intersection/section capabilitiesHas sophisticated multi file linkagesThe only practical option for some analysisExcelEasy to use – well known softwareSort and filterUpdated easilyMnCMATMappingChartingFiltering
27 Presentation Overview Development of ProgramMnCMAT FeaturesCase StudiesGaining AccessQuestions and Demonstration
28 Brief History of MnCMAT Developed in Iowalate 1990’s – early 2000’sIowa DOT & ISUOriginal named Crash Mapping Analysis Tool (CMAT)Introduced to Minnesota in 2006Via County EngineersFunded byLocal Road Research Board (LRRB) ProjectResearch Implementation Committee (RIC)State Aid for Local Transportation (SALT)
29 Crash Analysis Tool Classification Macroscopic ToolLarge Area CoverageTrends and StatisticsMicroscopic ToolDrill Down CapabilitiesFiltersSelection CapabilitiesGIS Base Mapping ToolVisual ToolChartsMapsReportsData Files
30 Basics of MnCMAT Program GIS Based Mapping SystemMnDOT Mainframe DataTransportation Information System (T.I.S.)LocationCrashTypeRoad ConditionDriver DataXXXXXXT.I.S. Data is Generated from Law Enforcement and Citizen Crash Reports
31 Basic MnCMAT Crash Analysis Process Step 1Select Area to be AnalyzedStep 2Apply Filtering CriteriaStep 3Generate OutputMapsChartsReportsData Files
32 Basic MnCMAT Crash Analysis Process Step 1Select Area to be Analyzed
33 MnCMAT Data Covers Entire State Primary Selection by County, District, Tribal Government, or StateMultiple Secondary Selection MethodsRectanglePolygonCircleRoadway Segments
55 Filter Categories City Contributing Factor 1 Relation to Intersection CountyCrash DiagramCrash SeverityDay of MonthDay of WeekDriver AgeDriver ConditionDriver GenderFirst Harmful EventInvestigating OfficerLight ConditionMnDOT DistrictMonthNumber of FatalitiesNumber of VehiclesRelation to IntersectionReliability of InformationRoad DesignRoadway CharacterSpeed LimitSurface ConditionsSystem ClassTime of DayTraffic Control DeviceTravel DirectionTribal Govt.Type of CrashType of Work ZoneVehicle ActionVehicle Travel DirectionVehicle TypeWeather ConditionsYear
56 Filters Within MnCMATSelect 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
58 Filters Within MnCMATSelect 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
79 Crash Severity for Lane Departures Crashes Case Study No. 1Crash Severity for Lane Departures CrashesQ. “What is the crash severity for lane departure crashes in the city of Faribault between ?”
80 Steps Needed for Case 1Select 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 yearsHighlight 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
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. 2Q. “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. 3Q. “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.0Online MnCMAT Tool
90 Distracted Young Drivers Reports generated using both MnCMAT programs confirm the details of the two crashesThe crash reports indicate that there was one right angle and one rear end crash
91 Case Study No. 4Q. “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 4Select 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 driversOf the 140 crashes, 114 crashes (over 80%) were incapacitating accidents
95 SummaryThe 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 requiredNo Cost to City or County Agencies or Other Entities Approved by a City or County
99 DISCLAIMERThe 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 VizeckySulmaan Khan
104 Crash costs – Step 1 Get Minnesota Data CrashesFatalitiesInjury AInjury BInjury CVehiclesFatal1,5691,7244115555122,730Severity A5,674-6,6361,7351,4949,991Severity B26,97533,9286,82448,788Severity C49,89465,75596,651PDO186,839340,915Total270,9507,04736,21874,585499,074
105 Step 2 – get current year costs from FHWA GDP DeflatorFatalA injuryB InjuryC InjuryPDO2003106.41$3,065,246$212,209$42,442$22,400$2,3582004109.43$3,152,240$218,232$43,646$23,036$2,4252005112.74$3,247,587$224,833$44,967$23,732$2,498Step 3 – calculate cost for current yearSeverityFatal CostsInjury A CostsInjury B CostsInjury C CostsPDO CostsSum CostsCrashesCost per CrashFatal$5,598,840,847$92,293,939$24,956,461$12,150,974*$5,728,242,2201,569$3,650,887Severity A$1,491,991,660$77,994,561$35,456,161$1,605,442,3825,674$282,947Severity B$1,525,626,673$161,937,828$1,687,564,50126,975$62,561Severity C$1,560,522,00149,894$31,277PDO$851,654,840186,839$4,558*PDO costs are not shown due to incorporation into other crash severities.
117 Minnesota 141,000 miles of Roadway 900 miles of Interstate 2900 miles of Interstate11k miles of Trunk Highway45k miles of County Road22k miles of City Streets62k miles of Township/Other roads2009 K & A Crashes421 Fatalities1,036 Severe Injury Crashes1435876
118 HSIP Program Challenge to determine where to focus safety funds Black spots are infrequent on local roadsFatal and Severe injury crashes are random on local roadsCounty Roads2,089 Severe Crashes45,000 miles of road0.05 severe crashes per mileTrunk Highway2,168 Severe Crashes12,000 miles of road0.18 severe crashes per mile
120 Surrogates Heart Disease Surrogates for severe crashes? Smoking ObesityCholesterolBlood pressurePhysical activityStressAge/sex/hereditySurrogates for severe crashes?Segments, Intersection, Run off Road Crashes…
121 Surrogates for Segments Traffic VolumeDensity of Road Departure CrashesCurve (Critical Radius) DensityEdge Risk AssessmentAccess DensityIf surrogate applies to a segment of road
122 Surrogates for Curves ADT Range Radius Range Visual Trap on Curve Intersection on CurveSevere Crash on CurveIf surrogate applies to a roadway Curve
123 Surrogates for Rural Thru STOP Intersections GeometrySkewed minor leg approachIntersection on/near horizontal curveVolumeMinor ADT/Major ADT ratioProximityPrevious STOP signRailroad crossingIntersection Related CrashesCommercial Development in quadrants
Your consent to our cookies if you continue to use this website.