Jump to content

WMATA Washington


DCAreaTransitFan

Recommended Posts

Collision of two out of service trains happened earlier this morning between Foggy Bottom and Farragut West stations. I heard they’re all 3000 Series with cars 3008/3009, 3120/3121, and 3206/3207 were involved. Unknown damaged as of right now but Blue/Orange/Silver lines affected all day today. 
 

Also Orion VII 2718 is at CET yard showing on transsee. Either it’s retired or will go under maintenance but most likely going to be retired. 

Link to comment
Share on other sites

6 hours ago, DCTransitFilms said:

Collision of two out of service trains happened earlier this morning between Foggy Bottom and Farragut West stations. I heard they’re all 3000 Series with cars 3008/3009, 3120/3121, and 3206/3207 were involved. Unknown damaged as of right now but Blue/Orange/Silver lines affected all day today. 

So here’s how it follows: 3141-3140-3121-3120-3206-3207 was the stationary train (Train 755), while the striking train (Train 700) was cars 3008-3009-3010-3011-3019-3018. 3008 ended up striking 3207 and 3008 has significant damage. It’s most likely both 3008-3009 and 3206-3207 are going to be written off as I heard it was major damage especially on 3008. Trains are still single tracking between Foggy Bottom and McPherson Sq as of right now. 

B1DB4191-E5C4-4F1D-BCFB-2AAFED7487E1.png

Link to comment
Share on other sites

6 hours ago, DCTransitFilms said:

So here’s how it follows: 3141-3140-3121-3120-3206-3207 was the stationary train (Train 755), while the striking train (Train 700) was cars 3008-3009-3010-3011-3019-3018. 3008 ended up striking 3207 and 3008 has significant damage. It’s most likely both 3008-3009 and 3206-3207 are going to be written off as I heard it was major damage especially on 3008. Trains are still single tracking between Foggy Bottom and McPherson Sq as of right now. 

B1DB4191-E5C4-4F1D-BCFB-2AAFED7487E1.png

It could be that they put 3009 and 3207 together, if 3008 and 3206 are damaged beyond repair. Anyway, I'm glad nobody was seriously hurt, because the 3Ks aren't that solidly built. 

Speaking of Metro Rail, I'm wondering when we'll hear an update about the 8000 Series procurement. The bids for that contract were supposedly submitted a few months ago. I know one complicating factor is the federal opposition to CRRC bidding on US contracts (although currently, none of the proposed legislation on this subject has been signed into law). 

Link to comment
Share on other sites

13 minutes ago, WMATAC40LF said:

It could be that they put 3009 and 3207 together, if 3008 and 3206 are damaged beyond repair. Anyway, I'm glad nobody was seriously hurt, because the 3Ks aren't that solidly built. 

Speaking of Metro Rail, I'm wondering when we'll hear an update about the 8000 Series procurement. The bids for that contract were supposedly submitted a few months ago. I know one complicating factor is the federal opposition to CRRC bidding on US contracts (although currently, none of the proposed legislation has been signed into law). 

I don’t believe WMATA will do that since the 3000 series cars are already slanted for retirement in 2023 so there wouldn’t be a point of keeping them into service but who knows. 
 

Also idk about the 8000 Series railcars yet hopefully not China but I’m hoping at least Alstom. 

Link to comment
Share on other sites

4 hours ago, DCTransitFilms said:

I don’t believe WMATA will do that since the 3000 series cars are already slanted for retirement in 2023 so there wouldn’t be a point of keeping them into service but who knows. 
 

Also idk about the 8000 Series railcars yet hopefully not China but I’m hoping at least Alstom. 

I suspect the 3Ks will linger around until at least 2025, based on the delays with the 8K procurement. As for what will be repaired, it usually comes down to how much damage was done. If its anything major, repairs probably don't make sense (and if the carbody structure has failed, repairs may not even be possible). However, if the drawbars and couplers are the only things that need replacing, some of these cars may eventually be returned to service. 

I think Alstom is the best option for the 8000s. Hyundai Rotem has had issues with some of their other US contracts, and there are obviously a bunch of concerns surrounding CRRC.  

  • Like 1
Link to comment
Share on other sites

On 10/8/2019 at 1:37 AM, WMATAC40LF said:

I suspect the 3Ks will linger around until at least 2025, based on the delays with the 8K procurement. As for what will be repaired, it usually comes down to how much damage was done. If its anything major, repairs probably don't make sense (and if the carbody structure has failed, repairs may not even be possible). However, if the drawbars and couplers are the only things that need replacing, some of these cars may eventually be returned to service. 

I think Alstom is the best option for the 8000s. Hyundai Rotem has had issues with some of their other US contracts, and there are obviously a bunch of concerns surrounding CRRC.  

I do think 3140/3141, 3120/3121, and 3010/3011 will be repaired idk about the rest though. Ik 3008 suffered major damage (saw twitter pics) with one of the handrails being bent. But 3009 and 3206 can easily be mate together but idk if WMATA will do that because of the age. Also yeah the 3ks might be around until 2025 and Alstom is most likely the best bet as CRRC has concerns and Hyundai is having problems. 

Also there’s some pictures on twitter of the collision and it shows 3008 suffering major damage with its handrail being bent really badly. It looks like it’ll be a write off but as of right now the damage is unknown. All the cars involved in the collision are currently at Brentwood Yard undergoing more investigation and checking if the cars can be repaired (3140/3141, 3120/3121 had their couplers broken). Here’s a link of the pics: https://mobile.twitter.com/MetrorailSafety/status/1182038843882639360

 

here are also pics of the interior of 3008 (from the link provided above)

49724A7D-368E-4C80-9170-32CA550F52C5.png

553E9886-2FAF-496B-95A8-94F44B47EDB5.png

A3AB2DE8-9558-47F8-BCA4-3A0714539328.png

  • Like 1
Link to comment
Share on other sites

4 hours ago, DCTransitFilms said:

I do think 3140/3141, 3120/3121, and 3010/3011 will be repaired idk about the rest though. Ik 3008 suffered major damage (saw twitter pics) with one of the handrails being bent. But 3009 and 3206 can easily be mate together but idk if WMATA will do that because of the age. Also yeah the 3ks might be around until 2025 and Alstom is most likely the best bet as CRRC has concerns and Hyundai is having problems. 

Also there’s some pictures on twitter of the collision and it shows 3008 suffering major damage with its handrail being bent really badly. It looks like it’ll be a write off but as of right now the damage is unknown. All the cars involved in the collision are currently at Brentwood Yard undergoing more investigation and checking if the cars can be repaired (3140/3141, 3120/3121 had their couplers broken). Here’s a link of the pics: https://mobile.twitter.com/MetrorailSafety/status/1182038843882639360

 

here are also pics of the interior of 3008 (from the link provided above)

49724A7D-368E-4C80-9170-32CA550F52C5.png

553E9886-2FAF-496B-95A8-94F44B47EDB5.png

A3AB2DE8-9558-47F8-BCA4-3A0714539328.png

Yep, stuff popping out like that is never a good sign. Unsurprisingly, the interior damage is very close to where the carbody bolster connects to the center portion of the railcar.

The following image tells us all we need to know about 3008... The monocoque body buckled, so its a write off. We'll see what happens to the others.

Screen Shot 2019-10-10 at 2.09.37 AM.png

  • Like 1
Link to comment
Share on other sites

6 hours ago, WMATAC40LF said:

Yep, stuff popping out like that is never a good sign. Unsurprisingly, the interior damage is very close to where the carbody bolster connects to the center portion of the railcar.

The following image tells us all we need to know about 3008... The monocoque body buckled, so its a write off. We'll see what happens to the others.

Screen Shot 2019-10-10 at 2.09.37 AM.png

Yeah 3008 will be retired for sure, idk about 3207 yet haven’t seen damaged from it yet

  • Like 1
Link to comment
Share on other sites

On 10/8/2019 at 1:37 AM, WMATAC40LF said:

I suspect the 3Ks will linger around until at least 2025, based on the delays with the 8K procurement. As for what will be repaired, it usually comes down to how much damage was done. If its anything major, repairs probably don't make sense (and if the carbody structure has failed, repairs may not even be possible). However, if the drawbars and couplers are the only things that need replacing, some of these cars may eventually be returned to service. 

I think Alstom is the best option for the 8000s. Hyundai Rotem has had issues with some of their other US contracts, and there are obviously a bunch of concerns surrounding CRRC.  

Kawasaki is also always an option. As for the 3000 series cars in that wreck, I don't see why Metro would even both repairing cars that have at most 5 years left on them anyway.... 

 

I don't see the 2000s and 3000s staying pass 2024 tbh.

 

 

In other news, DASH bus has 14 new buses on order for next year. 3 more XD35s, 4 XD40s, 3 XE40s and 4 XE35s. Most of the remaining Orion Vs will be gone by the end of next year. I believe that farther down the line, DASH may also get XE60 artics too to replace the ex Bee line Neos.

13 hours ago, DCTransitFilms said:

I do think 3140/3141, 3120/3121, and 3010/3011 will be repaired idk about the rest though. Ik 3008 suffered major damage (saw twitter pics) with one of the handrails being bent. But 3009 and 3206 can easily be mate together but idk if WMATA will do that because of the age. Also yeah the 3ks might be around until 2025 and Alstom is most likely the best bet as CRRC has concerns and Hyundai is having problems. 

Also there’s some pictures on twitter of the collision and it shows 3008 suffering major damage with its handrail being bent really badly. It looks like it’ll be a write off but as of right now the damage is unknown. All the cars involved in the collision are currently at Brentwood Yard undergoing more investigation and checking if the cars can be repaired (3140/3141, 3120/3121 had their couplers broken). Here’s a link of the pics: https://mobile.twitter.com/MetrorailSafety/status/1182038843882639360

 

here are also pics of the interior of 3008 (from the link provided above)

49724A7D-368E-4C80-9170-32CA550F52C5.png

553E9886-2FAF-496B-95A8-94F44B47EDB5.png

A3AB2DE8-9558-47F8-BCA4-3A0714539328.png

Does anyone know if WMATA retired any more 2000 Orion Vs since the new XD40s came into service?

Link to comment
Share on other sites

52 minutes ago, Chris.A said:

Most of the remaining Orion Vs will be gone by the end of next year.

Since you mention it, I was told there will be 5 Orion 5s in service once all is said and done (No word on the order breakdown). As with every retirement plan though, this is subject to change so. Very exciting times ahead for DASH at least in the electric bus department and thank god they're off the gillig train...

 

Link to comment
Share on other sites

56 minutes ago, Chris H said:

Now that the King St. station reconstruction is complete, does DASH use those Neoplan artics on regular fixed routes?

I haven’t noticed but I haven’t really seen them around in service. I think Dash only got them for that one time for the platform reconstruction.

Link to comment
Share on other sites

15 hours ago, Chris.A said:

Kawasaki is also always an option. As for the 3000 series cars in that wreck, I don't see why Metro would even both repairing cars that have at most 5 years left on them anyway.... 

 

I don't see the 2000s and 3000s staying pass 2024 tbh.

 

 

In other news, DASH bus has 14 new buses on order for next year. 3 more XD35s, 4 XD40s, 3 XE40s and 4 XE35s. Most of the remaining Orion Vs will be gone by the end of next year. I believe that farther down the line, DASH may also get XE60 artics too to replace the ex Bee line Neos.

Kawasaki apparently wants to exit the railcar market (at least certainly the North American market), because it isn't terribly profitable. They aren't one of three builders who are reportedly interested in the 8K contract.

Regarding the 2000s and 3000s, I suspect they will hang around for a little while longer than we were initially told. Its now looking like the first 8000s will enter service in 2024 (at the earliest), so unless 200+ subway calls are placed into service that year, the Breda rehabs will probably make it into 2025 or 2026. Additionally, WMATA's decision to add certain components (such as local content requirement) to the 8K contract will probably draw out the delivery and testing timeline even more.

Link to comment
Share on other sites

Also 6195 was on the 42/43 and 6196 was on the J12 it looking like Landover got rid of some D40LFRs unless they were loaned. Also 5488 was operating on the X1 which we finally got the return of tics on the X1. Plus I’m guessing FMR handles some Western blocks as 3162 was on the L1 and 2658 on the M4 yesterday and 2730 on the L1 today. 

Link to comment
Share on other sites

13 hours ago, DCTransitFilms said:

Also 6195 was on the 42/43 and 6196 was on the J12 it looking like Landover got rid of some D40LFRs unless they were loaned. Also 5488 was operating on the X1 which we finally got the return of tics on the X1. Plus I’m guessing FMR handles some Western blocks as 3162 was on the L1 and 2658 on the M4 yesterday and 2730 on the L1 today. 

Yep, on a very quick visit to DC last month, I saw more D40LFRs in the District than ever before -- even rode 6108 on the 96. They're a good fit on busy urban routes!

Yes, the closure of Northern caused quite a ripple effect. A lot more DC service now comes from Montgomery and Four Mile Run. I don't know of any District routes that run entirely out of Four Mile Run, but you're likely to see pieces here and there.

At least in the morning, rush hour in the City is slightly later than the 'burbs due to shorter distances. So if a Four Mile Run bus ends up in DC after finishing a 16Y, there isn't time to deadhead into Virginia for another 3Y or 11Y or 16Y trip. Rush hour will be over. But there is time to deadhead somewhere in the District -- a much shorter movement -- and fire off a "loose" late-peak trip of an L1 or 43.

See the picture. You can tell where the bus lives by the first letter of the block number in the window (AM10, AP61). These two flew in from West Ox via the 38B. "A" means West Ox (they carried it over from the old Arlington division which West Ox replaced). The other letters are self-explanatory (except "P" which means Southern -- maybe representative of Prince George's?) ...

WMATA_BlockNumber.jpg

Link to comment
Share on other sites

2 hours ago, Border City Transit said:

Yep, on a very quick visit to DC last month, I saw more D40LFRs in the District than ever before -- even rode 6108 on the 96. They're a good fit on busy urban routes!

Yes, the closure of Northern caused quite a ripple effect. A lot more DC service now comes from Montgomery and Four Mile Run. I don't know of any District routes that run entirely out of Four Mile Run, but you're likely to see pieces here and there.

At least in the morning, rush hour in the City is slightly later than the 'burbs due to shorter distances. So if a Four Mile Run bus ends up in DC after finishing a 16Y, there isn't time to deadhead into Virginia for another 3Y or 11Y or 16Y trip. Rush hour will be over. But there is time to deadhead somewhere in the District -- a much shorter movement -- and fire off a "loose" late-peak trip of an L1 or 43.

See the picture. You can tell where the bus lives by the first letter of the block number in the window (AM10, AP61). These two flew in from West Ox via the 38B. "A" means West Ox (they carried it over from the old Arlington division which West Ox replaced). The other letters are self-explanatory (except "P" which means Southern -- maybe representative of Prince George's?) ...

WMATA_BlockNumber.jpg

Ah thanks for the help for the block numbers. And I guess you're right with the FMR buses running with Western Routes or other routes. That's why we gotten some XN40s or Orion VII on the L1 and M4 and E4 lately. Plus D40LFRs are all over the place with most running in DC now probably of capacity reasons and shortages on buses since the D40LFRs were supposed to be at MD garages. But last few years we had them held at Western, Northern, Blade, FMR, and West Ox. Now D40LFRs are at Southern Ave, Montgomery, Shepherd Parkway, Blade, and Landover. Probably some more will move to Western since 6195 is running the 42 right now but I really don't know why D40LFRs are all over the place and don't know why they're moving all over the place.

Link to comment
Share on other sites

On 10/14/2019 at 1:46 PM, vvozz said:

Hello , does anyone know is the bus operators at the contracted bus garage wear the same Metrobus uniforms as Union bus operators ?

I actually don’t know haven’t been on those contracted buses yet but I assume they do. I might be wrong though.

Also guys I made a new Twitter account that tracks bus movements in the DC system. It’s called @ DCBusMovements and it’ll showcase news from WMATA & bus movements from WMATA. 

96737302-5F39-46E2-B451-002A8147C0F6.png

Link to comment
Share on other sites

On 10/21/2019 at 8:59 AM, DCTransitFilms said:

Western took a hold of D40LFRs 6173 and 6192-6204. Probably there more D40LFRs that moved there too.

Saw a number of Orion VII OG CNGs yesterday around Northern VA. I actually road bus #2717 on the 22C and boy did that bring back memorizes of the good old days. Also, DASH Orion V #85 is still active despite rumors of it being retired. Also saw 2007 C40LFR #2825 on the 7Y yesterday. Nice to see non XN40s out of FMR.

 

 

BTW Orion Vs #2122 and #2123 are most likely no longer at FMR.  

  • Like 1
Link to comment
Share on other sites

Also Transdev is in huge trouble now. Every Route from Cinder Bed is currently not operating due to a strike most likely. This affects the 17s, 18s, 29s, REX, and TAGs buses.

3BEC16CE-D132-43F2-9100-D76C4082C6F2.png

4F12B319-7A02-498A-B9A5-5FECB79CF294.png

I wouldn't be surprised if WMATA decided to get back the rights from Transdev due to the employee strike, DE40LFAs breaking down, and other contributions that leads to this. 

Link to comment
Share on other sites

3 hours ago, DCTransitFilms said:

Also Transdev is in huge trouble now. Every Route from Cinder Bed is currently not operating due to a strike most likely. This affects the 17s, 18s, 29s, REX, and TAGs buses.

3BEC16CE-D132-43F2-9100-D76C4082C6F2.png

4F12B319-7A02-498A-B9A5-5FECB79CF294.png

I wouldn't be surprised if WMATA decided to get back the rights from Transdev due to the employee strike, DE40LFAs breaking down, and other contributions that leads to this. 

It's just as I thought. I knew this was going to happen eventually, because NICE bus (which is also managed by these guys) have been trying to go on strike for the past year due to similarly bad conditions. I wonder if Four Mile Run, West Ox, and Sheppard's Parkway could help out with Cinder Bed's Rushhour lines until things get back on track (if they ever do)?

14 minutes ago, DCTransitFilms said:

Also a DE40LFA got into an accident last night and flipped upside down. Unknown number as of right now but this happened along Suitland Parkway.

 

 

How in the Blue hell did this even happen!?!? You think it's a Sheppard's Parkway bus?

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...