Railroad special investigation report : Maryland Transit Administration light rail vehicle accidents at the Baltimore-Washington International Airport transit station near Baltimore, Maryland, February 13 and August 15, 2000

NHTSA · 2001 · ROSA P / United States. National Transportation Safety Board

archive: archived pipeline: cataloged verified

Get this paper ↗ (full text — opens at the source; we link to it, we don't host it)

Summary

This National Transportation Safety Board (NTSB) special investigation report examines two similar light rail vehicle (LRV) accidents involving the Maryland Transit Administration (MTA) at the Baltimore-Washington International Airport Station in 2000. The first accident occurred on February 13, 2000, when Train 24 struck a hydraulic bumping post and derailed, injuring 18 people. The second occurred on August 15, 2000, when Train 22 struck a bumping post and derailed, injuring 17 people. Although the direct causes differed, the NTSB identified common operational factors influencing both outcomes. The investigation focused on three primary safety issues: the adequacy of medication use requirements for operators, the impact of sleeping disorders on performance, and the reliability of event recorders. The February 13 accident involved an operator who had taken prescription pain medications (oxycodone and Tylenol 3) and aspirin on the day of the incident. The operator admitted to feeling tired and nauseated and acknowledged he likely dozed off. He failed to report his use of these sedating medications to the MTA, despite a policy expectation that operators disclose such use. Toxicological testing confirmed the presence of these drugs. The August 15 accident involved an operator diagnosed with obstructive sleep apnea (OSA), a condition that impairs alertness. The investigation found that the MTA lacked adequate screening and management protocols for OSA among its operators. In both cases, the operators failed to stop at the designated station, resulting in collisions with the track-end bumping posts. The report also highlighted significant deficiencies in the MTA’s event recording systems. The LRVs were equipped with event recorders designed to store data triggered by brake application. However, the software was flawed; it was designed to store only one event at a time, erasing previous data when a new event occurred, contrary to MTA specifications. Furthermore, the system failed to record the February 13 accident data correctly, showing a "flat-line" and a phantom triggering event that did not correspond to actual train movement. This malfunction prevented investigators from retrieving critical operational data regarding speed and brake application prior to the collision. Based on these findings, the NTSB issued safety recommendations to the Federal Transit Administration, U.S. rail transit systems, and the MTA. The recommendations emphasized the need for stricter regulations governing the use of prescription and over-the-counter medications by rail operators, including mandatory reporting and fitness-for-duty assessments. The Board also called for improved screening and management of sleep disorders, particularly obstructive sleep apnea, to ensure operator alertness. Additionally, the NTSB recommended improvements to event recorder technology to ensure reliable, continuous, and retrievable data storage for accident reconstruction. These measures aim to prevent future incidents caused by impaired operator performance and to enhance the ability to investigate rail transit accidents.

Key finding

Two light rail vehicle accidents occurred due to operator impairment from prescription medication and untreated sleep apnea, compounded by event recorder systems that failed to capture operational data.

Methodology

other

Provenance

The full processing record for this entry. Every stage of this paper's journey through the pipeline is logged — what ran, with which tool and model, how many attempts it took, and when it last completed. Discovered via bulk_ingest_rosap on 2026-05-23 (6 acquisition events logged).

Summary generated by qwen3.6-27b-prismaquant on 2026-06-10; verification: verified.

Topics

Ranked by relevance to this paper. Hover a topic for its definition.

• rail grade crossings