Cover Image

Not for Sale

View/Hide Left Panel
Click for next page ( 46

The National Academies | 500 Fifth St. N.W. | Washington, D.C. 20001
Copyright © National Academy of Sciences. All rights reserved.
Terms of Use and Privacy Statement

Below are the first 10 and last 10 pages of uncorrected machine-read text (when available) of this chapter, followed by the top 30 algorithmically extracted key phrases from the chapter as a whole.
Intended to provide our own search engines and external engines with highly rich, chapter-representative searchable text on the opening pages of each chapter. Because it is UNCORRECTED material, please consider the following text as a useful but insufficient proxy for the authoritative book pages.

Do not use for reproduction, copying, pasting, or reading; exclusively for search engines.

OCR for page 45
Database Analysis 45 attempting to identify root and contributing causes of accidents, any cells in Table 4-9 that are not shaded could not be shown to be contributing or root causes of accidents. The table clearly shows that the MCMIS dataset must be supplemented considerably before it can be a good source of information for identifying root or contributing causes of hazmat truck accidents. 4.1.15 Summary and Potential Measures for Improving Root Cause Analysis The MCMIS Crash file is formed using a complex set of operations that vary from one PAR originator to another, and Crash file preparation that varies from one state to another. Although the managers of the MCMIS Crash file have made great strides in improving the quality of the data, additional improvements are required for this database to be a useful tool in an information system that is capable of identifying contributing and root causes of accidents. The single biggest improvement in MCMIS crash reporting would be MCMIS parameter fields that are completely populated. Some fields should be required to be filled out, particularly those related to the vehicle, carrier, driver, route characteristics, and point-of-contact information. Additional improvements include the following: Require that the DRIVER_CONDITION_CODE field be filled out. In Hazardous Materials Seri- ous Crash Analysis: Phase 2 (Battelle 2005), the code "Appeared Normal" was the common entry for about 94% of the vehicle crash records. The codes for "Asleep" and "Fatigued" totaled about 3%, and the total for "Drugs or Alcohol Impairment" is about 1% and less than 1% for "Being Ill." The DRIVER_CONDITION_CODE field is clearly valuable, especially for programs designed to improve driver performance. This is the only field that captures driver performance in MCMIS and provides a valuable indicator of whether, in the opinion of the police officer fill- ing out the PAR, the vehicle driver was truly incapacitated. Fill all five hazmat fields completely and accurately for trucks carrying hazardous materials. Presently, in records where one or more of the fields indicates a vehicle as carrying haz- ardous materials, all five fields are completely filled out less than 15% of the time. When several of the fields are filled out, the entries are often inconsistent, making it difficult to make an accurate determination of when a truck was transporting a hazardous material, and the UN number, class, and/or name of the hazardous material actually being transported. Although it is normally possible to identify the name of the hazardous material from the data reported in the VEHICLE_HAZMAT_MATERIAL field, it should be noted that in either the recording of the information or in the electronic transmission of the data, the field is often truncated. Enter the DOT number for all serious crashes involving hazardous materials. Currently, a DOT number is entered for only 80% of the vehicles carrying hazardous materials. A carrier transporting hazardous materials, even if not involved in interstate commerce, must register with FMCSA and be assigned a DOT number. For hazmat shipments, it should always be pos- sible to assign a DOT number. Fill out the VEHICLE_CONFIGURATION_ID and ROAD_CONFIGURATION_ID fields. Specify the LOCATION field in a manner that enables the accident location to be found on a map. Presently, this is the case roughly 30% of the time. Specifying the route number or street name followed by the longitude and latitude is a straight-forward way to present location information. The difficulty in identifying the accident location on a map is aggravated by trun- cation of the field occurring somewhere in the recording or record transmission process, thereby eliminating key information. Give state personnel entering the data into the MCMIS crash record system access to databases containing information such as the MCMIS Registration file and the 49 CFR Part 172 Hazardous