National Academy of Sciences | 150 Year Anniversary

Questions? Call 800-624-6242

| Items in cart [0]

The National Academies Press

Rights & Permissions

topleft topright

TCRP Report 137: Improving Pedestrian and Motorist Safety Along Light Rail Alignments (2009)
Transit Cooperative Research Program (TCRP)

Citation Manager

Masliah, Maurice, Levinson, Herbert S, Cleghorn, Don, Clavelle, Allison, Boone, Jonathan, Transportation Research Board. "The NTD Database." TCRP Report 137: Improving Pedestrian and Motorist Safety Along Light Rail Alignments. Washington, DC: The National Academies Press, 2009.

Please select a format:

BibTeX EndNote RefMan


Page
24
bottomleft bottomright
Page
24
Front Matter (R1-R11)
Summary (1-7)
Phase I (8-8)
Phase II (9-9)
Structure of Final Report (10-11)
Literature Review (12-12)
Telephone Consultations (13-13)
Site Visits (14-14)
LRT Exposure to Pedestrians and Motor Vehicles (15-16)
Top LRT Safety Issues (17-18)
LRT Safety Treatments (19-19)
Summary (20-20)
Data Collection and Transfer between FTA/NTD, SSO, and Local Transit Agencies (21-21)
National Transit Database (22-22)
Data Collected by NTD (23-23)
The NTD Database (24-24)
NTD Data Quality Issues (25-30)
Analysis of the NTD Database (31-40)
Purpose of SSO Agency Safety Data Collection (41-41)
SSO Databases (42-42)
Data Collected by Local Transit Agencies (43-44)
Comparison of Databases (45-45)
Comparison of Local Transit Agency and SSO Agency Databases (46-47)
Comparison of Local Transit Agency and NTD Databases (48-49)
Conclusion (50-51)
Root Causes and Contributing Factors (52-52)
Determining the Highest Risk LRT Safety Issues (53-53)
Building a Safety Analysis Toolkit (54-54)
General Treatment Strategies (55-55)
Introduction to the Catalog of LRT Safety Treatments (56-56)
LRT Safety Treatments Included in the Catalog (57-57)
Safety Treatment Information Included in the Catalog (58-58)
Design Stage (59-59)
In-use Stage (60-60)
Prepare and Submit Safety Audit Report (61-61)
DoD Standard Practice for System Safety (MIL-STD-882D) (62-62)
LRT Risk Assessment Checklist (63-65)
Agencies with Multiple Accident Report Forms (66-66)
Categories of Information Included in Accident Reports (67-69)
FTA/NTD Data (70-70)
Structure of Reporting Forms (71-71)
Summary of Information to Be Included in the LRT Collision Database and Reporting Form (72-73)
References (74-74)
Appendix A - LRT Catalog of Safety Treatments (75-146)
Appendix E - Review of the Accident Data Collection Process (147-147)
Abbreviations used without definitions in TRB publications (148-148)

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 24
24 to incidents resulting in injuries/fatalities, and less focused The NTD Database on reporting incidents that do not. For example, prior to the issue of the 2008 Safety and Security Reporting Manual, an The NTD contained 66 data fields for each major incident. incident could not be classified as a major incident if a fatality Table 5 shows the data fields in the NTD summarized by was the result of a suicide, or if there were less than two injuries category of data. requiring immediate medical attention away from the scene. As shown in Table 5, the data fields contained in the NTD Table 4 shows criteria previously considered indicative of a provide comprehensive information for a variety of data cate- major incident and the years they were included. gories. The date and time of each incident is clearly specified, The implications of these changes in incident reporting and includes a field to indicate the time zone of the location should be considered when analyzing the data contained in where the incident occurred. The location of the incident is also the NTD. For example, prior to 2003, rail collisions at a grade clearly identified, and users are even provided with the option crossing were subject to the same reporting criteria as all other of specifying the exact longitude and latitude of the incident incidents, while in 2003 the NTD made all rail collisions at a location. All parties involved in the collision are classified (i.e., grade crossing reportable. From 2004 to 2007, collisions at pedestrian, motor vehicle) and described. grade crossings were given their own specific criteria (i.e., prop- The key categories of data with regard to safety analysis are erty damage exceeding $7,500, or one or more injuries) to be consequence of the incident, alignment/crossing controls, used in evaluating whether or not they were reportable. In the environmental factors, and exposure to risk. The consequence most recent edition of the NTD Safety and Security Reporting of the incident is quantitatively defined by the number of Manual, rail collisions at an at-grade crossing are once again injuries, the number of fatalities, and the extent of property subject to the same reporting criteria as all other collisions, but damage (in dollars) resulting from the incident. The alignment these have been changed since pre-2003. It should also be noted is identified based on the classification of the right-of-way that the definition of a crossing can vary. For a while, some cities as exclusive, semi-exclusive, non-exclusive, etc. The crossing (such as San Francisco) only defined LRT crossings with gates control field indicates the presence or absence of passive or as crossings. active control devices for road/rail grade crossings. If the inci- Frequent changes in reporting standards result in some dent occurred at a street intersection (common for LRT), the confusion among local transit agencies as to which inci- control device at the intersection is also provided. Environ- dents are reportable from year to year, and lack of uniformity mental factors include illumination, weather, ROW condition in collision data between years results in reduced ability to (i.e., dry, wet, slush, etc.), ROW configuration (straight, curve, make inferences from available data. Despite these disadvan- uphill, downhill, etc.), and ROW type (i.e., divided highway, tages, the NTD has introduced changes to NTD reporting intersection/grade crossing, etc.). criteria as part of its effort to balance the need to maximize Although the NTD included data fields for measures of expo- the quality and relevance of safety data in the NTD while sure, all five data fields in this category were blank for all of the minimizing unnecessary data collection and reporting at recorded incidents. In addition, examination of the NTD Safety the local level. and Security Manuals between 2003 and 2008 indicated that the Table 4. Reportable criteria. Years Included in Major Reportable Criteria Incident Reporting Criteria (Inclusive) A collision at grade crossing 2003 A collision at grade crossing resulting in at least one injury requiring immediate medical attention away from the scene or property damage equal 2004­2007 to or exceeding $7,500 A collision with person(s) on a rail right-of-way (ROW) resulting in at least one injury requiring immediate medical attention away from the scene for at 2003­2007 least one person A mainline derailment 2003­2007 A collision involving a rail transit vehicle resulting in at least one injury requiring immediate medical attention away from the scene for at least one 2003­2007 person Forcible rape 2006­2007 Confirmed terrorist events 2006­2007