• NTSB hearing on Ft. Totten

  • Discussion related to DC area passenger rail services from Northern Virginia to Baltimore, MD. Includes Light Rail and Baltimore Subway.
Discussion related to DC area passenger rail services from Northern Virginia to Baltimore, MD. Includes Light Rail and Baltimore Subway.

Moderators: mtuandrew, therock, Robert Paniagua

  by farecard
 
The Board members are sweating the staff on many many details...as they should.

One detail I caught; Alstrom has many oscillating modules, but none of the competitors seem to.
  by Sand Box John
 
WMATA: NTSB press releases on the 06 22 2009 Fort Totten Wreck

NTSB Issues Updates On Three Washington Metrorail Accident Investigations; Announces Board Meeting Date For 2009 Red Line Collision Investigation In Washington, DC


NTSB Cites Track Circuit Failure And WMATA's Lack Of A Safety Culture In 2009 Fatal Collision
For Immediate Release: July 27, 2010 SB-10-29

Metro Collision Animation from above Board meeting.

Direct download of Collision Animation Window Media Format (21.0 MB WMV file)

Full report will be available on the website in several weeks.
  by Sand Box John
 
"farecard"
One detail I caught; Alstrom has many oscillating modules, but none of the competitors seem to.


That's because the Alstrom (GRS) modules in question are nearly 35 years old.
GRS held the patents on much of the technology, everything after was made under license. The patent have sense run out.
  by farecard
 
Sand Box John wrote:"farecard"
One detail I caught; Alstrom has many oscillating modules, but none of the competitors seem to.


That's because the Alstrom (GRS) modules in question are nearly 35 years old.

That should not matter. A large number of things are over 35, not just me, but many aircraft in the world, lots of locomotives and plenty of railroad gear.

Either:
  • they were well-designed, and stable until failure...
  • they became a trouble item as they aged, due to component aging, etc.
If the latter, Alstrom should have issued recalls on them.
  by farecard
 
A synopsis of the NTSB report, including the probable cause, conclusions and safety recommendations, is available on the NTSB website.

I've yet to find that link......
  by Sand Box John
 
"farecard"
That should not matter. A large number of things are over 35, not just me, but many aircraft in the world, lots of locomotives and plenty of railroad gear.


Those things are scrupulously maintained by their owners and operators. It pretty obvious that WMATA has not been doing the same.

Either:
  • they were well-designed, and stable until failure...
  • they became a trouble item as they aged, due to component aging, etc.


If the latter, Alstrom should have issued recalls on them.


See above.

A synopsis of the NTSB report, including the probable cause, conclusions and safety recommendations, is available on the NTSB website.

I've yet to find that link......


All of the gruesome detail will be in the final report to be released in a few weeks.

In the meantime you can go through the 356 MB in the 327 docket exhibits.
  by farecard
 
http://ntsb.gov/Publictn/2010/RAR1002.htm

CONCLUSIONS

1. The following were neither causal nor contributory to the accident: weather, training and qualifications of the train operators, fatigue, use of alcohol or illegal drugs by the train operators, track structure and rail integrity, and condition and performance of train mechanical equipment.
2. The operator's decision to operate train 214 (the struck train) in manual mode during the evening rush hour period was in violation of Metro rules, but track circuit B2-304 was failing to detect trains, regardless of whether they were operating in manual or automatic mode.
3. Because train 214, which was being operated in manual mode, was traveling at a much slower speed than the authorized speed commands it was receiving, train 214 stopped completely within the faulty B2-304 track circuit when its detection was lost and it received a 0 mph speed command.
4. Because of the design of the Washington Metropolitan Area Transit Authority (WMATA) operations control center information management system and the high number of track circuit failure alarms routinely generated by that system, operations control center controllers could not have been expected to be aware of the impending collision or to warn either train operator.
5. Considering the challenges of the recovery operations, the emergency response was well coordinated and effectively managed.
6. The Metrorail automatic train control system stopped detecting the presence of train 214 (the struck train) in track circuit B2-304, which caused train 214 to stop and also allowed speed commands to be transmitted to train 112 (the striking train) until the collision.
7. Even though the operator of train 112 activated emergency braking before the collision, there was not enough time, once train 214 came into full view, to stop the train and avoid a collision.
8. On the day of the accident, parasitic oscillation in the track circuit modules for track circuit B2-304 was creating a spurious signal that mimicked a valid track circuit signal, thus causing the track circuit to fail to detect the presence of train 214.
9. Spurious signals had been causing the track circuit modules for track circuit B2-304 to erroneously indicate that the track circuit was vacant from the time the track circuit transmitter power was increased after the impedance bond was replaced on June 17, 2009, until the accident 5 days later.
10. Train operators did not report problems with track circuit B2-304 before the accident because reductions in speed commands to maintain train separation, or even momentary losses of all speed commands, were common during train operations.
11. The track circuit modules did not function safely as part of a fail-safe train control system because GRS/Alstom did not provide a maintenance plan that would detect anomalies in the track circuit signal, such as parasitic oscillation, over the modules' service life and prevent these anomalies from being interpreted as valid track circuit signals.
12. Some of the General Railway Signal Company (GRS) track circuit modules in use on the WMATA Metrorail system continue to exhibit parasitic oscillation, and the presence of this oscillation presents an unacceptable risk to Metrorail users.
13. As shown by the fact that (1) the GRS modules in the accident track circuit B2-304 consistently exhibited parasitic oscillation in on-scene and laboratory testing regardless of the type of impedance bond or simulated load used, (2) numerous other Metrorail track circuits that used all GRS components were found to have parasitic oscillation similar to the oscillation found at Fort Totten, and (3) numerous other track circuits with components made by different manufacturers showed no evidence of such oscillation, this accident did not result from WMATA's use of Union Switch & Signal impedance bonds with GRS track circuit modules.
14. The change in transmitter power level necessitated by the installation of a Union Switch & Signal impedance bond in track circuit B2-304 was within the design parameters of the equipment and would not have resulted in a failure of train detection in the absence of parasitic oscillation within the GRS track circuit modules.
15. WMATA failed to institutionalize and employ systemwide the enhanced track circuit verification test developed following the 2005 Rosslyn near-collisions, and this test procedure, had it been formally implemented, would have been sufficient to identify track circuits that could fail in the manner of those at Rosslyn and Fort Totten.
16. If proper shunt placements had been used, as required by WMATA's procedures, to verify track circuit B2-304 either immediately after the new impedance bond was installed on June 17, 2009, or when the track circuit was tested the following day, the work crews would have been able to determine that the track circuit was failing to detect trains, and actions could have been taken to resolve the problem and prevent the accident.
17. A technician following the manufacturer-provided GRS track circuit module maintenance procedures would not have detected the spurious signals that caused track circuit B2-304 to fail in an unsafe manner.
18. WMATA Metrorail automatic train control test procedure T163, developed since this accident, will permit technicians to detect the presence of parasitic oscillation like that found in the failed track circuit modules at Fort Totten; however, unless these procedures are carried out on a periodic basis, an unsafe condition may persist for some time before being discovered and corrected.
19. A comprehensive safety analysis of an automatic train control system must consider all foreseeable system failures that may result in a loss of train separation, including failures in train detection caused by track circuit failures.
20. WMATA did not effectively distribute technical bulletins and safety information to its automatic train control technicians nor did it ensure that the information was received, understood, and properly acted upon by those technicians.
21. WMATA failed to recognize that the near-collisions at Rosslyn in 2005 represented an unacceptable hazard that had not been considered in the fail-safe design of the automatic train control system, and WMATA failed to communicate that hazard to the affected divisions in the organization for resolution.
22. The Metrorail maintenance communication line system-a system that was in disrepair and was apparently no longer needed by WMATA-could allow unanticipated signal paths that could degrade the integrity, and thus the safety, of the Metrorail automatic train control system.
23. As revealed by postaccident testing, the cables serving the impedance bonds for track circuit B2-304 did not meet proposed WMATA Metrorail standards for insulation resistance, and although this did not cause or contribute to the accident, such deficiencies, if undetected and uncorrected, could undermine the safety of the Metrorail train control system.
24. The structure of the Federal Transit Administration's oversight process leads to inconsistent practices, inadequate standards, and marginal effectiveness with respect to the state safety oversight of rail transit systems in the United States.
25. The results of this investigation, as well as the Federal Transit Administration's audit of the Tri-State Oversight Committee and WMATA, determined that the Tri-State Oversight Committee has been ineffective in providing proper safety oversight of and lacks the necessary authority to properly oversee the WMATA Metrorail system.
26. The results of this investigation and the findings and recommendations contained in the Federal Transit Administration's March 4, 2010, Final Audit Report of its 2009 safety audit of the Tri-State Oversight Committee and WMATA, if implemented, will enhance WMATA Metrorail passenger and employee safety.
27. The low priority that WMATA Metrorail managers placed on addressing malfunctions in the train control system before the accident likely influenced the inadequate response to such malfunctions by automatic train control technicians, operations control center controllers, and train operators.
28. The steps that WMATA has taken since the Fort Totten accident, such as improving and increasing the use of the loss-of-shunt software tool for identifying track circuit malfunctions, will contribute to improving the safety of the system.
29. The safety of transit rail operations would be improved by periodic transit agency review of recorded operational data and non-punitive safety reports, which have been demonstrated to be effective tools for identifying safety problems in other modes of transportation.
30. Based on the results of this investigation and the Federal Transit Administration's recent safety audit, WMATA was not adequately assessing the severity of hazardous risk associated with identified anomalies in its automatic train control system.
31. The WMATA Board of Directors did not exercise oversight responsibility for the system safety of the WMATA system.
32. Before the accident, the WMATA Board of Directors did not seek adequate information about, nor did it demonstrate adequate oversight to address, the number of open corrective action plans from previous Tri-State Oversight Committee and Federal Transit Administration safety audits of WMATA.
33. Before the accident, the position of chief safety officer lacked the necessary resources and authority within the organizational structure of WMATA to adequately identify and address system safety issues, ensure the distribution of safety-critical information throughout the organization, or manage the system safety program plan as required by 49 Code of Federal Regulations Part 659.
34. Shortcomings in WMATA's internal communications, in its recognition of hazards, its assessment of risk from those hazards, and its implementation of corrective actions are all evidence of an ineffective safety culture within the organization.
35. Previous attempts at non-regulatory oversight failed to compel WMATA to maintain the organizational structure necessary to ensure effective identification and communication of safety-critical information throughout its Metrorail operations.
36. The FTA's lack of toxicological specimen authority prevents transit agencies from collecting pertinent information for determining the circumstances of transit accidents.
37. The structural design of the 1000-series railcars offers little occupant protection against a catastrophic loss of occupant survival space in a collision, and the continued use of these cars in revenue service constitutes an unacceptable risk to WMATA Metrorail users.
38. WMATA's practice of bellying the 1000-series cars does not provide appreciable crashworthiness benefits and is not an acceptable substitute for removing the cars from service.
39. The lack of onboard event recording capability on the striking train prevented a definitive determination of train performance, the status of the onboard systems, and the operator's actions before the collision.
40. Because WMATA does not have a program to monitor the performance of onboard event recorders or to ensure that they are functioning properly, these devices cannot be relied upon by WMATA to provide data that can be used for accident investigations or for equipment or operations monitoring and maintenance.
  by farecard
 
We'll be talking for months on this, I bet....

To start:

11. The track circuit modules did not function safely as part of a fail-safe train control system because GRS/Alstom did not provide a maintenance plan that would detect anomalies in the track circuit signal, such as parasitic oscillation, over the modules' service life and prevent these anomalies from being interpreted as valid track circuit signals.
12. Some of the General Railway Signal Company (GRS) track circuit modules in use on the WMATA Metrorail system continue to exhibit parasitic oscillation, and the presence of this oscillation presents an unacceptable risk to Metrorail users.
13. As shown by the fact that (1) the GRS modules in the accident track circuit B2-304 consistently exhibited parasitic oscillation in on-scene and laboratory testing regardless of the type of impedance bond or simulated load used, (2) numerous other Metrorail track circuits that used all GRS components were found to have parasitic oscillation similar to the oscillation found at Fort Totten, and (3) numerous other track circuits with components made by different manufacturers showed no evidence of such oscillation, this accident did not result from WMATA's use of Union Switch & Signal impedance bonds with GRS track circuit modules.
This to me is the key indictment of GRS. GRS PR/legal folks seemed to building a Maginot Line defense that if only bad bad WMATA had not mixed brands, all would be well. It appears that was not the case...

As NTSB knows well, seldom does one failure cause a disaster like this. The parasitic oscillation alone would not have doomed 112 if there had not been the coupling through the rack panel. One thing I don't see mentioned. If a given block's receiver and transmitter are physically located at different places, i.e. the transmitter in one equipment room, the receiver in one at the far end of the block; this could not have occurred. But that's a VERY expensive solution to what should be a straightforward engineering issue: dependable track modules.

Such modules are hardly rocket science: it's audio frequency, with good levels [i.e not microvolts], lots of space, good power budgets, and reasonable environment [save S/S's equipment flood a few years ago...]. Further, there's little price pressure. Contrast such to a iPad or cellphone design; space, power, environment are all very limiting, and it better cost 0.01c in million unit production quantities, or it will not sell as well as BRAND X's.

One thing bound to come out in the civil suits: When did GRS et.al first know they would oscillate, and who did they tell?
  by farecard
 
31. The WMATA Board of Directors did not exercise oversight responsibility for the system safety of the WMATA system.
I do not think I have ever heard so direct & pointed NTSB indictment as they delivered yesterday. If you were watching the webcast, the final minutes were a Member suggesting a rewording to make it even more clear.

Did any WMATA Board members attend yesterday?
  by Trackrunner
 
farecard wrote:

12. Some of the General Railway Signal Company (GRS) track circuit modules in use on the WMATA Metrorail system continue to exhibit parasitic oscillation, and the presence of this oscillation presents an unacceptable risk to Metrorail users.
So have they removed all this "faulty" equipment? Is WMATA the only agency with this equipment.. I think quite a few in the North East (Ex: Boston, Philadelphia) have GRS equipment. Would it not be a potential hazard?
  by farecard
 
34. Shortcomings in WMATA's internal communications, in its recognition of hazards, its assessment of risk from those hazards, and its implementation of corrective actions are all evidence of an ineffective safety culture within the organization.
There's irony that this report comes out midst the Gulf BP disaster. Decades ago, I worked for a pipeline subsidiary of BP. They really embraced the safety program, with money, support and culture. No one went out of the building without a hardhat; even if the supervisor was gone, your coworkers would give you hell about it. Anyone could shut down a job with a safety report. But, I talked to a friend who just retired from there. It is now 180 degrees out; everything is skimp, hurry, make-do. Guess what happens? People die.

WMATA's Board and staff have a major effort in front of them, unless they plan to just blow it off yet again.
  by farecard
 
Trackrunner wrote:
So have they removed all this "faulty" equipment? Is WMATA the only agency with this equipment.. I think quite a few in the North East (Ex: Boston, Philadelphia) have GRS equipment. Would it not be a potential hazard?
Other systems were listed. NTSB recommend all be pulled. But I doubt there are sufficient replacements to be had on short notice, especially since I bet GRS won't be high on the recommended supplier list.
Code: Select all
# To Massachusetts Bay Transportation Authority, Southeastern Pennsylvania Transportation Authority, Greater Cleveland Regional Transit Authority, Metropolitan Atlanta Regional Transportation Authority, Los Angeles County Metropolitan Transportation Authority, and Chicago Transit Authority:
# Work with Alstom Signaling Inc. to establish periodic inspection and maintenance procedures to examine all GRS audio frequency track circuit modules to identify and remove from service any modules that exhibit pulse-type parasitic oscillation. 
The immediate response is to go test for oscillating modules; and replace/fix those. WMATA already knows where theirs are.
  by farecard
 
# Completely remove the unnecessary Metrorail wayside maintenance communication system to eliminate its potential for interfering with the proper functioning of the train control system.
I've heard little re: this. Is this the phones at the Emergency Power Off ("Blue Light") stations, or something else {as I suspect..}
  by walt
 
Maybe we should step back a minute and consider a couple of things-- first, it is clear that WMATA has issues regarding its oversight, partcularly where safety is concerned. It is also clear that they will now be forced to address these issues as they never have before. Second, maybe we should question just how much "high tech" is really necessary to operate an efficient and safe rapid transit system. I must note that the older systems, ie New York, Philly, and Boston, whose systems were built long before the advent of automatic or computer operated train control systems seemed to operate quite safely-- accidents of any kind on those systems were minimal considering the train miles operated and the extremely close headways on some of those lines. This is not to say that there were no accidents. but there did not seem to be the kind of problems that we have seen with Metro recently, and these systems were completely manually operated with the 60 plus year old block signalling system as their method for seperating trains. ( I do not recall ever, in 20 years living in the Philly area, during the PTC ( private ownership)days ever hearing about a rear end collision like the one involved here on the Market Frankford Subway Elevated or the Broad Street Subway system. And portions of the MFSE are now 103 years old). This is not a put down of the "modern" systems or a suggestion that we return, somehow, to the "good old days", but it is food for some thought as we move forward.
  by farecard
 
walt wrote:. Second, maybe we should question just how much "high tech" is really necessary to operate an efficient and safe rapid transit system. I must note that the older systems, ie New York, Philly, and Boston, whose systems were built long before the advent of automatic or computer operated train control systems seemed to operate quite safely-- accidents of any kind on those systems were minimal considering the train miles operated and the extremely close headways on some of those lines.
WMATA is layered. The base level [think ISO 0] is bog-standard AC block signaling, as used since BEFORE the Cubbies last won a World Series. That is exactly what failed.

Everything else is downstream of that.