2015 Commuter Rail Delay Discussion Thread

[sery2831]

"Slippery rail" on the Fitchburg line this morning; up to 25 minute delays.

I've become dubious about "slippery rail" delays: why would one train be delayed by leaves and a train 30 minutes earlier on the same tracks have no such delays? And the Fitchburg line hasn't even been running on the weekends: it's not as if this is a surprise problem, so why were crews not clearing the tracks while other work was being done on the line? Keolis' incompetence knows no limits.

Newer and older equipment react differently to the slippery rail. So depending on the trainset operating one might do fine and one might be delayed.

As far getting the leaves cleared. Over the weekend the track is out of service and the wash train cannot get access. So the tonight after 7p when the wash train is on duty is the soonest it can be cleared. There is no way to get the wash train through the work areas on Sunday night.

[saulblum]

Newer and older equipment react differently to the slippery rail. So depending on the trainset operating one might do fine and one might be delayed.

As far getting the leaves cleared. Over the weekend the track is out of service and the wash train cannot get access. So the tonight after 7p when the wash train is on duty is the soonest it can be cleared. There is no way to get the wash train through the work areas on Sunday night.

Fair enough. Thanks for clarifying. Last Monday the same train had the same delay, apparently in the same spot.

[BandA]

Add straw brooms in front of the engine above each rail. Would push the leaves off the rail probably as good as a washer. For any trains on the newberry-rockport line, mount witches on the brooms

[MBTA F40PH-2C 1050]

Train 708 the 7:00am from Forge Park, ran double draft with 710 pushing it into Boston, arriving around 10:45am.

the 2012 was the culprit on 708 with main reservoir problems...air compressor kept shutting down, and the new fancy computer we have onboard wouldn't let the engineer recycle it....but the real mess started very early in the morning on the doubledraft that deadhead's to Franklin....the 011 pulling 2 trains couldn't get up over the hill before Endicott....so 703 had to tie on and shove the triple draft to FGPK...then 708 ran into troubles, and 710, with the 2013 tied on and shoved to Boston

[nomis]

The 011 came into Franklin dead, as the middle set of the triple draft & the triple draft was split up at Franklin. the west set became 706, the middle set became 704 from Franklin, and the east set 703 finished at Franklin and went into the yard. 708 (as 8 double deckers) originated from Franklin yard, and had issues before departing Forge Park & 710 ran with the 703 equipment.

In the end - 2013 rescued 2012

[dbperry]

interesting insight into Franklin line delays on 11/16/15 AM:

https://vimeo.com/146013573" onclick="window.open(this.href);return false;

[Diverging Route]

And 352, the 0655 Anderson short-turn was cancelled again today "due to an earlier mechanical failure."

[emannths]

Lots of delays on the Worcester line over the past week have been attributed to track work and/or construction. Anyone know any details? Did something break, or is this related to the work around Boston Landing and Beacon Park, and what's the estimated duration?

This seems like another situation where delays are somewhat predictable and yet aren't announced until after the train is actually late.

[dbperry]

Most Framingham Worcester construction related delays seem to be related to rail replacement west of Framingham and rail destressing east of Framingham. Two different contracts, and I'll bet they are trying to finish both before winter sets in and kills construction season.

The Boston Landing delay seems to have been only Monday AM, and from what I heard on the scanner, I think the poorly managed temporary stop board was quickly fixed on Monday am by a phone conversation between the dispatcher or dispatcher supervisor and the field foreman. Haven't seen any delays near Boston Landing since then.

[Quiet Screamer]

Train 708 the 7:00am from Forge Park, ran double draft with 710 pushing it into Boston, arriving around 10:45am.

the 2012 was the culprit on 708 with main reservoir problems...air compressor kept shutting down, and the new fancy computer we have onboard wouldn't let the engineer recycle it....but the real mess started very early in the morning on the doubledraft that deadhead's to Franklin....the 011 pulling 2 trains couldn't get up over the hill before Endicott....so 703 had to tie on and shove the triple draft to FGPK...then 708 ran into troubles, and 710, with the 2013 tied on and shoved to Boston

2012 Air Dryer went south stuck in purge cycle causing MR not to charge.

[Type 7 3684]

There was an accident at Hanover St. in Newbury earlier causing major delays on the Newburyport Line. A pickup truck part of the crossing. A train was there at the time

[Type 7 3684]

Train 811 is disabled between Canton Jct. and Sharon. Rescue set is on the way to assist, the passengers will board 815 at Sharon. What engine was the culprit this time?

[Type 7 3684]

7 South Side lines are experiencing delays. Fairmount is the exception. About 15 alerts currently.

[deathtopumpkins]

9 alerts just for the Providence line. Geeze. 817 looks to be about an hour late into Providence, where it is being annulled.

[Type 7 3684]

20 south side alerts now, 7 for the Prov. line. Going to bet a HSP did this...