June 2009 Washington Metro train collision

Coordinates: 38°57′37″N 77°0′21″W / 38.96028°N 77.00583°W / 38.96028; -77.00583
This is a good article. Click here for more information.
Source: Wikipedia, the free encyclopedia.

June 2009 Washington Metro train collision
Northeast, Washington, D.C.
Coordinates38°57′37″N 77°0′21″W / 38.96028°N 77.00583°W / 38.96028; -77.00583
CountryUnited States
LineRed Line
OperatorWashington Metropolitan Area Transit Authority
Incident typeTrain collision/telescoping
CauseTrack circuit malfunction
Statistics
Trains2 (2 six-car trains)
Deaths9 (including a train operator)
InjuredApproximately 80

During the afternoon

Northeast, Washington, D.C.
, United States. A moving train collided with a train stopped ahead of it; the train operator along with eight passengers died, and 80 people were injured, making it the deadliest crash in the history of the Washington Metro.

The National Transportation Safety Board (NTSB) investigation found that after a June 17 replacement of a track circuit component at what became the crash site, the track circuit had been suffering from parasitic oscillations which left it unable to reliably report when that stretch of track was occupied by a train. The struck train came to a stop because of traffic ahead. Because the entire train was within the faulty circuit, it became invisible to the Automatic Train Control (ATC) system. The train behind it was therefore commanded to proceed at 55 mph (89 km/h). The operator of the striking train applied the emergency brake after the stopped train came into full view, but there was not enough time to prevent the collision, which occurred at approximately 49 mph (79 km/h).[1]

Collision

Aerial view of emergency responders at the crash
NTSB and recovery teams working in the night following the collision

At approximately 4:57 pm EDT (20:57 UTC) on Monday, June 22, 2009, Washington Metro Train 112, bound from

operator in the lead car of the moving train, Jeanice McMillan, 42, of Springfield, Virginia;[7] at least 80 people were injured. The death toll makes the crash the deadliest in Metro history.[7][8][9][10][11]

The NTSB found that Train 214 had come to a stop entirely within the faulty circuit B2-304, making it effectively invisible to the automatic train control (ATC) system. Other trains had received speed commands of 0 when traveling through this circuit, but had enough forward momentum to make it to the next circuit and resume detection and receipt of speed commands from the ATC system. Train 214 was going slower than normal because it was being driven in manual mode by its operator, and it came to a stop while remaining on circuit B2-304 and was therefore invisible. Train 112 behind it was given full speed (55 mph [89 km/h]) commands by the ATC to proceed on the track. The investigation found that the emergency brakes had been applied by the operator of train 112 when train 214 came into view but it was too late to avert the collision, which occurred with a speed of about 49 mph (79 km/h).[1]

A series of near-collisions in 2005 in similar circumstances in the tunnel between Foggy Bottom and Rosslyn stations led to a new test procedure which would have identified the faulty circuit after installation. However, by 2009, Metro engineers were unaware of this incident or the tests developed to detect the failure condition.[1]

Rolling stock involved

Car 5066 following the collision being investigated by the NTSB. This car was retired by WMATA and was used as a source of spare parts along with 5067 until all the 5000-series railcars were pulled from service in late 2018.

Train 112 (the moving train) was made up of cars 1079, 1078, 1071, 1070, 1130 and 1131—all from the

Automatic Train Control, which allow autonomous operation with little human intervention.[12]

After the collision, WMATA announced a policy of no longer placing the 1000-series at the end of trainsets to prevent telescoping in a collision, as they were the weakest cars structurally.[13] All 1000-series cars were then put in the middle of trainsets and served for another eight years until their retirement in June 2017.[citation needed]

Cars 5066 and 5067 were never repaired and were used for spare parts until all the 5000-series railcars were retired in 2018.[14] 1078 was also retired following the collision.[citation needed]

Response

At 5:20 pm, rescuers first entered car 1079, the lead car of train 112.

telescoped over the rear car of the stationary train, trapping many passengers who required rescue by emergency workers using ladders for access.[4] Survivors described the crash as "like... hit[ting] a concrete wall," with air clouded by smoke and debris, and panic among passengers when car doors did not immediately open.[15]

Dennis Oglesby, a United States Army soldier, and Martin Griffith, an Army contractor and former Army soldier, who were in the lead train and were uninjured in the collision, helped passengers evacuate from their train, most of whom appeared to have minor injuries. Oglesby and Griffith then noticed that six to eight people from the other train had been ejected by the force of the collision and were more seriously injured. One person from the overtaking train had been thrown onto the roof of the stationary train and had suffered a severe head wound. Oglesby and Martin gave first aid to the more seriously injured victims until help arrived, and informed responding emergency personnel that the rails were still powered and needed to be shut down.[16]

Rhode Island Avenue–Brentwood
station on the evening of the collision

Immediately following the collision,

Takoma Metro station, and arrived at the location of the collision soon after. D.C. Fire Chief Dennis Rubin stated that the initial 9-1-1 emergency calls made the incident seem small, but after firefighters arrived on scene, they dispatched mass casualty incident teams. Within two hours, more than 200 firefighters were on-scene in response to the three-alarm incident.[17] Rescuers worked through the night of June 22, using cranes and heavy rescue equipment to free trapped passengers and search for bodies.[7][18]

Fire Chief Dennis Rubin initially confirmed four fatalities (including the train operator) and 74 injuries, 14 of which were considered moderate and 6

fighter jets to defend Washington, D.C. during the September 11 attacks – died in the collision along with his wife, Ann; the other passengers who died in the crash were Lavonda King, Veronica DuBose, Cameron Williams, Dennis Hawkins, Mary Doolittle, and Ana Fernandez.[20]

According to Daniel Kaniewski, a former George W. Bush administration Homeland Security official now with the Homeland Security Policy Institute at George Washington University, the overall emergency response was "calm and ordered," indicating that U.S. emergency response "during extraordinary incidents [has] significantly improved" since the September 11 attacks.[21]

Service disruption

Delays continued on the Red Line the day after the collision, the "earlier situation" referred to on the Passenger Information Display System sign.
Clean up recovery of the wrecked cars following the collision. Red Line service was suspended between Fort Totten and Silver Spring until Saturday June 27.

Immediately following the incident, Red Line services were suspended between the

Washington Metropolitan Area to remote work on June 23 if possible.[23][24] The Red Line was projected to be very crowded after resumption of service and the Washington Metropolitan Area Transit Authority (WMATA) advised people to take alternate bus routes. The replacement bus shuttle between the affected stations was expected to be subjected to long delays.[25]

Services were restored in both directions on Saturday, June 27, but with a reduced maximum speed of 35 mph (56 km/h) on the entire Red Line, and slower speeds in the area of the collision.[26]

Aftermath

Initial inquiry

Fort Totten

Shortly after the incident, WMATA General Manager John Catoe stated that the cause was not known but that "the system is safe."[27] The National Transportation Safety Board (NTSB) began an investigation.[7] WMATA and NTSB investigators considered several possible causes, which might include operator error, brake failure, fault in the computerized signal and operation system, or a combination of the three. During rush hour operation, train movement is typically controlled by a centralized computer system, and a separate decentralized system can automatically apply the brakes to prevent a collision. These systems had failed at least once in the past, and the NTSB subsequently identified incompatible specifications, from the maximum deceleration capability of the trains to the deceleration rates used in the wayside system design.[28][29][30] The train has a manual emergency brake, which can be applied by the driver in the event of an imminent collision, if the driver can see and identify the hazard with sufficient time to stop. Officials indicated that the manual brake was indeed engaged.[31] It is possible that the brake system failed to perform as designed, or that the operator applied the brake too late.[32] The lead car of the moving train was two months overdue for scheduled brake maintenance.[7] In a press conference the evening of June 22, Catoe stated that the last car on the stopped train was a CAF 5000-Series car (car 5066), which entered service in 2001, and that the lead car on the moving train was a Rohr Industries 1000-Series car. WMATA later confirmed that all of the cars on the moving train were 1000-Series.[5]

A typical 5000-Series car similar to the stopped train in the accident at Branch Avenue Yard

The 1000-Series entered service in 1976 when the Metro system opened, and were refurbished and had their motors converted from DC to AC propulsion by

Woodley Park station in which a 1000-Series Rohr car telescoped into another train.[33] In this case, NTSB's Hersman confirmed that, "the first car [of the striking train] overrode the rear car [of the struck train], and much of the survivable space on that first car of the striking train was compromised".[8] The NTSB called for the accelerated retirement of the 1000-Series cars, or urged that they be "retrofitted with crashworthiness collision protection that is comparable to 6000-Series car railcars."[34] Additionally, the 1000-Series cars lack data recorders that could be used in determining the cause of a crash.[7] During the press conference, Catoe stated that he had "no basis to suspend the use of 1000-Series cars at this time",[33] but WMATA later announced a decision to stop using the 1000-Series cars as the lead or trailing units of any trains.[35]

On June 24, WMATA issued a press release stating that the agency is "not likely to know the cause for several weeks or months as the investigation unfolds."[36] Twenty-four hours after the incident, the NTSB confirmed that evidence indicated that the emergency brake had been engaged by the operator. Additionally, the striking train was in automatic mode and so the on-board software should have stopped the train.[37]

Inbound approach to collision site

On June 25, NTSB tests of the 740-foot (230 m) long track circuit below the stopped train showed that it did not work correctly, failing to detect the presence of a test train that investigators had placed on it.[38][39][40] Hersman said, "These circuits are vital. It's a signal system. It's providing information, authorization and speed commands to the following train," but stopped short of blaming them in this case.[31] WMATA had replaced all 20,000 track circuit relays system-wide in 1999, after a component designed to last 70 years began failing after only 25 years in service, but the agency claims that none of the newer relays had failed prior to this event.[7] WMATA ordered the inspection of all track circuits on its 106 miles (171 km) of track after the NTSB test.[35] On July 23, the NTSB announced that the track circuit at the accident site had been malfunctioning since 2007, 18 months prior to the collision, and WMATA has since found six other circuits within the system that have been behaving unusually. WMATA disabled each circuit that could not be immediately fixed and created an online circuit tracking system, similar to its elevator outage tracker.[41]

NTSB report

The

NTSB report on the accident was released on July 27, 2010, and blamed a faulty track circuit, part of the automatic train control system, for causing the crash.[42][43] WMATA made a press release detailing changes on July 26 in anticipation of the release of the report.[44]

Memorials

A plaque that commemorates the victims of the collision at Fort Totten station

A plaque is located in Fort Totten's mezzanine that commemorates the victims of the crash.

On June 22, 2015, the sixth anniversary of the accident, the Legacy Memorial Park in honor of the victims was opened;

Mayor Vincent C. Gray.[47] The park features a memorial wall and nine inscribed sculptures, one in honor of each person who died in the crash. The sculptures were created by sculptor Barbara Liotta, and the memorial was designed by the firm of Hunt Laudi; the design is titled A Sacred Grove.[48][49] Representatives of victims' families and city government officials attended the dedication, but Metro officials did not.[50] The park is located at the entrance to Blair Memorial Gardens, which is close to the site of the collision.[49]

The same week as the memorial dedication, the National Transportation Safety Board held hearings related to another fatal incident in the Metro system that happened earlier in 2015; the juxtaposition of the two events was noted by some commentators.[48][50]

On the third anniversary of the crash, NTSB chairwoman Deborah Hersman and Mayor Gray attended the unveiling of a plaque on the Charles A. Langley Bridge. The bridge crosses the rail tracks at the site of the accident, and a makeshift memorial had been maintained there by victims' families.[51][52] Another memorial plaque was installed by Metro officials at Fort Totten station.[53]

See also

References

  1. ^ a b c NTSB (July 27, 2010). "NTSB Railroad Accident Report: Collision of Two Washington Metropolitan Area Transit Authority Metrorail Trains Near Fort Totten Station" (PDF). Retrieved May 15, 2015.
  2. ^ a b Saslow, Eli (June 28, 2009). "Three Minutes to Fort Totten". The Washington Post. Retrieved June 30, 2009.
  3. ^ Malandain, Lucile; Michael Mathes (June 22, 2009). "Nine dead in Washington metro crash". AFP. Retrieved June 30, 2009.
  4. ^ a b Sullivan, Andy (June 22, 2009). "Four Killed, 70 Injured in Washington Subway Crash". Reuters.
  5. ^ a b c "Tuesday Red Line service altered as a result of Monday collision". Washington Metropolitan Area Transit Authority. Archived from the original on June 26, 2009. Retrieved July 29, 2009.
  6. ^ "Two Red Line Trains Collide, Six Fatalities". www.wmata.com. Archived from the original on June 26, 2009. Retrieved June 21, 2020.
  7. ^ a b c d e f g h i Lena H. Sun; Lyndsey Layton; Debbi Wilgoren (June 23, 2009). "Nine Killed in Red Line Crash". The Washington Post. Retrieved June 23, 2009.
  8. ^ a b c "Investigator: D.C. Metro crash 'a scene of real devastation'". CNN. June 23, 2009. Retrieved June 23, 2009.
  9. NBC Washington
    . June 22, 2009. Retrieved June 22, 2009.
  10. ^ "US subway trains in collision". BBC News. June 22, 2009. Retrieved June 22, 2009.
  11. ^ "2 dead after Metro train derailment, collision". wtop.com. WTOP-FM. June 22, 2009. Retrieved June 22, 2009.
  12. NTSB
    . October 29, 1996. p. 16. Retrieved September 9, 2009.
  13. ^ Thomson, Robert (May 7, 2014). "D.C. streetcar opening still months away, but plans develop for next phase in Anacostia". WashPost. Retrieved May 8, 2014.
  14. ^ WMATA [@wmata] (October 12, 2018). "END OF THE LINE: Today is the last day you'll ride a 5000-series railcar!" (Tweet). Retrieved October 12, 2018 – via Twitter.
  15. ^ Metro crash 'like we hit a concrete wall,' passenger says. CNN. June 23, 2009. Retrieved June 23, 2009.
  16. Military Times
    , August 23, 2009.
  17. ^ "D.C. Fire Chief: Firefighters Expected a 'Small Incident'." The Washington Post. June 23, 2009.
  18. ^ a b Robert Thomson (June 22, 2009). "Rescuers Still Searching Trains". The Washington Post. Retrieved June 23, 2009.
  19. ^ "4 Dead After Metro Trains Collide in Washington D.C." Archived June 25, 2009, at the Wayback Machine Fox News. June 22, 2009.
  20. ^ "Man killed in D.C. Metro crash ordered jets above Capitol on 9/11". CNN. June 23, 2009. Retrieved June 27, 2009.
  21. ^ Dave Cook (June 23, 2009). "Emergency response to Metrorail crash shows post-9/11 gains". The Christian Science Monitor. Retrieved June 23, 2009.
  22. ^ "2 Dead, Many Injured in Red Line Train Collision". ABC7 News. June 22, 2009. Archived from the original on June 24, 2009. Retrieved June 22, 2009.
  23. ^ "After Crash, Feds Urge Telework." The Washington Post. June 23, 2009.
  24. ^ "Morning Commute Will Be Tough For Many." The Washington Post. June 23, 2009.
  25. ^ "Wednesday Red Line service altered as a result of Monday collision". Washington Metropolitan Area Transit Authority. June 24, 2009. Archived from the original on June 27, 2009. Retrieved June 27, 2009.
  26. ^ "Red Line resumes normal operations after Monday collision". About Metro. Washington Metropolitan Area Transit Authority. June 27, 2009. Archived from the original on June 28, 2009. Retrieved June 27, 2009.
  27. ^ D.C. Metro Trains Collide, Killing Four. The Wall Street Journal. June 22, 2009
  28. ^ Layton, Lindsey (June 23, 2009). "THE PROBE: Experts Suspect Failure Of Signal System, Operator Error". The Washington Post. Archived from the original on August 17, 2009. Retrieved June 23, 2009.
  29. ^ Layton, Lindsey (June 14, 2005). "Trouble in Tunnel Delaying Subway". The Washington Post. Retrieved June 22, 2009.
  30. ^ "NTSB: Train's Emergency Brake Was On". Fox Television Stations, Inc. June 23, 2009. Archived from the original on August 25, 2009. Retrieved June 23, 2009.
  31. ^ a b Layton, Lyndsey; Glod, Maria; Sun, Lena H. (June 24, 2009). "Probe Finds Metro Control 'Anomalies': Investigators Test Electronics Near the Scene Of Fatal Crash". The Washington Post. Archived from the original on June 1, 2010. Retrieved June 27, 2009.
  32. ^ Layton, Lindsey. "Experts Suspect Failure Of Signal System, Operator Error." The Washington Post. June 23, 2009. Retrieved June 23, 2009.
  33. ^ a b DeBonis, Mike. "Old Questions About Crashworthiness of Metro Cars." Washington City Paper. June 22, 2009. Retrieved June 22, 2009.
  34. ^ NTSB (March 23, 2006). "NTSB Determines that the Operator's Failure to Apply Brakes Caused Washington Subway Collision in 2004". National Transportation Safety Board. Archived from the original on September 3, 2009. Retrieved June 23, 2009.
  35. ^ a b "Metro orders inspection of signal circuit". Washington Times. June 26, 2009. Retrieved June 28, 2009.
  36. ^ "Wednesday Red Line service altered as a result of Monday collision". Washington Metropolitan Area Transit Authority. Archived from the original on June 27, 2009. Retrieved July 29, 2009.
  37. ^ Sun, Lena H. (June 24, 2009). "Train Operator Apparently Hit Brakes Before Crash". The Washington Post. Archived from the original on June 1, 2010. Retrieved June 24, 2009.
  38. ^ Keane, Angela (June 25, 2009). "Track Circuit in Metro Crash Didn't Work, NTSB Says". Bloomberg.
  39. ^ Stout, David (July 2, 2009). "Equipment Was Repaired Days Before Train Crash". The New York Times. Retrieved July 2, 2009.
  40. ^ "Source: Metro circuits were malfunctioning for five days". Frederick News-Post. June 26, 2009. Archived from the original on June 27, 2009. Retrieved July 2, 2009.
  41. ^ Sun, Lena H.; Layton, Lyndsey (July 24, 2009). "Circuit at Metro Crash Site Began Malfunctioning in Late '07, NTSB says". The Washington Post. Archived from the original on August 22, 2010. Retrieved July 29, 2009.
  42. ^ "Fatal Washington Metro Crash Shows Need for U.S. Transit Rules, NTSB Says". Bloomberg. July 27, 2010. Retrieved July 28, 2010.
  43. ^ "July 27, 2010 Railroad Accident Report – Collision of Two Washington Metropolitan Area Transit Authority Metrorail Trains Near Fort Totten Station Washington, D.C. June 22, 2009". NTSB. July 27, 2010. Retrieved April 10, 2012.
  44. ^ "Metro demonstrates safety commitment, compliance with NTSB recommendations, including replacement of 1000 series rail cars". WMATA. July 26, 2010. Archived from the original on July 14, 2012. Retrieved July 7, 2015.
  45. ^ "Legacy Memorial Park Honoring 2009 Metro Accident Victims to Open Monday". dc.gov.
  46. ^ Stephanie Ramirez/WUSA 9 Staff (June 22, 2015). "Legacy Memorial Park honors victims killed in 2009 Metro crash". WUSA9. Retrieved September 10, 2015.
  47. ^ "Legacy Memorial Park Project". dc.gov. Retrieved September 10, 2015.
  48. ^ a b "At Legacy Memorial Park, A Community Remembers Victims of 2009 Metro Collision". DCist. Archived from the original on November 5, 2017. Retrieved September 10, 2015.
  49. ^ a b "Metro Memorial Park finally coming together five years after tragedy". Washington Business Journal. March 26, 2014. Retrieved September 10, 2015.
  50. ^ a b "Memorial Park To Red Line Victims Opens As NTSB Hearings Into Metro Death Begin". WAMU 88.5. Retrieved September 10, 2015.
  51. ^ "Metro Crash Memorial Plaque Presented at Fort Totten Station 3 Years After Metro Rail Crash". wusa9.com. Retrieved September 10, 2015.[permanent dead link]
  52. ^ "Gray to unveil Fort Totten Metro crash memorial plaque but no park decision". Washington Examiner. June 20, 2012. Retrieved September 10, 2015.
  53. ^ Sinclair Broadcast Group (June 22, 2012). "2009 Metro Red Line crash memorial unveiled". WJLA. Retrieved September 10, 2015.

Further reading

External links

Wikimedia Commons has media related to June 22, 2009 Washington Metro train collision.
Wikinews has related news:

Retrieved from "https://en.wikipedia.org/w/index.php?title=June_2009_Washington_Metro_train_collision&oldid=1149468323"