Evaluation of 2006 Pennsylvania crash data reported to the MCMIS crash file
dc.contributor.author | Blower, Daniel Frederick | en_US |
dc.contributor.author | Matteson, A. | en_US |
dc.date.accessioned | 2007-10-17T17:02:48Z | |
dc.date.available | 2007-10-17T17:02:48Z | |
dc.date.issued | 2007-09 | |
dc.identifier | 99862 | en_US |
dc.identifier.other | UMTRI-2007-37 | en_US |
dc.identifier.other | DTMC75-06-H-00003 | en_US |
dc.identifier.uri | https://hdl.handle.net/2027.42/57181 | |
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 Pennsylvania. MCMIS Crash File records were matched to the Pennsylvania Crash file to determine the nature and extent of underreporting. Overall, it appears that Pennsylvania is reporting about 77 percent of crash involvements that should be reported to the MCMIS Crash file. However, the vehicle type variables in the Pennsylvania data contain inconsistencies, and the MCMIS Crash severity criteria cannot be applied directly. A method using the vehicle identification number (VIN) was employed to identify the appropriate vehicles, and a surrogate was developed for crash severity. Reporting rates were highest for fatal involvements, and significantly lower for injury/transported and tow/disabled crash involvements. Smaller qualifying vehicles were less likely to be reported than larger vehicles like tractor-semitrailers. Unlike most states, bus involvements were more likely to be reported than truck involvements. Reporting rates also varied by the type of investigation agency (state police, county, or city police). Missing data rates are low for most variables, except for driver license class, roadway access, and road trafficway. Some inconsistencies between data reported to the MCMIS file and recorded in the Pennsylvania data were also noted. | en_US |
dc.description.sponsorship | Federal Motor Carrier Safety Administration, Washington, D.C. | en_US |
dc.format.extent | 33 | en_US |
dc.format.extent | 194805 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 | Accident Records | en_US |
dc.subject.other | Accident Statistics/Accident Rates | en_US |
dc.subject.other | Buses | en_US |
dc.subject.other | Data Acquisition Methods | en_US |
dc.subject.other | Databases/Data Banks | en_US |
dc.subject.other | Evaluative Methods | en_US |
dc.subject.other | Motor Carriers | en_US |
dc.subject.other | Pennsylvania | en_US |
dc.subject.other | Police Reports | en_US |
dc.subject.other | State Governments/Province Governments | en_US |
dc.subject.other | Trucks | en_US |
dc.title | Evaluation of 2006 Pennsylvania crash data reported to the MCMIS crash file | en_US |
dc.title.alternative | Evaluation of 2006 Pennsylvania crash data reported to Motor Carrier Management Information System | 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/57181/1/99862.pdf | en_US |
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.