National Academy of Sciences | 150 Year Anniversary

Questions? Call 800-624-6242

| Items in cart [0]

The National Academies Press

Rights & Permissions

topleft topright

HMCRP Report 1: Hazardous Materials Transportation Incident Data for Root Cause Analysis (2009)
Hazardous Material Cooperative Research Program (HMCRP)

Citation Manager

Transportation Research Board. "5.2.1 Develop Framework for Identifying Contributing Causes and Root Causes of Hazardous Material Accidents." HMCRP Report 1: Hazardous Materials Transportation Incident Data for Root Cause Analysis. Washington, DC: The National Academies Press, 2009.

Please select a format:

BibTeX EndNote RefMan


Page
96
bottomleft bottomright
Page
96
Front Matter (R1-R11)
Summary (1-8)
1.1 Project Purpose (9-9)
1.2.1 Literature Review (10-10)
1.2.3 Analysis of Databases (11-11)
1.3 Effective Methods to Ensure High-Quality Data (12-12)
1.4 Potential Measures to Enhance the Ability of Databases to Identify the Root Causes of Hazmat Crashes (13-13)
2.2.1 Rail Equipment - Train Accident Data (14-14)
2.2.2 Project 5 Overview - Developing Common Data on Accident Circumstances (15-15)
2.2.4 Transportation Research Circular 231: Truck Accident Data Systems: State-of-the-Art Report (16-16)
2.2.6 The Human Factors Analysis and Classification System - HFACS (17-17)
2.2.9 Highway Safety: Further Opportunities Exist to Improve Data on Crashes Involving Commercial Motor Vehicles (18-18)
2.2.11 Comprehensive Safety Analysis 2010: 2006 Listening Session (19-19)
2.2.16 Hazardous Materials Serious Crash Analysis: Phase 2 (20-20)
2.3 Summary of Findings and Implications (21-21)
2.3.2 Solutions Being Implemented or Under Consideration (22-22)
3.1 Introduction (23-23)
3.2 Summary of Responses from Carriers (24-24)
3.2.1 Carrier Satisfaction with HMIRS (25-25)
3.3.1 Shipper 1 (26-26)
3.3.2 Shipper 2 (27-27)
3.4.1 Interviews with Agencies Maintaining Databases (PHMSA) (28-28)
3.4.2 Interviews with Agencies Maintaining Databases (FMCSA) (29-29)
3.4.3 Interviews with Agencies Maintaining Databases (FRA) (30-30)
3.5 Summary of Findings from Interviews (31-31)
4.1.1 MCMIS Database Description (32-32)
4.1.3 Database Format (33-33)
4.1.6 Types of Fields Covered (34-34)
4.1.7 Database Purpose and Function (35-35)
4.1.10 Accuracy and Completeness of Data (36-36)
4.1.11 Identification of Hazmat Incidents in MCMIS (37-41)
4.1.12 Quality Control Process (42-42)
4.1.13 Interconnectivity with Other Databases (43-43)
4.1.14 Analyses Using Database (44-44)
4.1.15 Summary and Potential Measures for Improving Root Cause Analysis (45-45)
4.2 Hazardous Materials Incident Reporting System (HMIRS) (46-46)
4.2.1 Database Description (47-48)
4.2.3 Data Collection (49-49)
4.2.5 Accuracy and Completeness of Data (50-53)
4.2.8 Analyses Using Database (54-59)
4.2.9 Summary and Potential Measures for Improving Root Cause Analysis (60-60)
4.3 Fatality Analysis Reporting System (FARS) (61-61)
4.3.4 Types of Hazmat Data Included (62-62)
4.3.6 Data Quality (63-63)
4.3.7 Additional Fields (64-64)
4.3.9 Compatibility with Other Databases (65-65)
4.4.4 Types of Hazmat Data Included (66-66)
4.4.5 Usefulness of the Data for Determining Root Causes (67-70)
4.4.7 Additional Fields (71-71)
4.4.10 Data Uses (72-72)
4.5.1 Database Description (73-73)
4.5.3 Data Collection (74-74)
4.5.7 Interconnectivity with Other Databases (75-75)
4.5.8 Analyses Using Database (76-77)
4.5.9 Summary and Potential Measures to Improve Root Cause Analysis (78-78)
4.6 Railroad Accident/Incident Reporting System (RAIRS) (79-79)
4.6.1 Track, Roadbed, and Structures (80-80)
4.6.3 Mechanical and Electrical Failures (81-81)
4.6.5 Summary of Causes and Impact (82-83)
4.7.3 Data Collection (84-84)
4.7.5 Accuracy and Completeness (85-85)
4.8.1 Scope of Investigations (86-86)
4.8.2 Approach to Identifying Root Causes (87-87)
4.8.4 Data Quality (88-88)
4.8.5 Probable Cause Findings (89-89)
4.8.6 Summary (90-90)
4.9.1 Introduction (91-91)
4.9.4 Populating Records and Improving Data Quality (92-92)
4.9.6 Database Enhancements and Limitations (93-93)
4.9.7 Summary (94-94)
5.2 Information System Development (95-95)
5.2.1 Develop Framework for Identifying Contributing Causes and Root Causes of Hazardous Material Accidents (96-96)
5.2.3 Add or Modify Inventory Data in Databases (97-97)
5.2.5 Develop a System for Each Database That Will Target About 5% of Hazmat Crashes for More Detailed Investigation (98-98)
5.3.2 Complete Values for All Parameters (99-102)
5.4.1 Potential Measures for MCMIS (103-104)
5.4.2 Potential Measures for HMIRS (105-106)
5.4.3 Potential Measures for TIFA (107-107)
5.4.4 Potential Measures for RAIRS (108-108)
5.6 Follow-On Project (109-109)
References (110-111)
Appendices (112-112)
Abbreviations used without definitions in TRB publications (113-113)

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 96
96 Hazardous Materials Transportation Incident Data for Root Cause Analysis same hazmat truck crash may appear in FMCSA's MCMIS database and in PHMSA's HMIRS database. The information in these databases could be linked to combine information from dif- ferent sources on the same accident. Similar reasoning could apply for a hazmat rail crash found in FRA's RAIRS database and HMIRS, or a fatal hazmat truck crash in TIFA and MCMIS. Beyond the inherent advantage in linking hazmat crashes in different databases, additional information is needed to more effectively identify root and contributing causes. Current acci- dent data need to be supplemented by information about the circumstances and conditions that existed before the accident occurred, factors not presently captured. Since these additional pieces of information could come from a variety of sources, the term "information system" and not "database" is used to describe the components and structure of such a system. An example of the value of this approach is an analysis that NTSB performed on grade-crossing accidents. Approximately 60 unprotected private grade-crossing accidents were selected for study, beginning with the information commonly recorded in RAIRS. NTSB gathered additional information by visiting each site, and collecting information that both supplemented RAIRS data and validated on-site conditions listed in RAIRS. NTSB also obtained witness statements from accident sites as soon as possible. None of the information in the witness statements is captured in RAIRS and it is those data that showed driver distractions to be a frequent contributing cause of accidents. The data collected by the NTSB showed that driver grade-crossing visibility was often more limited than documented in RAIRS tables. Had the analysis relied solely on RAIRS data, poor visibility would not have been cited as a major contributing cause for these passive grade-crossing accidents. Although field data collection may be too labor intensive and costly on a recurring basis, this example illustrates the advantages of supplementing data in the databases. Another approach with considerable potential, which is currently being implemented by FRA, is more detailed investigation of a representative sample of accidents. FRA conducts approxi- mately 100 detailed investigations of rail crashes annually. These investigations obtain additional data that are not captured in RAIRS. Using the terminology in this report, approaches taken by NTSB and FRA comprise an infor- mation system for selected accidents. NTSB and FRA investigations illustrate the feasibility of supplementing information contained in current databases to address a specific class of acci- dents, improving the ability to identify contributing and root causes for these classes of accidents. Although site visits and witness statements might be difficult to obtain on a routine basis, clearly, if the FRA chose to target its 100 detailed investigations on a particular class of accidents, addi- tional data could be obtained for those targeted accidents. In successive years, the focus of the detailed investigations could be switched to a different class of accidents. For example, if FRA targeted private grade-crossing accidents for 60 of the detailed investigations, it could have pro- duced a report similar to the one produced by NTSB, concluding that the contributing cause, perhaps even the root cause, of many of the accidents was crossing visibility. 5.2.1 Develop Framework for Identifying Contributing Causes and Root Causes of Hazardous Material Accidents This section focuses on developing an information system capable of capturing the data for thousands of hazmat accidents that occur each year. This information system would not reside in a single database. Rather, the system would use a number of relatable databases, analysis tools, and reports that can, in their totality, contain the information in sufficient detail and quality to identify root and contributing causes of accidents. This would include those databases that are currently used to collect information on hazmat crashes. To identify the root and contributing causes of various classes of accidents, an analyst must be able to relate inventory information to the accident tables. Inventory information character-