2014 Discussion for Commuter Rail Delays

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

Moderators: CRail, sery2831

Re: 2014 Discussion for Commuter Rail Delays

Postby deathtopumpkins » Thu Dec 11, 2014 11:33 am

Interestingly I note that the T Alerts I received on my phone said 114 was delayed (with no time), and that 116 was delayed 25-35 minutes. Had no idea there was a major issue until looking at this thread.
T Alerts on the website list 120 minute delays for both trains.
Call me Connor or DTP

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

Re: 2014 Discussion for Commuter Rail Delays

Postby StefanW » Thu Dec 11, 2014 12:11 pm

I gave up waiting for what I assume is the 114/116 double-header after 116 got to the same spot as 114 and then proceeded to not move for 30+ minutes.

As I type this (12:10 PM) 116 just got dropped from the data feed but it was last showing up in the Salem area, a delay of 75+ minutes. That means that the poor people on 114 probably will be indeed late by more than two hours.
User avatar
StefanW
 
Posts: 482
Joined: Wed Aug 18, 2004 8:27 pm
Location: Lynn, MA / MP 11.53

Re: 2014 Discussion for Commuter Rail Delays

Postby Diverging Route » Fri Dec 12, 2014 8:05 am

208 had issues this morning, and so 352 was cancelled and the set/crew sent to as a rescue train.
User avatar
Diverging Route
 
Posts: 1560
Joined: Sat Mar 13, 2004 3:35 pm

Re: 2014 Discussion for Commuter Rail Delays

Postby MBTA F40PH-2C 1050 » Sat Dec 13, 2014 6:31 pm

heavy delays this morning in Attleboro.

Woman struck by train
MBTA F40PH-2C 1050
 
Posts: 3498
Joined: Thu Mar 11, 2004 7:57 pm

Re: 2014 Discussion for Commuter Rail Delays

Postby Rbts Stn » Sat Dec 27, 2014 8:22 am

I'm sure this isn't a harbinger of future results, but the first inbound and outbound Saturday Needham commuter trains in 2 years were both delayed, due to "mechanical problem".
User avatar
Rbts Stn
 
Posts: 587
Joined: Thu Feb 09, 2012 2:09 pm
Location: waiting for an "A" train to Watertown

Re: 2014 Discussion for Commuter Rail Delays

Postby MBTA F40PH-2C 1050 » Sun Dec 28, 2014 11:57 am

Rbts Stn wrote:I'm sure this isn't a harbinger of future results, but the first inbound and outbound Saturday Needham commuter trains in 2 years were both delayed, due to "mechanical problem".


there were a lot of issues Southside yesterday, running from crew shortages, equipment turns, yard moves, to Crew themselves not calling certain people for jobs. It was quite the mess indeed yesterday....we"ll do better next Saturday ;) Also, there were lots of HEP problems , 1034 was one of them
MBTA F40PH-2C 1050
 
Posts: 3498
Joined: Thu Mar 11, 2004 7:57 pm

Re: 2014 Discussion for Commuter Rail Delays

Postby Komarovsky » Tue Dec 30, 2014 10:40 am

Messy morning on the Worcester line. 502 and 506 had mechanical problems and it caused cascading 20 minute delays in both directions for several trains until about 9 this morning.
Komarovsky
 
Posts: 482
Joined: Thu Jul 07, 2011 10:11 pm

Re: 2014 Discussion for Commuter Rail Delays

Postby TrainManTy » Tue Dec 30, 2014 11:23 pm

506 was delayed by signal problems in Worcester. We had a Clear to Next Interlocking at CP33 (Westborough) and the conductor spent the whole run in the engineer's cab except for station stops. This isn't required by NORAC for a cab signal failure but it could be a Keolis rule or maybe the alerter died too.
Tyler

All posts are my personal opinion. I do not speak for any organizations on this board.
User avatar
TrainManTy
 
Posts: 444
Joined: Tue Jul 14, 2009 1:18 pm
Location: Worcester, MA

Re: 2014 Discussion for Commuter Rail Delays

Postby MBTA F40PH-2C 1050 » Wed Dec 31, 2014 9:11 am

TrainManTy wrote:506 was delayed by signal problems in Worcester. We had a Clear to Next Interlocking at CP33 (Westborough) and the conductor spent the whole run in the engineer's cab except for station stops. This isn't required by NORAC for a cab signal failure but it could be a Keolis rule or maybe the alerter died too.


Sounds like the alertor was no good, A crew member must be present with the engineer in this case....but that wouldn't call for the Clear to Next Interlocking...cabs probably failed too
MBTA F40PH-2C 1050
 
Posts: 3498
Joined: Thu Mar 11, 2004 7:57 pm

Re: 2014 Discussion for Commuter Rail Delays

Postby jaymac » Fri Jan 02, 2015 7:59 am

400 and 402 got 241d both ways at CPF-FG 0504 and later/01-02-2015. Later moves under local control of maintainer in FG bungalow. Service alert showed trouble in Boston?
"A white SUV with a roof antenna just might not be a company van."
jaymac
 
Posts: 3388
Joined: Wed Mar 04, 2009 1:08 pm

Re: 2014 Discussion for Commuter Rail Delays

Postby Diverging Route » Fri Jan 02, 2015 8:07 am

jaymac wrote:400 and 402 got 241d both ways at CPF-FG 0504 and later/01-02-2015. Later moves under local control of maintainer in FG bungalow. Service alert showed trouble in Boston?


The set for 351/352 was used as a rescue, and consequently those trips cancelled.
User avatar
Diverging Route
 
Posts: 1560
Joined: Sat Mar 13, 2004 3:35 pm

Re: 2014 Discussion for Commuter Rail Delays

Postby cpf354 » Mon Jan 05, 2015 10:31 pm

The alert system had a slight hiccup this morning when it seems to have predicted a "cornfield meet" between trains 452 and 453, somewhere around West Concord! 452 was running about 15-20 late out of Littleton while 453 was close to on time through Waltham and Brandies. The alert system was showing 453 arriving in Concord just a few minutes before 452, which would not be possible since it is operationally single track through Concord. It probably wasn't until 453 had been cooling its' heels at Baker Bridge that they system pushed back it's arrival in Concord.
User avatar
cpf354
 
Posts: 839
Joined: Tue Jul 06, 2004 5:01 am

Re: 2014 Discussion for Commuter Rail Delays

Postby deathtopumpkins » Tue Jan 06, 2015 12:45 am

T Alerts also had a minor hiccup for Newburyport/Rockport train 169 today. I got an alert at 1:42 PM saying train 169, the 5:40 pm departure from North Station is delayed 10-20 mins due to police action. Not sure what's up with that, with an alert 4 hours in advance.
Call me Connor or DTP

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

Re: 2014 Discussion for Commuter Rail Delays

Postby Slushbucket » Tue Jan 06, 2015 1:46 pm

I'm aboard train 321. We're stranded outside the Tighe (?) warehouse. GP40MC is having mechanical problems. Will get loco number when I get a chance. At least the HEP is still working, would hate to be caught without heat on a day like this!

UPDATE: Dead loco was 1135. We got pushed into Anderson by 3247 at about quarter to 3pm. Train 323 with loco 1116 picked up the passengers going the rest of the way while 3247 pulled the 321 back. I could hear 1135 idling. I had a brief chance to speak to 3247's engineer but she didn't hear what the problem was.
Slushbucket
 
Posts: 36
Joined: Wed Feb 05, 2014 7:51 pm
Location: Merrimack Valley, MA

Re: 2014 Discussion for Commuter Rail Delays

Postby octr202 » Thu Jan 08, 2015 8:14 am

I have a friend aboard the ill-fated 206 out of Haverhill this morning. They died between LJ and WJ inbound, now apparently being pushed in by Amtrak 680. The T'lerts said that 308 was going to make the stop at Wilmington to cover for 206, but he just reported that they pulled into Wilmington to a platform packed full of very cold people.
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: No registered users and 7 guests