Evaluation of 2006 Wisconsin crash data reported to the MCMIS crash file
dc.contributor.author | Green, Paul E. | en_US |
dc.contributor.author | Matteson, A | en_US |
dc.date.accessioned | 2008-05-06T18:02:12Z | |
dc.date.available | 2008-05-06T18:02:12Z | |
dc.date.issued | 2008-03 | |
dc.identifier | 100945 | en_US |
dc.identifier.other | UMTRI-2008-13 | en_US |
dc.identifier.other | DTMC75-06-H-00003 | en_US |
dc.identifier.uri | https://hdl.handle.net/2027.42/58356 | |
dc.description | Special report | en_US |
dc.description.abstract | This report is part of a series evaluating the data reported to the Motor Carrier Management Information System (MCMIS) Crash File undertaken by the Center for National Truck and Bus Statistics at the University of Michigan Transportation Research Institute. The earlier studies showed that reporting to the MCMIS Crash File was incomplete. This report examines the factors that are associated with reporting rates for the state of Wisconsin. MCMIS Crash File records were matched to the Wisconsin Crash file to determine the nature and extent of underreporting. Overall, it appears that Wisconsin is reporting 71.0 percent of crash involvements that should be reported to the MCMIS Crash file. All of the variables needed to identify vehicles that should be reported to the MCMIS Crash file are recorded in the Wisconsin PAR file. The vehicle type variable seems to be a derived variable since there is no space for recording levels of vehicle type on the crash report form. Vehicles coded as utility trucks are not included in this evaluation because it is estimated that only 8 percent have GVWR greater than 10,000 pounds. The reporting rate for tractor combinations is close to 90 percent, but the rate for straight trucks is approximately 50 percent. Reporting rates also show a decreasing trend as crash severity decreases. The reporting rate for the towed due to disabling damage criterion is 67.6 percent. Based on agency type, the reporting rate for the state patrol is 81.5 percent. Missing data percentages in the MCMIS Crash File are generally low, except as noted for certain variables. A comparison of the vehicle configuration variable between the Wisconsin and MCMIS Crash files shows some disagreement in the coding of this variable. | en_US |
dc.description.sponsorship | Federal Motor Carrier Safety Administration, Washington, D.C. | en_US |
dc.format.extent | 38 | en_US |
dc.format.extent | 2493835 bytes | |
dc.format.mimetype | application/pdf | |
dc.language | English | en_US |
dc.publisher | University of Michigan, Ann Arbor, Transportation Research Institute | en_US |
dc.relation.ispartofseries | MCMIS Crash File | en_US |
dc.subject.other | Wisconsin | en_US |
dc.subject.other | Motor Carriers | en_US |
dc.subject.other | Trucks | en_US |
dc.subject.other | Buses | en_US |
dc.subject.other | Evaluative Methods | en_US |
dc.subject.other | Databases/ Data Banks | en_US |
dc.subject.other | Data Acquisition Methods | en_US |
dc.subject.other | Accident Statistics/ Accident Rates | en_US |
dc.subject.other | Accident Records | en_US |
dc.subject.other | Police Reports | en_US |
dc.subject.other | State Governments/ Province Governments | en_US |
dc.title | Evaluation of 2006 Wisconsin crash data reported to the MCMIS crash file | en_US |
dc.title.alternative | Evaluation of 2006 Wisconsin crash data reported to the Motor Carrier Management Information System crash file | en_US |
dc.type | Technical Report | en_US |
dc.subject.hlbsecondlevel | Transportation | |
dc.subject.hlbtoplevel | Engineering | |
dc.description.bitstreamurl | http://deepblue.lib.umich.edu/bitstream/2027.42/58356/1/100945.pdf | |
dc.owningcollname | Transportation Research Institute (UMTRI) |
Files in this item
Remediation of Harmful Language
The University of Michigan Library aims to describe library materials in a way that respects the people and communities who create, use, and are represented in our collections. Report harmful or offensive language in catalog records, finding aids, or elsewhere in our collections anonymously through our metadata feedback form. More information at Remediation of Harmful Language.
Accessibility
If you are unable to use this file in its current format, please select the Contact Us link and we can modify it to make it more accessible to you.