Where There’s Smoke, There’s Delays on the Red Line
It hasn’t been a good week for Farragut North on the Red Line. Just a day Four days after a debris fire on the Glenmont-bound tracks caused delays and single-tracking Monday Friday morning, we now have reports of smoke this morning at the same station, causing yet more single-tracking on the Shady Grove tracks between Judiciary Square and Dupont Circle, which is practically all of the Downtown segment of the Red Line.
(Don’t worry, Metro’s going to hire a contractor! He’ll save us!)
Watch WMATA’s advisories page for the situation. Anyone reading get stuck down there? Post a comment when you get back up into the daylight.
Update: I have just emerged from Dupont Circle, and the Red Line appears to be running normally again. Yay!
Update: I must have been stuck in some sort of temporal anomaly, because I thought the first fire was yesterday, when it was actually last Friday. Sorry, DC, and sorry, space-time continuum. I will try harder not to make your heads ache with my poor grasp of fourth dimension awareness.
There apparently was a fire at Farragut North.
http://www.flickr.com/photos/38786049@N00/374568684/
We were delayed half an hour or so due to “single tracking.”
Channel 4 reports:
“A Metro spokeswoman said an insulator joint on the electrified third rail caused the problem, which temporarily caused Metro to single-track trains between Farragut North and the Judiciary Square station. …
“Fire department apparatus also blocked portions of Connecticut Avenue, NBC4 traffic specialist Tonya Bennett reported.
“The problem was first reported around 9:10 a.m. and a Metro spokeswoman said it was resolved within an hour.”
ANOTHER fire? At about 10 am Wednesday morning, there were delays on the Red Line due to “an emergency situation” at Farragut North. My train eventually proceeded through Farragut North without stopping, only letting us out at Dupont Circle.
NBC says it’s a track fire. (Again?) Or are the confusing Tuesday’s emergency with Wednesday’s?