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 22
22 Report form (S&S-50) on a monthly basis. This form reports action plan. However, some SSO agencies are moving toward a summary of the non-reportable safety and security inci- electronic database systems that would be suitable for conduct- dents that occurred within the previous month. Figure 3 illus- ing large-scale safety analysis. trates the transfer of incident data from the scene of the The project team conducted a survey of local transit agen- incident across the three levels of transit administration. cies to determine the availability and quality of collision data As indicated in Figure 3, the incident investigation can be at the local transit agency level. In total, 24 local transit agen- performed by the SSO agency, the local transit agency, or both. cies responded to the survey. Of these 24 agencies, 21 had col- However, in practice, it is the local transit agency that conducts lision data in either hardcopy or electronic format. The project the incident investigation and transfers the final investigation team followed up by requesting collision data from most of report to the SSO agency. the transit agencies who had indicated that they had collision data, but many transit agencies either did not respond to these requests or declined to provide collision data. In total, colli- Collision Data Available, Requested, sion data was obtained for eight local transit agencies. How- and Received ever, the transit agencies that did decide to provide collision In an effort to conduct a comprehensive review and accurate data were either unable or unwilling to provide it in database analysis of LRT safety data, the project team requested collision format. In addition, the time period covered by the data var- databases from a variety of transit agencies at each of the three ied from agency to agency. levels of transit administration. The NTD provided two complete databases in Microsoft National Transit Database Excel format, which contained all reported safety and security incidents that occurred between the years 2002 and 2007. The The United States Congress created the NTD to be "the first database contained all of the "non-reportable" (formerly Nation's primary source for information and statistics on the "non-major") incidents reported to the NTD through the S&S- transit systems of the United States" (5). 50 form. The second database contained all the "reportable" The mandate of the NTD is set forth in Title 49 U.S.C. (formerly "major") incidents reported to the NTD through the 5335(a), which states: S&S-40 form. Since the non-major incident database did not contain sufficient detail to either identify individual incidents To help meet the needs of individual public transportation systems, the United States Government, State and local govern- or be used in safety analysis, only the major incident database ments, and the public for information on which to base public (henceforth referred to as the "NTD database") was examined. transportation service planning, the Secretary of Transportation The project team also requested databases from a number of shall maintain a reporting system, using uniform categories to SSO agencies. However, only the CPUC provided a database accumulate public transportation financial and operating infor- for analysis. The CPUC database was provided in MS Excel for- mation and using a uniform system of accounts. The reporting mat, and included a total of 22 data fields. Based on discussions and uniform systems shall contain appropriate information to help any level of government make a public sector investment with SSO agencies, it appears that many SSO agencies do not decision. The Secretary may request and receive appropriate store electronic collision data suitable for conducting safety information from any source. analysis on multiple incidents. The data collected by SSO agen- cies is primarily intended for the investigation of individual Any recipient or beneficiary of the "Urbanized Area For- incidents with the goal of developing a suitable corrective mula Program" and "Other Than Urbanized Area (Rural) S&S-40 Reportable Incident Form within 30 days of incident Annual Submission S&S-50 Safety and Security Summary Form monthly NTD SSO Transfer of Final Investigation Report Local Incident Investigation Incident Investigation Incident Figure 3. Transit incident data transfer across levels of transit administration.