- Date
- June 22, 2009
- Location
- United States
- Industry
- Transportation
- Access vector
- Not applicable
- OT targeting
- None
- Primary peril
- Collision / Derailment
- Impact duration
- 15 to 16 years of manual operation
Washington DC Metro Red Line train collision, 2009

The incident path, stage by stage
Each stage of the attack, from intent to financial loss, with this incident’s path highlighted. Solid cells are confirmed, dashed cells are reported by a source but not confirmed, dotted cells are implied by the facts, and Unknown marks what is not publicly known. Click a stage title or a highlighted cell to read that part of the analysis.
Scroll sideways to see every stage.
On this page
Highlights
What happened. At about 4:58 p.m. on June 22, 2009, Metrorail train 112 struck the rear of standing train 214 near Fort Totten station on the Red Line in Washington, DC. The National Transportation Safety Board (NTSB) found that a failure of track circuit modules made the automatic train control system lose detection of the standing train and keep sending speed commands to the train behind it. Nine people aboard train 112 were killed[1].
Why it matters. There was no attacker: this was an accidental failure of a control system, carried here as a reference point for what such a failure can cost. NTSB found that a test for this failure had existed since two 2005 near-collisions but was not used systemwide, and the operator then ran every train in manual mode for 15 to 16 years[1][2][3].
About this analysis. This analysis sets out what is known, stage by stage. The NTSB report text reachable for it stops partway through its analysis, so figures known only from secondary accounts of NTSB’s findings are left out. This account reflects the best available information as of October 22, 2026; new information could confirm, change or discredit parts of it.
Highlights
- NTSB found that track circuit B2-304 reported the track as vacant while train 214 stood on it, so the control system kept sending speed commands to train 112 up to the point of impact[1].
- Nine people were killed, 52 were taken to hospitals and about 90 were triaged and treated at the scene, according to NTSB[1].
- After two near-collisions in 2005, the Washington Metropolitan Area Transit Authority (WMATA) developed a test for this kind of failure. NTSB found it had not been institutionalized and used systemwide[1].
- WMATA directed all trains to run in manual mode. Automatic operation returned on the Red Line in December 2024 and on the last lines in June 2025[1][2][3].
Attack flow
- Updated: 2026-10-22
- Intent: Accidental [confirmed]
- Threat actors: Not applicable [not in path | Accidental event, no attacker]
- Access vector: Not applicable [not in path | No intrusion]
- IT impact: Not in path [not in path | No IT system involved]
- OT targeting: Not applicable [not in path | No attacker]
- OT sophistication: Not applicable [not in path | No attacker]
- OT impact: Loss / Denial of Control [confirmed | Equipment failure, per NTSB]
- Perils: Collision / Derailment [primary]
- Financial losses: Assets & Equipment [confirmed | $12M est., NTSB]; Health, Safety, Casualty [confirmed]; Business Interruption [confirmed]; Cyber-Physical Incident Response [confirmed]; Cyber Incident Response [implied]; Reputation Damage [implied]
What happened
The collision happened inside a 738-foot track circuit designated B2-304, one of the circuits that tell the automatic train control (ATC) system whether a train is on a stretch of track[1]. NTSB, as reported by The Washington Post, said the circuit had “functioned irregularly since December 2007”[4]. On June 16 and 17, 2009, a new transmitter impedance bond was installed in it[1].
NTSB found parasitic oscillation in the track-circuit transmitter, which made the circuit report the track as vacant while train 214 stood on it. The control system lost detection of train 214 and kept sending speed commands to train 112; commands of 55 mph, the segment’s top speed, resumed to train 112 at 4:57:20. Eight passengers in the lead car of train 112 and its operator were killed, and the lead car lost about 63 feet, or 84 percent, of its occupant survival space[1].
On June 25, Metro’s general manager, John B. Catoe Jr., ordered all of the system’s roughly 3,000 signal circuits on 106 miles of track inspected[5]. On September 22, NTSB issued an urgent recommendation telling WMATA to examine its track circuits for parasitic oscillation, and from late October to late December 2009 technicians tested 1,482 circuits and found 208 with the same type of oscillation[1]. WMATA directed that all trains be operated in manual mode “for an indefinite period”[1]. Automatic operation returned on the Red Line on December 15, 2024[2][6], on the Green and Yellow Lines in May 2025[7], and on the Blue, Orange and Silver Lines on June 15, 2025[3]. By February 2012, Metro had settled seven of nine wrongful-death lawsuits, on terms that were not disclosed[8].
Intent: accidental
No attacker, cyberattack or malicious act of any kind is documented in any source reviewed. NTSB’s probable cause has two parts: a failure of the track circuit modules, built by GRS/Alstom Signaling, and WMATA’s failure to make sure that an enhanced track circuit verification test was institutionalized and used systemwide[1]. The path therefore starts at Accidental. The event is carried in this library because the failure was in a control system, and its losses are a reference point for what a loss of train detection can cost, whatever its cause.
Threat actors: none
There was no attacker, and no source suggests one[1]. What NTSB found at fault was equipment and an organization: the track circuit modules failed, and WMATA had not propagated a test it had itself developed[1]. Alstom, Ansaldo and ARINC later settled with Metro and, according to The Daily Record, “acknowledged legal responsibility for the crash along with Metro”[8]. No threat actor is highlighted on the map.
Access vector: not applicable
No intrusion of any kind took place. Nothing reached the train control system from outside: the fault arose in the track circuit itself, whose transmitter impedance bond had been replaced on June 16 and 17, days before the crash[1]. NTSB describes a hardware and maintenance defect, not malicious code or commands, and no source suggests any other route. This stage is marked not applicable on the map.
IT impact: not in the path
No IT system is implicated. NTSB’s investigation describes no server, network device, workstation or software compromise; the causal chain runs through a field device that reports whether track is occupied[1]. The stage is marked Not in path, and the flow on the map passes through it without touching any IT technique.
OT targeting: not applicable
The failure was inside the train control system, in the track circuit that detects whether a train is present[1], but nothing was aimed at it. With no attacker there is no targeting, and the stage is shown as not applicable. This analysis classifies the event by what failed and what followed, not by anyone’s intent.
OT sophistication: not applicable
There was no attacker to be crude or sophisticated. What NTSB describes is a latent defect: parasitic oscillation that made a circuit report a section as vacant while a train stood on it. The same type of oscillation was found in 208 of 1,482 circuits tested later in 2009[1], so the defect was spread across the system rather than confined to one circuit.
OT impact: loss of control, by failure
The track circuit reported an occupied section as vacant, and the ATC system kept sending speed commands to the following train up to the point of impact[1]. The system meant to keep the trains apart depended on that train-detection circuit, and no independent collision protection is described. The effect is shown as Loss / Denial of Control, confirmed by NTSB, with the caution that it came from an equipment failure, not from anyone acting on the system.
Perils: collision
The primary peril is collision: train 112 struck the rear of train 214[1]. No source reports fire, derailment or any other peril following it, and the crush of the lead car is collision damage. NTSB had recommended in 2006 that WMATA retire its 1000-series railcars faster or retrofit them for crashworthiness. All six cars of train 112 were 1000-series cars, and NTSB estimated their body could fail in a collision at 11.6 to 14.8 mph[1].
One circuit that reported an occupied track as empty was enough to put one train into the back of another.
Financial losses: two figures, and years of manual operation
NTSB gives two figures: about $12 million in damage to train equipment, and WMATA’s estimate of about $5,000 in track and appurtenance damage[1]. Nothing else is quantified. The wrongful-death settlements were not disclosed[8], no fine or civil penalty is disclosed, and the largest consequence, 15 to 16 years of manual train operation across the system, has never been costed.
Loss evidence
- Confirmed: Property damage (train equipment and track); Manual operations and workarounds; Cyber-physical event response (mass-casualty emergency response); Bodily injury; Loss of life; Medical liability (wrongful-death settlements); Third-party physical and societal impact (manual operation borne by riders)
- Reported amounts: $12M Damage to train equipment, as estimated in NTSB’s report[1]; $5,000 Track and appurtenance damage, as estimated by WMATA, according to NTSB[1]
- Implied: Lost revenue and productivity; Asset degradation; Equipment repair and replacement; Process safety engineering; Safety regulation liability; Legally mandated improvements; Public relations response
- Not supported: Network device replacement; Server replacement; Computer and laptop replacement; Embedded device replacement; Industry regulation liability; Ransom extortion
NTSB also found an ineffective safety culture at WMATA and inadequate oversight by the Tri-State Oversight Committee, the WMATA Board of Directors and the Federal Transit Administration[1]. NTSB has no penalty authority, and its recommendations are not legal mandates.
What this incident shows
The fix existed before the crash. After two near-collisions in 2005 caused by a loss of train detection, WMATA developed an enhanced track circuit verification test and issued technical bulletins requiring it, yet none of the WMATA technicians NTSB interviewed was familiar with it. NTSB found that the test, used systemwide, would have identified the faulty circuit before the accident[1].
The defect was also spread across the system, in 208 of 1,482 circuits tested in late 2009[1], and an assessment of every device sharing that latent failure mode could plausibly have found it earlier. Once trust in the control system was lost, restoring it took years: WMATA did not return automatic operation to its last lines until June 2025, and an operator still stays in the cab[3][2].
References
- National Transportation Safety Board. “Collision of Two Washington Metropolitan Area Transit Authority Metrorail Trains Near Fort Totten Station, Washington, D.C., June 22, 2009.” Railroad Accident Report NTSB/RAR-10/02, adopted 27 July 2010, reissued 8 Apr. 2026. ntsb.gov/investigations/AccidentReports/Reports/RAR1002.pdf
- WMATA. “Metro to begin Automatic Train Operation for the first time in 15 years.” News release, 12 Dec. 2024. wmata.com/about/news/Metro-to-begin-Automatic-Train-Operation-for-the-first-time-in-15-years.cfm
- “Metro’s Blue, Orange and Silver lines start running on automatic train operation.” NBC4 Washington, 15 June 2025. nbcwashington.com/news/local/transportation/metro-extends-automatic-train-operation-to-blue-orange-and-silver-lines/3937002/
- “Circuit at Metro Crash Site Began Malfunctioning in Late ’07, NTSB Says.” The Washington Post, 23 July 2009. washingtonpost.com/wp-dyn/content/article/2009/07/23/AR2009072301575.html
- “Metro orders inspection of signal circuit.” The Washington Times, 26 June 2009. washingtontimes.com/news/2009/jun/26/metro-orders-inspection-of-signal-circuit/
- “Metro resumes automatic train operations on Red Line after 15 years.” FOX 5 DC, 15 Dec. 2024. fox5dc.com/news/metro-resumes-automatic-train-operations-red-line-after-15-years
- “Metro gets approval to expand automation to Green and Yellow Lines.” WTOP, May 2025. wtop.com/tracking-metro-24-7/2025/05/metro-gets-approval-to-expand-automation-to-green-and-yellow-lines/
- “Metro settles most death suits from 2009 train crash.” The Daily Record (Maryland), 15 Feb. 2012. thedailyrecord.com/2012/02/15/metro-settles-most-death-suits-from-2009-train-crash/


