Railroad Forums 

  • 2016 Commuter Rail Delay Discussion Thread

  • Discussion relating to commuter rail, light rail, and subway operations of the MBTA.
Discussion relating to commuter rail, light rail, and subway operations of the MBTA.

Moderators: sery2831, CRail

 #1411834  by StefanW
 
A colleague of mine was put off 408 onto a bus at Belmont. However, 408 right now (9:15 AM) is on the normally-outbound track side-by-side with 406. I expect they are transferring passengers from 406 onto 408.

492 is right behind.

Unless the combined passenger load from 406 + 408 + 492 couldn't squeeze into the consists of 408 & 492 then it was an unfortunate hasty move to put the 408 people on busses as soon as they did.
 #1411836  by StefanW
 
408 will be at Porter in a few minutes. Right now 492 is creeping past 406 on the opposite track as 408 did.
 #1411908  by deathtopumpkins
 
327 died north of Winchester Center. 329 is assisting. T-Alerts predict a 50-60 min delay on 327 and a 25-35 min delay on 329.

Of course this would happen on the first time in ~6 months I ride the Lowell line!I

EDIT: On the move again after 30 minutes. Somewhat surprisingly, we were passed on the other track while stopped by Amtrak 685 and MBTA 331.

Then we passed a stopped train to the left before Anderson/Woburn, whIle another train was across the platform at Woburn itself. I suspect the train across the platform at Woburn is 327. Lights off, multiple conductors standing around the doors.

EDIT 2: Perhaps that was not 327. It just left Anderson heading inbound with passengers on board and lights on in only the first car.
 #1411924  by Trinnau
 
StefanW wrote:A colleague of mine was put off 408 onto a bus at Belmont. However, 408 right now (9:15 AM) is on the normally-outbound track side-by-side with 406. I expect they are transferring passengers from 406 onto 408.

492 is right behind.

Unless the combined passenger load from 406 + 408 + 492 couldn't squeeze into the consists of 408 & 492 then it was an unfortunate hasty move to put the 408 people on busses as soon as they did.
Customers were given the option to get off 408 at Belmont and take MBTA bus service to the red line. At that point it was unknown how long until train traffic could resume by the scene. Luckily with everything pushed away from the tracks they were able to restore service quickly. If that car had been across the other track, however.
 #1412783  by deathtopumpkins
 
Let's see... this morning there was a broken rail in Belmont and in Manchester, and Pan Am signal problems on the Haverhill line.

Apparently at one point there were delays for every line except Fairmount.
 #1416321  by octr202
 
Many issues on everything that isn't the Fitchburg Line up north this morning. 100 was cancelled out of Rockport (mech failure), and it sounds like two dead sets (50%!) at Bradford as well. Unknown whether one of them was healed, or a replacement set was sent up, but 206 appears to be cancelled, with a mixture of putting some people on the Downeaster (Haverhill), and also having 288 turn at Andover to cover there and Ballardvale. No idea what the poor souls at Bradford and Lawrence are supposed to do...
 #1416323  by Diverging Route
 
jaymac wrote:No service alerts as of 0725/01-09-2016, but Boston West was 241ing everything at Crawford.
As a regular 302 passenger, I arrived at Anderson/Woburn to see the a late 301 northbound, and another headlight (that turned out to be PanAm 354 on Track 3). The signals on the north end of the station were flashing on and off irregularly, with all three tracks northbound indicating stop signal. In the distance I could see tail lights of a car near the signal bungalow. 302 arrived about 13 minutes late before resuming normal speed south of Anderson.
  • 1
  • 31
  • 32
  • 33
  • 34
  • 35