Show simple item record

Evaluation of 2005 Ohio crash data reported to MCMIS crash file

dc.contributor.authorGreen, Paul E.en
dc.contributor.authorMatteson, A.en_US
dc.date.accessioned2007-01-25T19:23:45Z
dc.date.available2007-01-25T19:23:45Z
dc.date.issued2006
dc.identifier99790en
dc.identifier.otherUMTRI-2006-36en
dc.identifier.otherDTMC75-06-H-00003en
dc.identifier.urihttps://hdl.handle.net/2027.42/49328
dc.description.abstractThis report is part of a series of reports 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. 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 Ohio. This is the second MCMIS evaluation for the state of Ohio. Using 2005 data, MCMIS Crash file records were matched to the Ohio Police Accident Report (PAR) file to determine the nature and extent of underreporting. Based on this procedure, it is estimated that Ohio is reporting 42.5 percent of crash involvements that should be reported to the Crash file. This represents an improvement over the 35.8 percent reported in the first evaluation using 2000 data. Although the overall reporting rate was 42.5 percent, the reporting rate for carriers operating in interstate commerce was 79.1 percent, compared to 17.0 percent for intrastate carriers. Reporting rates also varied by crash severity, vehicle type, and reporting agency. The reporting rate for fatal involvements was 85.4 percent, compared to 52.7 percent for injured and transported involvements, and 32.3 percent for towaway. Crashes involving large trucks such as tractor semitrailers were more likely to be reported than single-unit trucks or buses. Crashes covered by the Ohio State Patrol were more likely to be reported than those covered by sherriff’s offices or local police departments. Ohio overreported 1,094 vehicles, or about 22 percent, to the MCMIS Crash file. Missing data rates are low for most variables, except in a few cases such as driver condition, road access, road trafficway, and Vehicle Identification Number (VIN). Comparison of the vehicle configuration variable between the MCMIS Crash file and the Ohio Crash file is generally good.en
dc.description.sponsorshipFederal Motor Carrier Safety Administration, Washington, D.C.en
dc.formatill., chartsen
dc.format.extent37en
dc.format.extent1015824 bytes
dc.format.mimetypeapplication/pdf
dc.languageEnglishen
dc.language.isoen_US
dc.publisherUniversity of Michigan, Ann Arbor, Transportation Research Instituteen
dc.relation.ispartofseriesMCMIS Crash Fileen
dc.subject.otherMotor Carriersen
dc.subject.otherTrucksen
dc.subject.otherBusesen
dc.subject.otherEvaluative Methodsen
dc.subject.otherDatabases/ Data Banksen
dc.subject.otherData Acquisition Methodsen
dc.subject.otherAccident Statistics/ Accident Ratesen
dc.subject.otherAccident Recordsen
dc.subject.otherPolice Reportsen
dc.subject.otherState Governments/ Province Governmentsen
dc.subject.otherOhioen
dc.titleEvaluation of 2005 Ohio crash data reported to MCMIS crash fileen
dc.title.alternativeEvaluation of Ohio crash data reported to Motor Carrier Management Information System crash fileen
dc.typeTechnical Reporten_US
dc.subject.hlbsecondlevelTransportation
dc.subject.hlbtoplevelEngineering
dc.description.bitstreamurlhttp://deepblue.lib.umich.edu/bitstream/2027.42/49328/1/Ohio2005_MCMISv3.pdfen_US
dc.owningcollnameTransportation Research Institute (UMTRI)


Files in this item

Show simple item record

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.