Cover Image

Not for Sale

View/Hide Left Panel
Click for next page ( 43

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 42
42 incidents and the status of recommended corrective actions. rective action, and hazards forms from the local agencies, Thus, in addition to providing transit agencies with overarch- and groups the related files. Unfortunately the system han- ing safety and security standards, the SSO agency is actively dles each report file as a unit so it cannot support any sort of involved in overseeing the improvement of safety conditions at detailed analysis. They have a process by which reports are specific locations in response to specific incidents. reviewed and approved by the SSO staff electronically, or sent back to the local agency for changes. When the reports are approved, the SSO simply provides a password and user- Data Collected by SSO Agencies name to the FTA staff to allow access to the system and does According to the SSO Rule, SSO agencies are required to not then need to send the hardcopy or digital reports to the investigate, or cause to be investigated, incidents that satisfy FTA. Florida has shared this system with North Carolina, one or more of the following criteria: and is willing to share it with other states. Utah maintains a searchable log of collision notifications, A fatality at the scene, or where an individual is confirmed but this is a tracking log and does not include the entire dead within thirty (30) days of a rail transit-related incident; collision report. They prepare the annual report for the Injuries requiring immediate medical attention away from FTA using the reports they receive and send the report to the scene for two or more individuals; the FTA electronically. Property damage to rail transit vehicles, non-rail transit California receives reports from the local LRT agencies and vehicles, other rail transit property, or facilities and non- enters them into a database with an incident number. This transit property that equals or exceeds $25,000; is searchable by type and fatalities, but it is very limited. An evacuation due to life safety reasons; They are currently doing a feasibility study for a new data- A collision at a grade crossing; base system that would contain more information. They A main-line derailment; use the FTA template to report information. A collision with an individual on a rail right-of-way; Oregon receives collision notification reports by e-mail A collision between a rail transit vehicle and a second rail or telephone, and they are logged and tracked by agency. transit vehicle, or a rail transit non-revenue vehicle (4). Portland TriMet submits collision reports electronically, while Portland Streetcar submits in hardcopy. Oregon Information on the data management practices of a range issues the annual report to the FTA with all the data, cod- of SSOs was gathered though interviews with the key staff at ing it into the FTA templates. each agency. Of the seven SSOs (Arizona, California, Col- orado, Florida, Louisiana, Oregon, and Utah) contacted, both SSO Databases Louisiana and Colorado rely on hardcopy collision records from the local LRT agency. Arizona was contacted before their Of the seven SSO agencies contacted, only the CPUC pro- LRT system opened, and said that they intended to start col- vided a copy of their collision records initially. Utah DOT later lecting collision records using hardcopy. The other states provided some summary data which are also included in tables receive their reports in some electronic form from the local below where applicable. Some SSOs do not have databases, LRT agency either through e-mail, an online entry system, or but instead have hard or soft copies of incident reports, while electronic documents. others could not release their databases for unspecified reasons. A number of the SSOs are either pursuing increased elec- The CPUC database was provided in MS Excel format, and tronic data handling or are already using some sort of electronic contained a total of 22 data fields. Table 17 shows the data fields data management: contained in the CPUC database by data category. The CPUC database contains basic description of the date, Louisiana is working with the University of New Mexico to time, location, and classification of incidents. The consequence develop a web application capable of receiving all incident of the incident is quantified based on the number of injuries data electronically, and transferring the data to FTA elec- and fatalities sustained by both transit employees and other tronically. This setup would avoid the manual entry of data parties involved in the incident. The database also provides into the FTA spreadsheet forms. information regarding the crossing or intersection controls Arizona would like to eventually move to a database system. present. The "warning device" field indicated whether the cross- Colorado enters the non-confidential data from its hard- ing or intersection was controlled by lights, gates, traffic signals, copy collision reports into the FTA spreadsheet format. passive control devices, etc. Driver action is recorded in the Florida has an online reporting system developed in-house general "summary of incident" fields. The CPUC database also based around the Oracle database management system. It included a separate field indicating whether the collision was handles electronic submission of collision notification, cor- the result of a vehicle driving around a crossing gate.