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. "4.2.9 Summary and Potential Measures for Improving Root Cause Analysis." 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
60
bottomleft bottomright
Page
60
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 60
60 Hazardous Materials Transportation Incident Data for Root Cause Analysis 4.2.8.7 Differences before and after Changes in HMIRS Structure Prior to the restructuring of HMIRS, hazmat records had to be duplicated to account for the presence of a carrier hauling hazardous material for several shippers in the same vehicle and for designating more than one destination for some of the packages. A query of the database for PHASE = 261 and ACCDR = True, shows that there are a total of 603 primary incident records for 2003 and 2004 and an additional 146 records to account for multiple shippers and multiple destinations. The total number of records is therefore 749 records, remarkably similar to the total of 747 records reported for 2005 and 2006 combined. Although not important when consider- ing root causes, it is easier to understand the shipment logistics after the restructuring. The total number of incidents is quite close as well, considering that in the 649 accidents reported for 2005 and 2006, 33 were associated with the new requirement to report non-spills if a cargo tank hav- ing a capacity of 1,000 gallons or greater was involved in an accident and there was damage to the cargo or the equipment protecting the cargo. If those were not considered, the number of crashes in 2005 and 2006 would total 616, again quite similar to the 603 reported in 2003 and 2004. A more detailed evaluation of the records is found in Appendix D (available on the TRB website at www.TRB.org by searching for HMCRP Report 1). 4.2.9 Summary and Potential Measures for Improving Root Cause Analysis 4.2.9.1 Summary of Database Evaluations The restructured HMIRS database can be considered to be a relational database and, except for the PKGFAIL Table, the record set for an en route accident is complete. Even in the case of the PKGFAIL Table, the data are available for about 80% of the HMIRS en route accidents. From the point of view of identifying route and contributing causes, this is not believed to be a signif- icant limitation. For a complete description of the package, vehicle, driver, and roadway characteristics asso- ciated with an accident, HMIRS would have to be joined with MCMIS for trucks and RAIRS for rail. Until the restructuring of HMIRS, the biggest detriment to joining the two databases was the lack of common fields. HMIRS now has a field to enter the DOT number, and this field is now being populated almost 90% of the time. The DOT number is also entered for about 90% of the MCMIS records designated as showing a hazmat placard. Assuming the non-reporting is random, the DOT number can be used to join about 80% of the accidents that meet both the HMIRS and MCMIS reporting criteria. Since all carriers of placarded quantities of hazardous material must register with both FMCSA and PHMSA, they must have a DOT number and there should be no blank entries in either database. Information technology has advanced to the point where both the carrier reporting in HMIRS and the police officer reporting to MCMIS have the capability to report the longitude and lati- tude of the accident. Providing that a common format is used in both databases, it is believed that one query could be used to identify accidents reported to both HMIRS and MCMIS and the data-scrubbing step could be eliminated or significantly reduced. The main reason why a fraction of the HMIRS and MCMIS records cannot be linked is the difference in reporting criteria. Some of the difference between the number of records in MCMIS that can be joined with HMIRS records can also be attributed to underreporting. It is suspected that carriers are not reporting all of their Report Type C accidents but that state- ment can not be made with certainty. Lastly, the carriers are providing action statements for 74% of the truck accidents and 46% of the rail accidents. An increase of the carrier reporting rate to at least 90% would be highly desirable. In addition, the action statements given are quite positive