Tuesday, January 14, 2020 Service Events

Summary of events that occur during our active monitoring of rail operations on Metro. Majority of listed events fail to impact service to the level where they require a social media post from us, however they do show what’s occurring on the system. Page is refreshed every 20 minutes during active monitoring

Support Our Operations

7:35A Monitoring Start

7:46A Largo Train 418 instructed to skip Morgan Blvd

7:49A Car 3060 on Silver Train 607 experiencing propulsion surges

7:50A Shady Grove Train 116 reported possible bodily fluids in car 7144

8:04A Intermittent Radio outages system-wide, restored around 8:25A

8:53A Monitoring Ended

4:06P New Carrollton Train 906 held at Eastern Market for MTPD response for disorderly juveniles

4:10P Huntington Train 310 reports sick passenger in car 7058 while crossing Potomac River bridge – pax report no pulse 4:12 – No signs of life 4:13 –

4:15P Huntington Train 310 Offloaded at Pentagon

4:15P Greenbelt Train 305 rerouted to Arlington Cemetery

4:18P OPS3 instructs Supervisor at L’Enfant Plaza to instruct passengers to go downstairs and use Blue line trains to reach VA – No announcement from OPS2

4:19P OPS2 announces single tracking via inbound Track 1 at Arlington Cemetery & Pentagon

4:22P OPS1 announces single tracking from Mt. Vernon Sq <> Pentagon City on Yellow Line

4:22P Arlington FD EMS on site at Train 310

4:23P Report of bodily fluids on car 3223 on Largo Train 614 – car isolated 4:36P

4:23P Gap Train 735 placed in service at National Airport towards Huntington – departs 4:34

4:25P Train Control Tech 2378 preparing to enter trackbed at inbound switches at L’Enfant Plaza to remove clamps from switch 1 to allow single tracking – clamps removed 4:28P

4:28P Glenmont Train 121 reports motor overload on car 6163, remove at Glenmont

4:31P Train Control Techs 2378 instructed to move to Mt. Vernon Sq

4:32P Huntington Train 311 instructed to leave Archives and hold short of switch 1 at L’Enfant Plaza

4:34P Arlington EMS departed Pentagon at 4:30, awaiting ME

4:37P Franconia Train 410 rerouted to Huntington

4:39P L’Enfant Plaza switch 1 indicating out of alignment, Train Control Techs instructed to manually align switch 1 for a crossover movement from the outbound to inbound track for Train 311- instructed to lock the switch in a normal traffic position at 4:42P – Train 311 instructed to proceed to L’Enfant Plaza platform 2 at 4:46 after holding 14 mins

Break in monitoring from 4:52P <> 5:46P

5:50P Car 7480 isolated on Greenbelt Train 302 for bodily fluids

6:12P Restricted Speed for trains servicing Judiciary Square for passenger with medical concerns

8:08P Greenbelt Train 509 request EMS for unresponsive passenger at Southern Av on car 7554 – Single tracking via Outbound Track 2 at Southern Av & Naylor Rd

8:24P PGFD EMS on site at Southern Av

8:35P Non Revenue Train 710 (from Pentagon incident) cleared to depart National Airport pocket track enroute to Greenbelt Yard

8:37P Passenger removed from 7554 by EMS – car 7554 isolated

Advertisement

Monday, January 13, 2020 Service Events

Summary of events that occur during our active monitoring of rail operations on Metro. Majority of listed events fail to impact service to the level where they require a social media post from us, however they do show what’s occurring on the system. Page is refreshed every 20 minutes during active monitoring

Support our Operations

7:34A Branch Av 504 reports unable to close all doors at PG Plaza – cleared

7:40A Vienna Train 908 reports inoperative public address system at Minnesota Av – cleared at 7:54

9:01A Franconia Train 401-3177 reports brakes in emergency at Capitol Heights – cleared by operator

9:06A Shady Grove Train 128 reports a brake system and HVAC warning on car 7288 at Wheaton – tripped circuit breaker

9:16A MTPD response to New Carrollton for fight/assault with weapon, taser deployed

9:19A Report of passenger experiencing a medical emergency on platform at Georgia Av, trains placed on restricted speed

12:42P Branch Av Train 508 reports sparks from Weez bond at ~E2 210

12:44P Huntington Train 304 offloaded at Ft. Totten to serve as Test Train 704

12:45P Greenbelt Train 307 instructed to perform a track inspection from Georgia Av > Ft. Totten – reports clear inspection at 12:47

12:55P Test Train 704 reported a small arcing event ~E2 222

12:57P Inbound track removed from service, single tracking started via Outbound track at Ft. Totten and Georgia Av

12:58P Yellow Line service truncated to Huntington <> Mt. Vernon Sq

1:01P Greenbelt Train 501 instructed to skip Georgia Av

1:02P MTPD & DC Fire Engine 17 on site at Ft. Totten

1:06P Branch Av Train 510 instructed to skip Georgia Av

1:18P ERT 663 (Emergency Response Team) on site at Ft. Totten – arrives at incident area at 1:35 – Enters trackbed at 1:45P (E2 215)

1:38P Branch Av Train 511 instructed to skip Georgia Av

1:51P Third rail power restored Georgia Av <> Ft. Totten on inbound track for ERT inspection

1:56P ERT 663 requests Non Revenue Train 700 as test train on the inbound track following negative stray current of a train passing on the outbound track

2:00P ERT 663 reports no smoke, arcing following the passing of Train 700 & clears track for normal service

2:13P Single tracking concluded and Yellow Line service resumes Huntington <> Greenbelt

Friday, January 10, 2020 Service Events

Summary of events that occur during our active monitoring of rail operations on Metro. Majority of listed events fail to impact service to the level where they require a social media post from us, however they do show what’s occurring on the system. Page is refreshed every 20 minutes during active monitoring

Support our Operations

No events identified during AM rush due to technical difficulties restricting radio communications capabilities

Thursday, January 9, 2020 Service Events

Summary of events that occur during our active monitoring of rail operations on Metro. Majority of listed events fail to impact service to the level where they require a social media post from us, however they do show what’s occurring on the system. Page is refreshed every 20 minutes during active monitoring

Support our Operations

7:19A Glenmont Train 137 reports brake issues at White Flint – 6126 losing brakes off during transition to braking, car maintenance reports good train

7:16A No Destination signs on 3046-47 > Corrected at 7:24A

7:26A Car 3230 Left Headlight inoperative

7:26A Passenger welfare check at Capitol South

7:31A Franconia Train 405 instructed to skip Arlington Cemetery

7:38A Largo Train 609 instructed to skip Morgan Blvd

8:15A Franconia Train 417 instructed to skip Arlington Cemetery

8:29A Vienna Train 912 unable to get a brakes off McPherson Sq – Offloaded

8:28A Greenbelt Train 308 held for MTPD

8:37A Franconia Train 410 instructed to skip Arlington Cemetery

8:45A Shady Grove Train 137 reported hot brakes on car 6126 at Rhode Island Av *see 7:19A entry (pulled from service at 9:36A at Shady Grove)

8:56A Car 7271 on Shady Grove Train 102 propulsion subsystem disabled, train to be removed at Shady Grove

8:58A Vienna Train 914 instructed to skip Dunn Loring

4:29P Franconia Train 412 reports speed control software problems on car 3031 – cleared by rail maintenance at 4:41P

4:40P Speed Restriction (< 15 MPH) in place on outbound platform at Ft. Totten (Lower) due to passenger on platform edge – lifted at 4:44P

5:07P Elevator Entrapment at Court House

5:34P Greenbelt Train 323 reported multiple train control software faults in car 7730 in approach to PG Plaza

5:47P Car 7095 isolated on Largo Train 410 due to presence of bodily fluids

5:59P Bodily Fluids reported on Franconia Train 405 in car 2007 – car isolated by rail maintenance at 6:14 at Braddock Rd

6:07P Franconia Train 415 reported a motor overload and brake odor at Capitol Heights

6:09P Largo Train 410 removed from service at Largo due to intermittent locking brakes

Collision between Train 700 and Train 755 at Farragut West on October 7, 2019

Preliminary Information and subject to change as Rail Transit OPS continues it independent review into this incident

At about 12:50AM, EDT, on Monday, October 7, 2019 Non-Revenue (carrying no passengers) Train 700, a six car train collided with the rear of Non-Revenue Train 755. Both train operators were transported to the hospital and release, and there was damage to multiple railcars in both trains.

On Monday, October 7, 2019, at 12:50AM EDT, the operator of Train 755 consisting of cars 3141-3140-3121-3120-3206-3207, reported a collision from the rear while holding just outside and west of the platform at Farragut West station, within a minute the Rail Operations Control Center (ROCC) instructed the train following Train 755, Train 700 to stop their train, at which time the operator of Train 700 consisting of cars 3008-3009-3010-3011-3019-3018 reported colliding with the train in front. At 1:02AM DC Fire was dispatched to Farragut West for a medical response (Both train operators reported needing medical assistance within 8 minutes of reporting the collision). At 1:05AM DC Fire dispatched a Metro Box alarm for the collision, however the initial location was given as Foggy Bottom station. Metro Transit Police were notified of the collision at 1:04AM. The Washington Metrorail Safety Commission (WMSC) is on-site investigating.

As of 6:00PM all twelve rail cars are still at the incident site, and will remain there through closing. Also Rail Transit OPS Group is continuing to review preliminary data that indicates that Train 700 may have reached a speed upwards of 36 – 40 MPH after departing Foggy Bottom, before coming to a stop, then apparently began moving forward without speed authorization at a speed of less than 15 MPH prior to the collision which occurred on a 1.6% incline and at the end of a five hundred foot long right hand curve. Damage to the rail cars was reported as most extensive between the colliding cars of 3008 and 3207, also there was a report of cars 3140 and 3121 pulling apart at the couplers. The last data we have for Train 700 is that at approximately 12:47:10 Train 700 entered the track circuit roughly 500’ prior to the rear of Train 755. Possible factors include loss of situational awareness by the operator of Train 700, possible medical condition experienced by Train 700 including the possibility of fatigue.

Update: Train 755 began departing the incident location at 1:06AM EDT, October 8, 2019 arriving at Brentwood Rail Yard at 1:34AM. Train 700 departed the incident location at 2:48AM with cars 3008-09 being towed by a diesel power unit arriving at Brentwood yard, and six car train 810 dispatched from West Falls Church Yard was utilized to push the trailing four cars of Train 700 (3010-11-3019-18) from the incident location at 3:40AM to Brentwood Yard as well.

Recommendation 1: To WMATA – During the review it was noticed that multiple trains would utilize the same non-revenue ID (i.e. 700) on different lines. Our recommendation is to split the 700 ID block between each line to avoid confusion, such as in the following example: 700-724 – Red Line; 725-744 – Blue Line; 745-769 – Orange Line; 770-779 – Yellow Line; 780-789 – Green Line; 790-799 – Silver Line

About Us: Rail Transit OPS Group provides independent evaluations of rail transit operations, performance, and safety processes as part of its dual mission: monitor and evaluate rail transit operators’ adherence to these processes, and provide additional information during service disruptions. Rail Transit OPS Group business operations are solely funded by individual contributions from the public. To make a contribution visit our Support Page You can find us on Facebook, Instagram, and Twitter at @RailTransitOPS.