The Breaking News Blog

All the latest news from the District, Maryland and Virginia

Metro Safety System Failure Undisclosed Before June Crash

Network News

X Profile
View More Activity
By Joe Stephens and Lena H. Sun
Washington Post Staff Writers
Sunday, August 9, 2009

The crash-avoidance system suspected of failing in the recent deadly accident on Metro's Red Line malfunctioned three months earlier, when a rush-hour train on Capitol Hill came "dangerously close" to another train and halted only after the operator hit the emergency brake, newly obtained records show.

At the time of the March 2 incident, the train operator and control-center supervisors did not know that anything serious was wrong, the records indicate. The operator applied the brake because he realized that the train was not slowing fast enough and would overrun the station platform, a fairly common occurrence. About a week later, while reviewing computer logs, officials determined that there was a problem with the Automatic Train Protection system and that the train had stopped just 500 feet behind another.

Despite repeated promises of greater openness about safety, Metro officials did not make public the near miss at the Potomac Avenue Station, and federal investigators said Metro did not tell them about it after the Red Line crash, which killed nine people and injured 80.

The National Transportation Safety Board, which is investigating the June 22 crash, learned of the March incident last week when notified by the little-known Tri-State Oversight Committee, said NTSB spokeswoman Bridget Serchak. Metro officials did not immediately respond to questions about why they did not notify the NTSB.

The Washington Post discovered the incident while reviewing documents obtained through a public records request filed with the oversight committee, which was created 12 years ago to monitor Metro.

In an April 29 letter to Metro's chief safety officer, committee chairman Eric Madison asked Metro to conduct an investigation and submit a report about the Potomac Avenue incident, citing the "potentially catastrophic" nature of it. He said the train "violated a block," meaning it improperly shared a section of track with another train, and "came dangerously close to the leading train." Madison, a planner for the D.C. Transportation Department, wrote that it was only by "coincidence" that a Metro employee later noticed the incident in computer records.

Metro has yet to formally respond to the committee, which is empowered to oversee safety issues and make suggestions but cannot direct Metro to take action.

Metro spokeswoman Lisa Farbstein said Friday that although both incidents might have involved the failure of the protection system, they appear linked to different components and so would be unconnected.

"If a part goes down on the car, it's not necessarily related to the part that's on the track," said Farbstein, who described the March and June incidents as "very, very different."

Farbstein said the March incident, which took place at 4 p.m. on a Monday as a train on the Orange Line headed toward Vienna, was caused by a single failed relay on a subway car that has been fixed. The car was a 1000 series model, the same kind of car on the striking train in the June crash. The June crash is suspected of being caused by a faulty track circuit. Either problem could lead to a temporary failure of the Automatic Train Protection, a fail-safe system that monitors train locations and is supposed to automatically stop a train if it senses it is too close to another.

Farbstein said that because the car component was flawed, the six-car train at Potomac Avenue did not receive a stop command.

"The train operator did use the [emergency brake] when he realized he wasn't slowing down," she said. The train overshot the platform by about 75 feet, the length of a rail car, and halted about 500 feet from the train in front of it, she said. No one was injured, and the train was taken out of service.


CONTINUED     1        >

© 2009 The Washington Post Company

Network News

X My Profile
View More Activity