Cover Image

Not for Sale



View/Hide Left Panel
Click for next page ( 73


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 72
72 Provide a reporting form structure that can be easily trans- alignment location (crossing or segment), details of geom- ferred into a searchable electronic database. Utilize check- etry, control devices, and traffic exposure. The database boxes and pull-down menus with a limited number of relevant should be updated as alignments and traffic volumes change responses, supplemented by text fields where necessary. (perhaps on a five-year cycle and after major construction). Record Exposure Data Summary of Information to Be Included in the LRT Collision Database and The information required to calculate and conduct mean- Reporting Form ingful comparisons of LRT collision rates should also be reported. Such information includes traffic exposure informa- Based on the analysis of the local, NTD, and SSO incident tion such as the number of vehicles crossing at a level crossing, databases, the project team compiled a list of potential fields the number of passengers boarding/alighting at a specific for an LRT collision reporting form and accompanying data- platform/station, and the number of pedestrians crossing the base. tracks per segment per unit time. As this information will not be available to the investigator at the scene of the collision, the Consider including the following fields on the LRT collision information will have to be obtained from the relevant source reporting form when it is developed: within the local agency and will need to be linked to the inci- dent report data after the on-scene data collection. Incident classification: Clear collision/incident distinction Ensure that LRT collision reports include fields for storing Type of object or individual involved geometric and traffic exposure measures that apply to the Type of impact specific incident site. These data may be sourced from local Location: exact location (cross referenced with separate municipalities or traffic agencies, and the database system LRT crossing database) storing the data should record the data source because it will Location detail: entering, exiting or dwelling in crossing or not likely be the same as that of the rest of the collision report. stop Weather conditions Illumination: daylight, dark, dawn/dusk, glare, streetlight- LRT Crossing Database ing (and condition of repair) As LRT collisions are relatively rare events, there may never Road/rail conditions: dry, leaves, water, ice, asphalt/ be enough LRT-related collisions at one location to develop concrete/gravel, upgrade/downgrade/level, construction, a statistically significant before-and-after study. To have straight/curve enough collisions to determine the safety effect of a treatment, Action of driver(s): researchers could compare the number of incidents at physi- Direction and speed of travel cally similar locations throughout one or more LRT systems. Use of head lights, tail lights, horn To undertake such analyses, researchers need to have geomet- Maneuver being executed ric and traffic control data for each crossing and information Source of information: driver, investigator, police, about any special safety measures or treatments that have been witnesses applied. Safety equipment: It is not enough to have this information only for locations Crossing type where there are incidents. An analysis database should include Traffic controls all crossing locations to determine the impacts of different Transit signal presence, type, indication of transit signal measures over the "do nothing" option in each of the alignment Aspect of signals types. The FRA maintains a similar database for heavy rail cross- Type and condition of switch ings, but the database for LRT needs to be significantly larger as Visibility and functionality of traffic signs/signals it needs to include information about crossings and segments Visibility and functionality of grade crossing devices between crossings where a vehicle or pedestrian may be able to (i.e., gates) enter the alignment. As compiling and updating the database is Presence and type of other safety treatments a significant undertaking and beyond the resources of most LRT Property damage: a repair cost estimate for all vehicles agencies, a national program appears to be necessary. involved, but with an option to provide a simpler classi- fication of damage with clear definitions (i.e., repairable/ To support analyses of LRT safety, an LRT crossing data- irreparable damage to LRV, repairable/irreparable damage base could be created. This database could include, for each to private vehicle)

OCR for page 72
73 Injuries/fatalities: Exposure (to be completed following contact with the Number of injuries of each class (predetermined classes appropriate agency): of severity) in each vehicle. Annual average daily traffic volume, number of pedes- Contact information: for drivers, vehicle owners, witnes- trians boarding/alighting, number of pedestrians per ses, emergency personnel, agency employees involved in segment per unit time investigation Source of exposure data