1 / 43

Why Should You Have Accessibility to Crash Data?

Why Should You Have Accessibility to Crash Data? . Because…. Improvements in producing high quality cause-of-death data are crucial for improving health and reducing preventable deaths. (World Health Organization)

dyan
Download Presentation

Why Should You Have Accessibility to Crash Data?

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Why Should You Have Accessibility to Crash Data?

  2. Because….. • Improvements in producing high quality cause-of-death data are crucial for improving health and reducing preventable deaths. (World Health Organization) • It removes the guesswork and efficiently places resources where they can best be used • It can assist in receiving federal funding for education, engineering and enforcement projects • It assists in reducing crashes, fatalities and serious injuries • It is your Data • It Saves Lives

  3. Can You Explain It Without the Crash Report? Must be a Fixed Object Crash

  4. Typical Data Analyzed from Crash Report(Not a Complete List) • Crash Type • Primary Cause • Secondary Cause • Weather condition • Traffic Control Device • Lighting Condition • Event Location • Vehicle Type • Alcohol Use • Road Surface Condition • Number of Lanes • Injury Classification

  5. Crash Data Analysis • Understanding “Why” there is a problem • Leads to beginning stages of Problem Identification • Mapping of crash locations • Summarizing of all data elements • Avoid making assumptions

  6. Very Important !Crash Report Narrative/Diagram

  7. PROBLEM IDENTIFICATION WB vehicle veered from its lane WB pickup dropped a wheel off to the right, overcorrected, ran off to the left and hit a house Motorcycle dropped off to the right, overcorrected and overturned on pavement SB vehicle missed a stop sign and hit passing WB semi Lost control in the snow and crossed into opposing lane in front of a semi SUV dropped wheel off to the right, lost control, and overturned on pavement SB pickup ran a stop sign and struck eastbound pickup WB SUV crossed pavement off to the south side, re-entered EB lane, and hit EB pickup truck Crash report not found Ran off road to the left and overturned Swerved to miss a deer and ran off the road to the left striking a utility pole EB car dropped a wheel off to the right, overcorrected, ran off to the left and overturned Lost control and crossed into opposing lane; head on SB van pulled from stop in front of EB pickup Ran off the road to the left and hit a utility pole EB car lost control and slid sideways in front of opposing traffic EB car hydroplaned in water at RR underpass and left road to the left, hitting the curb Dropped a wheel off on the right, overcorrected, ran off the road to the left, overturned

  8. And Yes sometimes they are Entertaining…..but Rarely! • Coming home I drove into the wrong house and collided with a tree I don’t have! • The other car collided with mine without giving warning of its intent! • I collided with a stationary truck coming the other way. • In my attempt to kill a fly, I drove into a telephone pole.

  9. Eliminate Assumptions in Data Analysis • Easy to assume cause based on “data” alone • The Narrative on the crash report from the Officer at the scene is extremely important • Verify cause through use of narrative/ diagram • Don’t Stop There -- Eliminate as many Assumptions as possible • Do Site Reviews

  10. Can you get copies of these or just Data generated from them?

  11. FHWA/IDOT Process Review • IDOT/FHWA meet once a year to Select Process Review Topics • Selection of topics should be based on real or perceived opportunities for improvement • IDOT/FHWA recommend topics for review • Final topic selection based on consensus of both IDOT/FHWA management

  12. Availability and Use of Crash Data Process Review Assess the AVAILABILITY and ACESSIBILITY of: Illinois Crash Reports and Data for the purpose of: IMPROVING problem identification and safety countermeasure selection

  13. Scope and Methodology • Evaluate • Stakeholder Accessibility to Crash Reports/Data • Stakeholder use of crash information • Document • Illinois Law • IDOT Policies/Practices • Types of crash data systems in use

  14. Interview/Survey Contacts Data Users/Owners • IDOT • Chief Counsel’s Office • Division of Traffic Safety • Bureau of Safety Engineering • Bureau of Local Roads • Districts 1,4 • Illinois Association of County Engineers Safety Committee • Chicago Department of Transportation • Chicago Metropolitan Agency on Planning • State, County and City Law Enforcement • Consultants • Emergency Medical Services

  15. Crash Data Accessibility Survey • Over 2000 surveys with 338 Responses • to: • County/City Engineers • Law Enforcement • Metropolitan Planning Organizations • IDOT Districts • Consultants • Emergency Medical Services

  16. Survey Results • 50.6 % Law Enforcement • 30.8 % Engineering • 18.4% Other Users • (Public/Private Sector)

  17. Does Your Organization Use Crash Data? • 68% Yes • 32% No (18.1% want it) • 11.5% Don’t Need It (Really?) • 9.5% Would access if they could • 8.3% Don’t know how to access • 0.3% Tried to acquire it but can’t • 2.4% No Response

  18. How do you access crash data • 36.4% Use Hard Copy Filing Systems of Completed Crash Reports • 29.3% Use Local Agency Electronic Data Base • 22.5% Uses IDOT System • 17.5% from IDOT Division of Traffic Safety • 7% from IDOT Bureau of Safety Engineering • 0.3% Use IDOT Safety Data Mart • 11.8% Other • Websites, GIS, Own software, MCR, Don’t try etc.

  19. Can you run your own crash data queries? • 40.2% Yes • 35.2% No • 24.5% No Response

  20. Does your organization have an internal system for storing/analyzing crash data? • 37.2% Yes • 62.8% No or No Response

  21. What issues have you experienced in accessing crash data? • 28.4% No Problems • 23.9% No Response • 16.9% Cannot access IDOT Safety Data Mart • 12.1% Slow Response Time • 9.7% Miscellaneous responses from • Too slow, SDM Too Difficult to use, Not enough current Data • 8.9% Inaccurate Data

  22. What method do you prefer to access crash data? • 29.3% No Response • 25.7% Password protected system through IDOT • 25.1% Current method is sufficient • 16.3% Internet • 3.6% Other • Would like to meet to discuss the options, the narrative of the crash report is imperative, enhanced County system

  23. Illinois Law • 625 ILCS 5/11-411 “Accident Report Forms” • IDOT has duty to prepare and supply crash report forms to police agencies • The written reports must have detailed information in accordance with standards. • (Pub. Act 78-255)

  24. Illinois Law (cont.) • 625 ILCS 5/11-408 “Police to report motor vehicle accident investigations” (Pub. Act 96-1147, eff. 7/21/10) • Police must submit all crash report to IDOT • Upon request, the Department shall furnish copies of its written crash reports to federal, state, and local agencies that are engaged in highway safety research and studies. (effective date July 2010)

  25. Illinois Law (cont.) • 625 ILCS 5/11-412 “Motor vehicle accident reports confidential” • All required written accident reports shall be for the confidential use of the Department and SOS • The Department may furnish copies of its written accident report to “federal, State, and local agencies that are engaged in highway safety research and studies (Pub. Act 95-757, eff. 7/25/08)

  26. Illinois Law (cont.) • 625 ILCS 5/11-414 “Department to tabulate and analyze motor vehicle accident reports” (Pub.Act 95-757, eff. 7/25/08) • Department shall tabulate and may analyze all written motor vehicle accident reports and shall publish annually or at more frequent intervals statistical information based on as to the number and circumstances of traffic accidents.

  27. Draft Observation/Recommendation • Observation: The language of four IVC statutes relating to crash reports and data has been interpreted in different ways over the years, is confusing and leaves gray areas for interpretation • Recommendation: Ensure all safety users have adequate accessibility to complete crash data for safety.

  28. Draft Observation • Observation: There seems to be a lack of formal IDOT policies and guidelines regarding the use of crash reports, there dissemination, review and updating

  29. Draft Recommendation • Create policy and guidelines to include: • What crash “data” or “reports” can be released • Define what information on crash report is “personal” and “confidential” and what can/cannot be released • Clarify who can receive data including the media, general public, researchers, consultants etc. and under what circumstances • Create guideline for regular review and updating of crash report form • Adhere to a strict schedule for completion of year end crash data within a certain time period • Create provisional data use policy

  30. Draft Observation • Factors such as lack of personnel, technical knowledge, time and difficulty accessing their own data, problem identification through the review of crash reports is difficult to produce for many county, city and state agencies.

  31. Draft Recommendation • Provide user friendly access to crash report images, mapped locations of crashes and query system to facilitate a more efficient and timely review of crash data • Include Enforcement, EMS, Education and Engineering

  32. Draft Observation • Many agencies commented that they were not aware of many techniques of crash data analysis and would like more training if it were available.

  33. Draft Recommendation • Create and provide training for crash data analysis to County, City, State agencies in the Education, EMS, Enforcement and Engineering fields for better problem Identification and countermeasure selection.

  34. Best Practice • IDOT District offices generally agree that they have good access to: • Crash Report Images • Crash Data • GIS Maps Recommendation: Review possible access of these systems for the rest of the data users.

  35. Illinois Statistics in 2012 • 956 People Died on Illinois Roadways • 274,111 Crashes • 83,768 Total Injuries • 12,401 “A” Type Injuries (Incapacitating) • Why? • Where? • When? • How Do We Fix It?

  36. The End

  37. Illinois Crash Fatalities: 1920 - 2012

  38. Illinois Motor Vehicle Deaths

  39. National Motor Vehicle Deaths

  40. 2012 National Projection 34,080 Motor Vehicle Fatalities Issued May 2013

More Related