Cover Image

Not for Sale

View/Hide Left Panel
Click for next page ( 45

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 44
44 Hazardous Materials Transportation Incident Data for Root Cause Analysis to couple MCMIS with the LTCCS, but the coder of the accident data in the causation study have obscured any information that can be used to link the data in the LTCCS to the other databases. The data are only given by month and year, no state or day of the month is provided. The VIN number of the vehicle has been truncated, so it is difficult to match the numbers shown in the LTCCS with the numbers in MCMIS. No other common fields could be found. One useful improvement that FMCSA could make to the MCMIS Crash file that would increase the possibility of linking the file to other databases would be to restore the rule for how the REPORT_NUMBER field is constructed. Prior to 2001, the instructions to the state were to use the police report number in the REPORT_NUMBER field. That rule is no longer required, although some states clearly embed the police crash report number in the REPORT_NUMBER field. The actual police report number of a crash would permit a hard link to a specific crash, not just the probabilistic link obtained by using date, time, and geographic location. 4.1.14 Analyses Using Database The previous sections have described some of the characteristics of the MCMIS Crash data- base. Since the focus of this analysis is hazmat accidents, here the focus will be on techniques to identify accidents involving hazmat vehicles and then to show the characteristics of those crashes. The ways to join MCMIS crash records with the records from other accident databases will be discussed in this section. The results from joining two datasets when the same accident is reported in both (for example, MCMIS and HMIRS) will be summarized separately after the individual databases have been described. Hazardous Materials Serious Crash Analysis: Phase 2 (Battelle 2005), described in Chapter 2 of this report, developed a matrix listing the parameters that were believed to provide a comprehensive understanding of the accident environment. The project reviewed PARs and made telephone calls to the carrier to obtain data on those parameters. The parameters, divided into the five classifications of vehicle, driver, packaging, infrastructure, and situational are shown in Table 4-9. The unshaded boxes are not recorded in MCMIS and, for those that are recorded, the color codes show the percentage of the hazmat accidents that correspond to entries in MCMIS. When Table 4-9. Accident parameter coverage in MCMIS based on percentage not null. Vehicle Driver Packaging Infrastructure Situational Pre-Crash Configuration Age Package Type Road Surface Condition Cargo Body Experience Quantity Shipped Road Condition Dangerous Event GVW Condition Quantity Lost Road Type Vehicle Speed Vehicle Defect Valid License Age (Cargo Tank) Traffic Way Impact Location Vehicle Citation Issued Rollover Protection Access Control Primary Reason Response Driver Response Inspection History Speed Limit Accident Type Design Training No. of Lanes Weather Condition Specification Location Light Condition Time of Day Health Consequences Key: > 95% 50% to 95% < 50%