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 MBTA F40PH-2C 1050 » Thu Jan 21, 2016 4:39 pm

embarrassing :(
MBTA F40PH-2C 1050
 
Posts: 3498
Joined: Thu Mar 11, 2004 7:57 pm

Re: 2016 Commuter Rail Delay Discussion Thread

Postby octr202 » Fri Jan 22, 2016 2:15 pm

Midday problems on Haverhill. From the alerts, looks like 207 (12:20 Andover, turns to 216) died between Reading and North Wilmington. 209 is pushing it into N. Wilmington. 216 is being bused, no word on what will happen to 218.
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 Type 7 3684 » Fri Jan 22, 2016 3:49 pm

Haverhill Train 216 (1:25 inbound) will depart Andover 100+ min late inbound via the Haverhill Line due to a mechanical issue.

Yeesh.
Young train enthusiast who also has an interest in planes and cars
Type 7 3684
 
Posts: 288
Joined: Fri Sep 25, 2015 3:36 pm
Location: Newton, MA

Re: 2016 Commuter Rail Delay Discussion Thread

Postby Screamer 1000 » Fri Jan 22, 2016 5:12 pm

HSP issues?
Screamer 1000
 
Posts: 109
Joined: Fri May 30, 2014 8:15 pm

Re: 2016 Commuter Rail Delay Discussion Thread

Postby octr202 » Fri Jan 22, 2016 8:45 pm

And that wasn't the end of it on the Western Route...

213 (16:30 outbound) apparently died in or near Lawrence station. 215 got caught behind it. According to the T alerts, 213's passengers were picked up by Amtrak to go to Bradford and Haverhill. 215's folks got bused, as did inbound 222 (213 turns to 222 at Bradford).

I was on 217 which was on time into Andover. The T alerts said it was likely in the ballpark of 90 minutes late by the time it got to Haverhill. 219 and even 221 reported as about an hour late each.

One more breakdown and they might have run as many buses for the Haverhill Line as trains this afternoon and evening.
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 GP40MC1118 » Sat Jan 23, 2016 2:20 pm

A particularly lousy night at Lawrence. 213's power - one of the "We Got 40 New Engines This Winter" was
the culprit. Amtrak 685 generously took their remaining passengers east and shoved 213 east of CP-Frost.
215, with the mighty 1139, dropped their passengers at Lawrence and tied on to 213's set, but had beau-coup
air issues and was unable to clear Frost for 217.

Not to be missed are:
1) A 112 car SEPO waiting things out between CPF-AS and CPF-JK.
2) That STUPID single track station at Lawrence that MBTA signed off on. Boy did this rear its ugly head again.
3) CPF-AS new design omitted a crossover, thus reducing flexibility.
4) No-brainer as yet completed double track restoration.
5) The equally glacial progress on the Merrimack River Bridge situation.

SEPO was sent east to free up track ahead of 217.
215/213 draft finally cleared CPF-Frost and 217, Amtrak 687, 219, 221 all followed SEPO east
GP40MC1118
 
Posts: 3314
Joined: Thu Mar 11, 2004 8:06 pm

Re: 2016 Commuter Rail Delay Discussion Thread

Postby GP40MC1118 » Sat Jan 23, 2016 2:25 pm

And it was one of the new engines earlier in the day too...Sigh...

D
GP40MC1118
 
Posts: 3314
Joined: Thu Mar 11, 2004 8:06 pm

Re: 2016 Commuter Rail Delay Discussion Thread

Postby sery2831 » Sat Jan 23, 2016 2:55 pm

First break down of the day was the 2038. The evening rush hour was the 2033 which has had two other failures this week. Including a failure in Haverhill at night earlier in the week. The good news for Haverhill morning passengers is that right now HSPs are banned from putting up in Bradford. But trains 200 and 213 are Boston based so those most likely will see HSPs.
Moderator: MBTA Rail Operations
User avatar
sery2831
 
Posts: 5136
Joined: Fri Mar 12, 2004 2:15 pm
Location: Manchester, NH

Re: 2016 Commuter Rail Delay Discussion Thread

Postby BandA » Sun Jan 24, 2016 12:02 am

Why are the HSP's failing? And how can they send out equipment that is repeatedly failing?
User avatar
BandA
 
Posts: 1901
Joined: Thu Oct 11, 2012 11:47 am

Re: 2016 Commuter Rail Delay Discussion Thread

Postby deathtopumpkins » Sun Jan 24, 2016 9:31 am

sery2831 wrote:First break down of the day was the 2038. The evening rush hour was the 2033 which has had two other failures this week. Including a failure in Haverhill at night earlier in the week. The good news for Haverhill morning passengers is that right now HSPs are banned from putting up in Bradford. But trains 200 and 213 are Boston based so those most likely will see HSPs.


Why are they banned from Bradford?
Call me Connor or DTP

Railfan & Roadgeek from the North Shore of Mass.
deathtopumpkins
 
Posts: 980
Joined: Tue Aug 27, 2013 8:56 am
Location: Somerville, MA

Re: 2016 Commuter Rail Delay Discussion Thread

Postby sery2831 » Sun Jan 24, 2016 8:14 pm

Since HSPs have to idle in the layovers for the time being, due to noise.
Moderator: MBTA Rail Operations
User avatar
sery2831
 
Posts: 5136
Joined: Fri Mar 12, 2004 2:15 pm
Location: Manchester, NH

Re: 2016 Commuter Rail Delay Discussion Thread

Postby NH2060 » Sun Jan 24, 2016 11:13 pm

BandA wrote:And how can they send out equipment that is repeatedly failing?

What other choice do they really have? The HSPs were supposed to boost an already aging fleet not throw a wrench into the mix. Same goes for the Rotems.


I can almost guarantee that this is the last time the MBTA orders anything not-exactly-off-the-shelf inside and out.
NH2060
 
Posts: 1443
Joined: Thu Feb 25, 2010 4:44 pm

Re: 2016 Commuter Rail Delay Discussion Thread

Postby sery2831 » Mon Jan 25, 2016 1:14 am

NH2060 wrote:I can almost guarantee that this is the last time the MBTA orders anything not-exactly-off-the-shelf inside and out.


Why do you say that? They repeatedly custom order equipment. I don't blame MPI for the HSP disaster at all, they make a great product.
Moderator: MBTA Rail Operations
User avatar
sery2831
 
Posts: 5136
Joined: Fri Mar 12, 2004 2:15 pm
Location: Manchester, NH

Re: 2016 Commuter Rail Delay Discussion Thread

Postby octr202 » Mon Jan 25, 2016 8:12 am

Looks like the HSP ban isn't solving the problems on the Western Route today...208 reported (via T Alerts) as 45-60 late due to mechanical problems.
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 25, 2016 8:57 am

To make up for 208, 356 was extended up to Wilmington to help cover. 208, according to T'lerts, "running at reduced speeds" and expected into North Sta 45-60 late. Stefan's tracker showing it 45 late at Wilmington as of 8:55 AM.
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.

PreviousNext

Return to Massachusetts Bay Transportation Authority (MBTA)

Who is online

Users browsing this forum: BigUglyCat and 8 guests