Cover Image

Not for Sale

View/Hide Left Panel
Click for next page ( 36

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 35
Database Analysis 35 172.101 Hazardous Materials Table in 49 CFR Part 172. There is no requirement that the name of the material be taken from the Part 172 Table and, as a result, the trade name of the hazardous material is often entered. The CRASH_CARRIER Table contains information on the carrier and the CRASH_DRIVER Table contains information on the driver of the vehicle described in the CRASH_MASTER Table. The CRASH_EVENT Table can have any number of events for each entry in the CRASH_MASTER Table. This is where the event sequence for the accident is specified. Prior to the restructuring that occurred in about 2003, four separate fields named EVENT_1 EVENT_2, EVENT_3, and EVENT were provided for the reporter to describe the accident sequence following the initiat- ing event. The event codes are shown in Table 4-1. For example, if the accident sequence was a collision with a motor vehicle in transit, followed by the vehicle running off the road, followed by the vehicle rolling over, there would be three EVENT_ID records entered and the entries for SEQ_NO 1, 2, and 3 would be 13, 1, and 3, respectively. Note that these are all events and not conditions that would be useful for identifying contribut- ing causes of the accident. Conditions would have to be inferred from the CRASH_MASTER Table in fields such as WEATHER, ROAD_CONDITION, and LIGHT_CONDITION. Although there is an accident description narrative in all PARs, this narrative must be captured in code numbers in the CRASH_MASTER and EVENT tables. 4.1.7 Database Purpose and Function FMCSA is responsible for ensuring the safety of commercial interstate motor vehicle truck and bus safety. In order to ensure safety, the MCMIS Crash file has been developed to provide data on the number of serious truck and bus crashes that are occurring each year. From such information, FMCSA can monitor trends, evaluate the effectiveness of current regulations, and Table 4-1. Event codes and descriptions. Event Event Description Codes 1 Non collision ran off road 2 Non collision jackknife 3 Non collision overturn (rollover) 4 Non collision downhill runaway 5 Non collision cargo loss or shift 6 Non collision explosion or fire 7 Non collision separation of units 8 Non collision cross median/centerline 9 Non collision equipment failure (brake failure, blown tire, etc.) 10 Non collision other 11 Non collision unknown 12 Collision involving pedestrian 13 Collision involving motor vehicle in transit 14 Collision involving a parked motor vehicle 15 Collision involving a train 16 Collision involving pedalcycle 17 Collision involving animal 18 Collision involving fixed object 19 Collision with work zone maintenance equipment 20 Collision with other movable object 21 Collision with unknown movable object 98 Other