1 / 25

Enhancing the Oregon Crash Reporting Process: A Feasibility Study

Enhancing the Oregon Crash Reporting Process: A Feasibility Study. ITE District 6 Annual Meeting July 12, 2005 Chris Monsere, Ph.D., P.E. Research Assistant Professor Portland State University Department of Civil and Environmental Engineering monsere@pdx.edu Erin Wilson

lynton
Download Presentation

Enhancing the Oregon Crash Reporting Process: A Feasibility Study

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. Enhancing the Oregon Crash Reporting Process: A Feasibility Study ITE District 6 Annual Meeting July 12, 2005 Chris Monsere, Ph.D., P.E. Research Assistant Professor Portland State University Department of Civil and Environmental Engineering monsere@pdx.edu Erin Wilson Master of Urban and Regional Planning Candidate Portland State University ewilson@pdx.edu

  2. Background • Transportation safety improvements rely on accurate data • Crash data have traditionally been inaccurate or incomplete due to errors that are both systematic and random • States use a variety of systems to collect and record crash data

  3. State Comparison

  4. State Comparison - Colorado

  5. Oregon Process • Oregon relies on citizen reports for majority of crash data • Crashes must be reported if: • Greater than $1500 damage to own vehicle • Greater than $1500 damage AND towing of other vehicle • Injury or death • 50,000 crashes per year • 70% of crashes are recorded by ODOT

  6. Oregon Process - Problems • Time delay (1.5 years and up) • One paper copy of each incident • Potential for human error in reporting and coding. • Citizen • Police • Crash coders at both DMV and ODOT

  7. Oregon Process – Citizen Form

  8. Oregon Process – Police Form

  9. ORS 811.720 Requires Participants to Report to DMV Within 72 Hrs of a Crash Police Report Driver Report Insurance Co. Info 72+ hrs DMV Accident Records Unit codes data for driver info and insurance ODOT Crash Analysis & Reporting Unit codes data for crash information DMV Accident Records Unit archives crash report forms 30-90 days 30-45 days 90 days to 18 months Data Extracts Ad Hoc/Custom Reports Publications STIP Transportation Safety Programs Oregon Process

  10. Crash Report Audit • Form completion • Location • Type of crash • Date/Time • Weather • Road Conditions • Light • Direction of movement • Injury • Safety equipment • Diagram

  11. Crash Report Audit

  12. Crash Report Audit

  13. Survey

  14. Potential Improvements Three major areas for improvement: • Errors made on report by police officer or citizen • Errors occurring during manual coding processes • Delay in receiving crash data because of the amount of time required for the manual coding process

  15. Potential Improvements • Benefits of online vs paper form • Could require complete information • Automatic field population • Map tool for location identification • Calendar tool for date/time • Weather, road conditions, light fields could be programmed to reduce error • Faster reporting potential • Better diagram tool • More user friendly

  16. Potential Improvements • This project could save money in the long run: elimination of paper, mailing costs, transportation costs for paper records, and some staff time • Start-up costs for the new system would include: software and hardware purchases, staff time for development, staff time for training, staff time for reorganization of existing crash units.

  17. Estimated Savings

  18. Estimated Savings to DMV

  19. Estimated Savings – ODOT CAR Unit

  20. Conclusions • The public would require education about using the new system • Security and privacy concerns of citizens must be acknowledged • An online system could not entirely replace the paper method • An alternative or complement could be a scanning system to process paper forms

  21. Conclusions The overall benefits of the enhanced system will include: • Higher data quality due to less opportunity for error • Ease of collection • Ease of information transfer between agencies • Improved customer service

  22. Conclusions There are many other enhancements available that could improve data collection: • GPS devices in police cars • In-vehicle reporting for police • A simplified form for citizens • Scanning for paper forms • Electronic versions of forms transferred between DMV and CAR and archived.

  23. Conclusions

  24. Conclusions There are many other enhancements available that could improve data collection: • GPS devices in police cars • In-vehicle reporting for police • A simplified form for citizens • Scanning for paper forms • Electronic versions of forms transferred between DMV and CAR and archived.

  25. Questions?

More Related