baltimoresun.com

« Rumblings against Red Line get louder | Main | Triple whammy for downtown traffic this weekend »

July 13, 2009

D.C. Metro replies to NTSB

Washington Metro officials say they can't immediately comply with a  recommendation from the National Transportation Safety Board that they add another layer of safety precautions to the subway system because such a technology is  not commercially available.

The NTSB issued an emergency  recommendation Monday that the Metro incorporate a new backup system into its crash-protection measures in the wake of the  June 22 collision of two trains. Nine people died in that ccrash -- the worst in the history of the Washington Metro.

The NTSB investigation has reached a preliminary finding that a circuit failure in Metro's current crash avoidance system failed, leaving the operator of a following train unaware that another train had stopped  on the tracks ahead. The board said the crash showed the Metro "is susceptible to a single-point failure" and should add a level of redundancy to its protections.

However, in its reply, the Metro board said its system is not compatible with any other existing transit system and  that any new protection technology would have to be  invented.

The Metro system's full reply follows:

 

Metro’s Board of Directors and General Manager appreciate the recommendations from the National Transportation Safety Board to Metro and the Federal Transit Administration. This has implications that reach far beyond Metro, and extend to the entire transit industry.

In spite of the issuance of this recommendation, the NTSB still has not determined the root cause of the accident. Every component of that circuit has been replaced, but the problem still persists. This is not a simple problem as is evidenced by the NTSB’s statement that “investigators are continuing to examine the train control system circuitry and recorded data to better understand how the train control system functioned prior to the accident."

It is important to know that there are currently no systems available commercially that could provide the Metro system with the kind of alerts that the NTSB has recommended, and that such a system must be invented. San Francisco’s Bay Area Rapid Transit system for example, would not meet our unique needs. We believe the NTSB acknowledged this much in its letter today, stating, “The NTSB believes that software algorithms or additional circuitry could be developed to continuously evaluate the validity of real-time track occupancy data and alert operations personnel when problems are detected.” As a result, we will be developing a new system that will be specifically tailored to Metro. Metro is in the process of contacting vendors who have the expertise needed to help us develop this service, and we are preparing cost estimates on this application.

Metro is also pleased that NTSB has now agreed to allow us to move forward with our plan to initiate an independent panel of experts in signal systems through the American Public Transportation Association before the NTSB investigation has been completed.

The safety of our customers and our employees continues to be our prime concern. As a result of the accident of June 22, 2009, we immediately returned control of all trains to manual mode. We will continue to operate in manual mode until a suitable backup, designed specifically for our rail system is developed. For more than 30 years, the current rail system has operated without a failure like the one we experienced on June 22, but we will devote all of our resources to implementing NTSB’s recommendation as soon as possible

Posted by Michael Dresser at 5:37 PM |
Categories: WMATA/D.C. Metro
        
About Michael Dresser
Michael Dresser has been an editor, reporter and columnist with The Sun longer than Baltimore's had a subway. He's covered retailing, telecommunications, state politics and wine. Since 2004, he's been The Sun's transportation writer. He lives in Ellicott City with his wife and travel companion, Cindy.

His Getting There column appears on Mondays. Mike's blog will be a forum for all who are interested in highways, transit and other transportation issues affecting Baltimore, Maryland and the region.
-- ADVERTISEMENT --

Live traffic updates
Most Recent Comments
Baltimore Sun coverage
Traffic and commuting news Subscribe to this feed
Michael Dresser's Getting There column Subscribe to this feed
Michael Dresser How-Tos

How to avoid Delaware traveling north
Obscure third route between Baltimore, D.C.
Better routes for I-95 north
How to avoid the Bay Bridge
Find cheaper gas
Check prices at area gas stations by ZIP code and find the lowest rates in the region with our new interactive gas map.

Baltimore-area lowest gas prices
Historical gas price charts
Sign up for FREE local news alerts
Get free Sun alerts sent to your mobile phone.*
Get free Baltimore Sun mobile alerts
Sign up for local news text alerts

Returning user? Update preferences.
Sign up for more Sun text alerts
*Standard message and data rates apply. Click here for Frequently Asked Questions.
  • Breaking News newsletter
When a big news event breaks, we'll e-mail you the basics with links to up-to-date details.
Sign up

Charm City Current
Traffic Resources
Baltimore Metropolitan Council (Regional transportation planning)
Maryland Department of Transportation (State transportation policy)
Maryland Transit Administration (Buses, light rail, Metro, Mobility)
State Highway Administration (Maintains numbered routes)
Motor Vehicle Administration (Licenses, permits, rules of the road)
Maryland Transportation Authority (Toll bridges, tunnels and highways)
Maryland Aviation Administration (BWI and Martin Airport)
AAA Daily Fuel Gauge Report (Track Maryland average gas prices.)
MarylandGasPrices.com (Find the lowest and highest prices.)
SafeRoadMaps (Find out where the crashes happen.)
Roads to the Future (Scott M. Kozel on Mid-Atlantic infrastructure.)
WMATA (Washington metropolitan buses and Metro)
Metropolitan Washington Council of Governments (D.C. regional planning)
U.S. Department of Transportation (federal transportation policy)
Stay connected