2016 Commuter Rail Delay Discussion Thread

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

Moderators: CRail, sery2831

Re: 2016 Commuter Rail Delay Discussion Thread

Postby octr202 » Mon Jan 09, 2017 8:18 am

octr202 wrote: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...


Further updates to the above, from the T'lerts;

-208 made it out of Haverhill in reasonable order, only to die between Bradford and Lawrence. Alerts now say an extra will "assist" it to Boston.

-201 died of unknown causes at Malden outbound. Alerts now say 289 will be used to shove it to Haverhill (and hopefully back again).
Wondering if I'll see the Haverhill double-tracking finished before I retire...
Photo: Melbourne W7 No. 1019 on Route 78, Bridge & Church Streets, Richmond, Victoria. 10/21/2010
User avatar
octr202
 
Posts: 4142
Joined: Fri Mar 12, 2004 8:13 am
Location: In the land of the once and future 73 trackless trolley.

Re: 2016 Commuter Rail Delay Discussion Thread

Postby octr202 » Mon Jan 09, 2017 8:37 am

octr202 wrote:
octr202 wrote: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...


Further updates to the above, from the T'lerts;

-208 made it out of Haverhill in reasonable order, only to die between Bradford and Lawrence. Alerts now say an extra will "assist" it to Boston.

-201 died of unknown causes at Malden outbound. Alerts now say 289 will be used to shove it to Haverhill (and hopefully back again).



And in an update to the update, it now sounds like both 208 and 201 are limping along unassisted now.
Wondering if I'll see the Haverhill double-tracking finished before I retire...
Photo: Melbourne W7 No. 1019 on Route 78, Bridge & Church Streets, Richmond, Victoria. 10/21/2010
User avatar
octr202
 
Posts: 4142
Joined: Fri Mar 12, 2004 8:13 am
Location: In the land of the once and future 73 trackless trolley.

Re: 2016 Commuter Rail Delay Discussion Thread

Postby Diverging Route » Mon Jan 09, 2017 1:05 pm

Dozens of T-Alerts this morning for south side issues, with some delays over an hour. Culprit is "Amtrak signal issues."
User avatar
Diverging Route
 
Posts: 1564
Joined: Sat Mar 13, 2004 3:35 pm

Re: 2016 Commuter Rail Delay Discussion Thread

Postby MBTA F40PH-2C 1050 » Mon Jan 09, 2017 2:52 pm

2017 and its air brake/computer were the issue on 706...messed up the morning rush hour on Franklin Branch. On the Corridor and Mainline, there was a broken rail on Track 2 at Hyde Park and dozens of track circuit issues, and switch problems at TRANSFER Int.
MBTA F40PH-2C 1050
 
Posts: 3498
Joined: Thu Mar 11, 2004 7:57 pm

Re: 2016 Commuter Rail Delay Discussion Thread

Postby Diverging Route » Fri Jan 13, 2017 9:06 am

From T-Alerts, 304 died this morning at Wedgemere and had to be pushed in by 206. That caused rippling delays to 306, 307 and 312.
User avatar
Diverging Route
 
Posts: 1564
Joined: Sat Mar 13, 2004 3:35 pm

Re: 2016 Commuter Rail Delay Discussion Thread

Postby leviramsey » Thu Jan 19, 2017 8:41 am

410 (don't know the locomotive number) lost its HEP in Shirley. Also was stuck in the station for maybe 10 minutes.
leviramsey
 
Posts: 325
Joined: Mon Aug 31, 2015 12:12 pm

Re: 2016 Commuter Rail Delay Discussion Thread

Postby EdSchweppe » Thu Jan 19, 2017 1:06 pm

And before 410 ran into problems, 406 crapped out, which meant that 408 picked up 406's passengers:
Fitchburg Update: Train 406's passengers will deboard at Ayer due to a mechanical issue. Train 408 will pick up passengers.

https://twitter.com/MBTA_CR/status/822062012654096385

492 was sent off from Littleton early, while 408 poked along behind making all local stops:
Fitchburg Line: Train 492 is currently about 5 min ahead of schedule. Train 408 will make local stops to accommodate Train 406's passengers.

https://twitter.com/MBTA_CR/status/822067126332694529

Net result: 408 was 39 minutes late at North Station. Not a good start to the day.
EdSchweppe
 
Posts: 86
Joined: Fri Aug 20, 2004 9:51 pm

Re: 2016 Commuter Rail Delay Discussion Thread

Postby Rbts Stn » Sat Jan 21, 2017 11:10 am

Here's a new one:

Needham Line notice:Train 1604 (10:00 am from Needham Heights) is at capacity. Consider Train 1606 (12:00 pm inbound)


I guess they didn't know there was something going on in town today?
User avatar
Rbts Stn
 
Posts: 589
Joined: Thu Feb 09, 2012 2:09 pm
Location: waiting for an "A" train to Watertown

Re: 2016 Commuter Rail Delay Discussion Thread

Postby EdSchweppe » Sat Jan 21, 2017 9:46 pm

Rbts Stn wrote:Here's a new one:

Needham Line notice:Train 1604 (10:00 am from Needham Heights) is at capacity. Consider Train 1606 (12:00 pm inbound)


I guess they didn't know there was something going on in town today?


That march ended up a lot bigger than anyone had originally planned. From the Globe website:
Protesters headed to the Boston Women’s March on Boston Common Saturday morning overwhelmed parts of the MBTA subway and commuter rail, which ran extra trains in the morning to offset delays, and then ramped up to weeknight rush-hour service in the afternoon.

"It was equivalent to a Boston College football game and a Red Sox game hitting at the same moment, and it was bigger than anything we see typically on July 4 or New Year’s Eve,”"said MBTA Chief Administrator and Acting General Manager Brian Shortsleeve at an afternoon press conference. "The MBTA was all hands on deck."

Transit officials were planning for 70,000 people to ride rapid transit, commuter rail, and bus lines, Shortsleeve said, but the march far exceeded that number
EdSchweppe
 
Posts: 86
Joined: Fri Aug 20, 2004 9:51 pm

Re: 2016 Commuter Rail Delay Discussion Thread

Postby Rbts Stn » Sun Jan 22, 2017 11:31 am

There were no extra trains or extra cars from Needham.
User avatar
Rbts Stn
 
Posts: 589
Joined: Thu Feb 09, 2012 2:09 pm
Location: waiting for an "A" train to Watertown

Re: 2016 Commuter Rail Delay Discussion Thread

Postby dbperry » Wed Jan 25, 2017 3:27 pm

suggest / recommend locking this thread and continuing discussion here:

viewtopic.php?f=65&t=164555
Known to Keolis and the MBTA as "Twitter Dave"
Frequently posting about the MBTA Framingham-Worcester line on Twitter: https://twitter.com/FramWorMBTA
Owner of Framingham-Worcester Blog: http://FramWorMBTA.weebly.com/
Maintainer of MBTA schedule archive: http://www.dbperry.net/MBTA/
User avatar
dbperry
 
Posts: 793
Joined: Mon Mar 27, 2006 9:28 pm
Location: Suburbs of Boston

Previous

Return to Massachusetts Bay Transportation Authority (MBTA)

Who is online

Users browsing this forum: No registered users and 3 guests