Preliminary Report: 8/12/18 – Unscheduled Train Departure from Vienna

On Sunday, August 12, 2018, there was an unscheduled Orange Line train departure from Vienna en route to Foggy Bottom at 2:21PM EST. The following is a summary of events related to that departure.

At 1:47PM, Vienna terminal operations instructed a supervisor to bring a gap train stored in the tail tracks at Vienna to the track 2 platform and keep the doors closed. The supervisor on board was instructed to enter a train ID of 770, which historically identifies a train as having no passengers to the controllers in the Rail Operations Control Center (ROCC).

Train 770 (T-770) opened its doors at 2:06PM, and departed Vienna at 2:21PM, as shown in the image below:

T-770 is shown here as AIMS Train ID 161; it was not a scheduled train departure from Vienna based on WMATA’s public train schedule.

A thorough review of all train departures from Vienna on August 12, 2018 shows T-770 was the only unscheduled revenue departure from Vienna that day.

T-770 serviced every station en route to Foggy Bottom.

This is a preliminary report. All information is subject to change as we learn more.

Rail Transit OPS Group is an independent organization that monitors rail transit operations, performance, and safety procedures to proactively address potential issues. Rail Transit OPS is supported solely from independent contributions by individuals like you. Like us on Facebook and follow us on Twitter.


Preliminary Report: 6/30/18 – Incorrect Routing of Green Line Train

On Saturday, June 30, 2018 at about 6:18 p.m., Washington Metropolitan Area Transit Authority (WMATA) Green Line Train 502 (T-502) headed from Greenbelt to Branch Avenue was incorrectly routed through two switches while in approach to the Fort Totten Metrorail station. The train came to rest in the non-revenue, single-track connector known as the B&E, which links the Red Line to the outbound Green Line.

The train operator of T-502 reversed operating ends of the train twice in order to move the train from the connector track back to the outbound Green Line track, then cross over to the inbound track where it should have been. This resulted in a 12-minute delay for the train’s passengers.

There were no injuries or damage during the incident. There was also no risk of a collision as, although the routing was incorrect for this particular train, it is a legitimate and viable routing; the Automatic Train Protection (ATP) system is designed to halt any conflicting train movements if any are detected.

Based on the information that is available to us, we believe the probable cause of this incident is human error on the part of both the train operator of T-502 and the Rail Operations Control Center (ROCC) staff.

The operator of T-502 failed to properly scan the tracks ahead and identify the first incorrect switch setting, which allowed the train to cross over from Track 2 (the inbound track) to Track 1 (the outbound track) on the Green Line. The second switch took the train from Track 1 to the B&E (connector track). These switches are protected by signals E06-08 (which protects movement from Track 2 to Track 1 under normal train traffic) and E06-52 (which protects movement from Track 1 to the B&E), respectively.

Both signals identified above should have been showing a ‘flashing lunar’ aspect, i.e. a white flashing light indicating that the switch is aligned for a diverging route to the other track. Additionally, the operator should have recognized that the speed commands being sent to their train indicated a reduced top speed of 28 MPH before the first switch; this speed is one of a small subset indicative of a impending crossover move, which could have alerted the operator to the incorrect routing. The operator of T-502 should have stopped the train upon seeing the flashing lunar at E06-08 and contacted the ROCC.

It is unclear why the switches were aligned for the movement T-502 took, as no trains utilized that route immediately prior to T-502. The ROCC controller should have identified earlier that the signal E06-52 was showing a proceed indication, which would be an unusual occurrence during normal operations.

Images below are from our partner DCMetroHero displaying the movements of Train 502 into the B&E Connector

Rail Transit OPS Group is an independent organization that monitors rail transit operations, performance, and safety procedures to proactively address potential issues. Rail Transit OPS is supported solely from independent contributions by individuals like you. Like us on Facebook and follow us on Twitter.

Business Changes Effective July 1st, 2018

First off, we would like to thank each and every one of you for your support over the past two and a half years. You, the riding public, have been very generous with your time and donations, allowing us to stay focused on our mission: providing you information.

After careful review, we’ve decided to officially adjust our business operations according to our current availability, financial position, and ridership trends. It is our expectation that the vast majority of you will not notice any changes, however we’ve detailed a summary of what to expect below:

  • Monitoring of WMATA Metrorail on Mondays and Fridays will generally be reduced, especially outside of AM and PM rush hours, e.g. mid-days and nights.
  • Weekend monitoring of WMATA Metrorail will change from continuous monitoring to incident monitoring, i.e. we will only commit to investigating moderate or major incidents in real time after notification from riders or automated MetroHero Alerts.
  • Monitoring of MARC and VRE will be discontinued until further notice.
  • Field audits will be suspended from July 1st thru September 15th, and we will not commit to conducting audits when the outside temperature is below 40 degrees or above 90 degrees. (This will allow us to more generally monitor WMATA Metrorail more efficiently, especially during weather extremes.)
  • We will begin publishing periodic reports to the public on the data we collect during our operations.

These changes will take effect July 1st, 2018. Altogether, we will be monitoring WMATA Metrorail operations an average of 30 hours per week, and will continue to review incidents as soon as we become aware of them. We expect this to bring our total monthly expenses to about $725, or $36.25 per business day. For context, we currently collect about $180/month via Patreon, which only includes subscriptions and not other generous one-time donations made via other payment services.

As always, we are open to suggestions via email at You can also message us on Facebook and Twitter. Remember: we are 100% funded by folks like you. If you find our services useful and would like to donate, please click here. Thank you again for your continued support!

The Rail Transit OPS Team

Preliminary Report: 6/5/18 – WMATA Red Line Incident at Forest Glen Station

This is a preliminary review and as such is subject to change as our review continues.

At about 5:05pm EDT on Tuesday, June 5, 2018, Glenmont-bound Red Line Train 133, consisting of six 3000-series cars, experienced a separation of a roof-mounted HVAC access panel (located on the ends) on the lead pair of cars—3213 and 3212—while in approach to Forest Glen station.


Modified image of the top of a 3000-series railcar (not the incident train). The top HVAC access panel has been outlined in red. Original image: Flickr/Bossi

At about 5:13pm, Glenmont-bound Red Line Train 152, also consisting of six 3000-series cars, made contact with this panel while in approach to Forest Glen station, resulting in smoke as the panel made contact with the electrified third rail.

Red Line trains single-tracked between Silver Spring and Forest Glen from 5:14pm to 9:23pm. Outbound service was disrupted at the beginning of the incident from 5:14pm to 5:51pm.

There were no reported injuries. Six rail cars sustained minor damage, while one sustained moderate damage.

Rail Transit OPS Group is an independent organization that monitors rail transit operations, performance, and safety procedures to proactively address potential issues. Rail Transit OPS is supported solely from independent contributions by individuals like you. Like us on Facebook and follow us on Twitter.

Preliminary Report: 5/31/18 – WMATA Red Line Service Suspension Due to Arcing Insulator

Washington Metropolitan Area Transit Authority (WMATA) Red Line train service was suspended between Farragut North and Gallery Place on Thursday, May 31 from approximately 10:15 a.m. until 10:48 a.m. after a train operator reported seeing fire on the trackbed.

At 10:09 a.m., the operator of 6-car Train 153 (T-153) en route from Metro Center to Farragut North in the direction of Shady Grove stopped approximately 2,100 feet outside of Metro Center and reported seeing a fire on the roadway. The train operator then requested permission to utilize a fire extinguisher to put it out. Upon hearing the report, the Rail Operations Control Center (ROCC) Rail Traffic Controller (RTC) called for several rail supervisors, instructing them to head towards the location of the reported fire.

The operator of T-153 was instructed at 10:10 a.m. to shut off the environmental (EV) system on the train—HVAC—and then instructed to reverse ends on the train. This would allow the operator to move the train back towards Metro Center.

WMATA ROCC suspended Red Line service at 10:15 a.m. and began holding trains in preparation to use Gallery Place and Farragut North as temporary terminals. Trains would offload and reverse back in the directions they came from. None would be allowed to pass between Farragut North and Metro Center.

At 10:15 a.m., the operator of T-153 reported to the ROCC that he had reversed ends on the train, and that the fire was now visible from the Glenmont-side operators cab, approximately five feet away. The operator requested to use a fire extinguisher to put out the fire, but was instructed by the ROCC to reverse ends again to the Shady Grove-side operating cab.

As the operator of T-153 was walking through the train, he received a report from a customer that a person had exited the train. Two minutes later at 10:21 a.m., the operator was instructed to consolidate passengers on the train into the lead car, which was the furthest from the reported track fire. The ROCC RTC further instructed the operator to perform a ground walkaround [1] of the train. The operator would be unable to make announcements to passengers on the train while on the ground.

The DC Fire/EMS command post with Battalion Chief 6 was set up outside Metro Center by 10:23 a.m., and WMATA Emergency Response Team (ERT) personnel arrived at Metro Center at 10:26 a.m., 17 minutes after the initial incident report.

At approximately the same time, the operator of T-153 finished their ground walkaround, saw no passengers on the roadway that had exited the train, and was returning to the lead (Shady Grove) car of the train. The operator reported that he saw “light smoke” while performing the ground walkaround.

WMATA ERT was granted permission to walk on the roadway towards the reported location of the fire, 1,600 feet outbound of Metro Center (A2 019+00) at 10:27 a.m., and the ROCC instructed the T-153 operator to apply a handbrake to the lead car of the train in preparation to de-energize the third rail in the incident area.

At 10:32 a.m., T-153’s operator reported that a handbrake had been applied to the lead car of the train (3209), and the ROCC reported at 10:33 a.m. that third rail on the affected track had been de-energized.

At 10:34 a.m., ERT personnel reported that a burnt insulator which previously had been arcing had been removed; permission was given to the ROCC to restore third rail power so that T-153 could be moved to Farragut North.

T-153’s operator reported the handbrake on 3209 was removed at 10:41 a.m., and the train berthed at Farragut North by 10:43 a.m. to continue towards Shady Grove in revenue service.

Rail service on the inbound track from Farragut North to Metro Center was restored at 10:44 a.m., while rail service from Metro Center towards Farragut North was restored at 10:47 a.m.

Notable Events

  • Train 153 was in the tunnel between Metro Center and Farragut North for approximately 34 minutes
  • We believe WMATA ERT personnel removed debris from the trackbed when the burnt insulator was also removed; the debris could have caught fire from arcing on the insulator
  • Passengers aboard T-153 reported smelling smoke while the train was in the tunnel, and reported limited communications from the operator [2]
  • Third rail power remained energized approximately 24 minutes after the start of the incident
  • Intermittent radio issues in the area where T-153 was held caused difficulties in communicating between the train operator, the ROCC, and ERT personnel
  • T-153’s operator spent approximately five minutes outside the train from 10:21 to 10:26 a.m. performing a ground walkaround after a passenger reported a person exiting the train in the tunnel
  • The WMATA ROCC announced that fans in the incident area were activated at approximately 10:15 a.m. (Rail Transit OPS is unable to verify the direction of fan activation)


  • WMATA Red Line service was promptly halted on both tracks in the affected area
  • The operator of T-153 did not clearly identify the location of the train, nor the location of the reported fire when reporting it to the ROCC, both of which caused reversing the train’s direction to take longer than necessary; had the operator of T-153 reported that the train was past the source of fire, the ROCC could have allowed T-153 to continue to Farragut North
  • WMATA ERT personnel did not properly verify that they had permission from the WMATA ROCC before beginning their work to remove the defective insulator
  • Communications and coordination between the ROCC and the Metro Transit Police Department (MTPD) appeared to be poorly executed and organized
    • MTPD personnel were not dispatched to respond to the incident until 10:21 a.m., 12 minutes after it was reported to the ROCC
    • MTPD officers had not confirmed until approximately 10:31 a.m. that there was a train (T-153) in the tunnel between Metro Center and Farragut North in the area affected by the reported track fire

[1] A ground walkaround is when an operator exits a train and physically walks around all sides of the train while on the roadway. This procedure is part of the Standard Operating Procedure (SOP) before a train leaves a rail yard to be put into revenue service, or when an Emergency Door Release (EDR) is broken.


This is a preliminary incident report, and information is subject to change.


Rail Transit OPS Group is an independent, publicly-funded organization that monitors rail transit operations, performance, and safety procedures to proactively address potential issues. Like us on Facebook and follow us on Twitter.