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. "2.2.11 Comprehensive Safety Analysis 2010: 2006 Listening Session." 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
19
bottomleft bottomright
Page
19
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 19
Literature Review 19 Overall, GAO concluded that commercial motor vehicle crash data do not yet meet general data quality standards of completeness, timeliness, accuracy, and consistency. More specifically, for fis- cal year 2004, nearly one-third of commercial motor vehicle crashes that states are required to report to FMCSA were not reported and, of those that were reported, there were problems with accuracy, timeliness, and consistency (e.g., 15% of crash records reported to FMCSA could not be matched to the carrier's DOT number). Data quality problems most often stemmed from errors or omissions either by law enforcement officers at the scene of a crash or in the processing of crash reports to a state-level database. Among the specific problems cited were the following: 1. Infrequent opportunities for officers to receive training on filling out crash reports, 2. Unfamiliarity with what and how to report that result from infrequent occurrences of com- mercial motor vehicle crashes in an officer's jurisdiction, 3. Competing priorities at the officer level (where safety is a higher priority than data collection at the crash scene), 4. Use of manual crash reporting forms (compounded when the commercial vehicle crash report is a supplemental form), 5. Complex processes some states use to transform a report into the FMCSA format, and 6. An overall lack of quality control during data entry. To combat this problem, individual states are engaged in the following activities, utilizing federal funds allocated by FMCSA to support state efforts to collect and report commercial motor vehicle crash data: · Analyzing existing data to identify problems and develop plans for addressing them, · Reducing report backlogs that have not been entered into state-level databases, · Developing and implementing electronic data systems for collecting and processing crash information (e.g., on-scene reporting using handheld computers), and · Providing training on the definitions and criteria for commercial motor vehicle crashes and emphasizing the importance of data quality. To date, improvements in both the timeliness and number of reportable crashes have been observed, as measured by FMCSA's data quality rating system. However, GAO found that this sys- tem contains some flaws that can mask the true effectiveness of crash reporting and made specific recommendations for how to address these shortcomings. 2.2.10 In-Depth Accident Causation Data Study Methodology Development Report (SafetyNet) This report (Paulsson 2005) was prepared for the European Commission in order to develop a system for taking an independent, in-depth accident causation database and creating an investiga- tion process that identifies the main risk factors leading to a crash. The main difference between the proposed and existing systems is that this system would be constructed from the ground up with the sole purpose of determining the causes of accidents, unlike the multitude of existing databases that have to be cross-referenced, when even possible, to accomplish this objective. One major concern that this report recognizes is the need for accurate and consistent data. To address this concern, the report recommends conducting interviews and issuing questionnaires to confirm all aspects of an incident as well as implementing systems to review the procedures that data collectors are using at crashes. 2.2.11 Comprehensive Safety Analysis 2010: 2006 Listening Session This listening session (Coray Gurnitz Consulting and Abacus Technology 2007) enabled partic- ipants to supply ideas on how FMCSA could improve its commercial motor vehicle safety compli- ance and enforcement programs. Among the suggestions made were the need for higher quality