Metro Rail Traffic Controller Error/Miscommunication Incidents Since 2012

The Federal Transit Administration incidents since 2012 where rail traffic controller errors or miscommunication between rail traffic controllers and train operators resulted in trains being directed into work zones, through red signals or where power was unintentionally restored in a work zone.

  • March 6, 2012: D& G Junction – Rail traffic controller routed a train into an active work zone.
  • April 24, 2012: Rosslyn – The first car of a six-car consist derailed at a switch just after the Rail Operations Control Center instructed the operator to pass a red signal and traverse the switch, which was not clamped.
  • Oct. 31, 2012: East Falls Church – Rail traffic controller sent a prime mover into a work area after authorizing the work crew to enter the right-of-way.
  • Nov. 7, 2012: Landover – Rail traffic controller restored power to an area with roadway workers present.
  • Jan. 30, 2013: Anacostia – Self-evacuation of stranded passengers from a train resulting from miscommunication.
  • May 13, 2013: Red signal violation by Train 713 related to miscommunication.
  • May 28, 2013: Red signal violation by Train 923 related to miscommunication.
  • Aug. 7, 2013: Third rail power energized in a work area.
  • Aug. 15, 2013: Rail buggy derailed when Rail Operations Control Center failed to confirm that it had cleared an interlocking and threw a switch.
  • Oct. 14, 2013: Collision in West Falls Church service and inspection shop when train operator was not informed that a pair of cars of the train in motion had brakes cut out, and the operator thus was unable to stop the train in time.
  • Jan. 11, 2014: Rail traffic controller instructed a train operator to offload a train that was not fully berthed at the platform.
  • Sept. 17, 2014: Rail Operations Control Center permitted a prime mover to enter a work zone.
  • Dec. 29, 2014: Near miss involving workers in the right-of-way at King Street Station.
Contact Us