Commuter Rail Delay Tracker/ Discussion (RETIRED)

For the Providence Line, alternate transportation might be Amtrak (if one happens to be scheduled around that time) or Bonanza/Peter Pan bus.

Prov/Stou 800 05:07 AM IB experiencing over 60 min delay 12/13/2010 6:24 AM

Prov/Stou 804 06:07 AM IB cancelled resulting in significant delays. 12/13/2010 6:23 AM

Prov/Stou 802 05:25 AM IB experiencing 30-45 min delay 12/13/2010 6:24 AM

So, if you're a Providence line user, it stings to be you this morning

Reports of signal-related delays on the first train out of Newburyport this morning. Also, the Western Route signal problems between WJ and Reading were continuing, 204 (experienced first hand) and 206 (based on T'lerts) took 15-25 minute hits. There had been reports of these signal problems starting Saturday afternoon in that area, apparently still going on this morning.

I wonder what went awry in the Providence that caused all these delays especially the head train (800) to be an hour late?

Whatever the problem, it was isolated to MBCR, as #95 got thru fine. 804 being cancelled explains the set i saw shutdown with no lights from #95.

Robert Paniagua wrote:Prov/Stou 800 05:07 AM IB experiencing over 60 min delay 12/13/2010 6:24 AM

Prov/Stou 804 06:07 AM IB cancelled resulting in significant delays. 12/13/2010 6:23 AM

Prov/Stou 802 05:25 AM IB experiencing 30-45 min delay 12/13/2010 6:24 AM

So, if you're a Providence line user, it stings to be you this morning

I wonder what could of caused #800 to be over a hour late and #804 to be cancelled??? I'm guessing #802 got stuck behind #800 somewhere down the line!!

octr202 wrote:Reports of signal-related delays on the first train out of Newburyport this morning. Also, the Western Route signal problems between WJ and Reading were continuing, 204 (experienced first hand) and 206 (based on T'lerts) took 15-25 minute hits. There had been reports of these signal problems starting Saturday afternoon in that area, apparently still going on this morning.

I got caught in the WJ to Reading delay on Saturday. I was told they needed to get a part and that it wouldn't be there until Sunday or Monday. We were 25 late getting into Boston on train #1216 and turn for train #1217, so we departed 19 mins late from Boston on #1217. By the time we got back to Boston on train #1220 we were 40 mins late. The signals worked going east but not west. And it's 4 miles from CPW-WJ to the first signal, so it's a long slow ride.

Ouch:

Prov/Stou OB train 923 5:45pm has been annulled. Passengers will be accommodated by train 925 6:30pm OB. 12/13/2010 5:47 PM

Inbound Needham #604 had some sort of problem between Forest Hills and Ruggles and reversed back to Forest Hills this morning. Any idea what happened?

More:

Fairmount 767 06:30 PM, 768 07:10 PM have been annulled, and will be replaced by substitute bus service making all station stops. 12/13/2010 5:51 PM

Fairmount 765 05:45 PM, 766 06:21 PM have been annulled. Passengers will be accommodated by substitute bus service making all scheduled stops. 12/13/2010 5:44 PM

Fairmount Train 765 05:45 PM OB will not run from South Station. A substitute bus shuttle will run in its place from South Station to Readville. 12/13/2010 2:56 PM

Wow, today is not a good day for the MBTA

Whatever the problem, it was isolated to MBCR, as #95 got thru fine. 804 being cancelled explains the set i saw shutdown with no lights from #95.

Oh I see, so Amtrak's 2151 and 095 (both outbound on track 1 while 800 and 802/804 were on track 2) came fine. I wonder if something (locomotivewise) might have caused 800 to be down for so long, as it caused a ripple effect inbound.

At least the signals on the Western Route appear to be functioning normally today, as John predicted.

Framnghm/Worc P514 08:40 AM IB experiencing 30-45 min delay due to truck striking bridge at Park Road in Wellesley. 12/14/2010 9:17 AM

Framnghm/Worc P512 07:35 AM IB experiencing 45-60 min delay due to truck striking bridge at Park Road in Wellesley. 12/14/2010 9:15 AM

Another day another incident.

#410 was canceled this morning and run as #412 after the 412 set apparently was found to be not working. Not sure what was wrong with it. Once again 410 was sent back to Fitchburg, though supposedly it never even made it as far as Leominster this time. Train was running about 5 minutes behind 412's schedule all the way in, and it was something of a sardine can when it arrived.