Commuter Rail Delay Tracker/ Discussion (RETIRED)

MBTA F40PH-2C 1050 wrote:I passed the Pawtucket facility this morning at 7:45 and a set with the 1055 and 7 double deckers was still in the layover and they were having troubles with it. After I got to Attleboro and train 833 arrived, they finally got the 1055 up and running because she passed through Attleboro on Track 2 while 833 was changing ends to become 834. Can we expect the 1055 to make its way to BET sometime soon???

The 1055 seems to be not one of our best rebuilds...always looks dirty and has a rather sick K5LA. It may be in BET before long.

BTW do you know if the troubled set was 812 or a very late 810?

-Dan

first off, just saw this on the MBTA site:

Framnghm/Worc outbound train # 535 (8:20pm) is experiencing a 60 minute delay due to a medical emergency at Framingham Station. 8/4/2008 10:16 PM

Framnghm/Work inbound train #536 (7:46pm) is being diverted to substitute shuttle bus service from Framingham Station inbound due to a medical emergency in Framingham. 8/4/2008 9:34 PM

.... 801 turns into 812 and the late train out of the yard is 810

yet another medical emergency on the Worcester line. anyone know what happened in these last 2 events?

Framnghm/Worc is experiencing significant delays due to a medical emergency in Westborough. Inbound train #P524 (2:05pm) will be replaced with bus service at Worcester making all local stops then connecting with train service into Boston at Southborough. 8/5/2008 1:29 PM

today, 8/5, the Lake Shore Limited P449, struck a trespasser on Track 1 @ Westboro station @ 12:45pm

Westboro accident

Cascading delays again: 1st Haverhill inbound delayed 30 min, "helped by #204". #212 held 12 min. at Oak Grove for an outbound (maybe #257), now #209, #214 also "15-20 min. delays". Lowell R/T 355/356 cancelled acc't "mechanical", #063 on the Eastern also "15-20 min. delay".

Close - I believe I heard 202 out of Haverhill running on time this morning (8/6/08). According to the 206's crew on the combined 204/206, 204 died around Bradford. Here's the summary, with edits from observations.

Haverhill Train #294 (5:42am inbound) is experiencing a 25-30 minute delay. 8/6/2008 6:09 AM
Sent: 8/6/2008 6:10 AM

294? That's new

Haverhill Train #204 (5:42am inbound) is experiencing a 45 minute delay. Train #206 (6:14am inbound) will assist Train #204 to Boston and will incur a 25-30 minute delay as well. 8/6/2008 6:09 AM

The combined 204/206 arrived at Andover about 7:00. We ran no more than about 40 mph (give or take 5-6 mph, based on speed of cars overtaking us on parallel streets at times), finally making it into North Station about 8:20 or so.

Haverhill Train #253 (6:50am outbound) is experiencing a 10-15 minute delay. 8/6/2008 6:55 AM
Sent: 8/6/2008 6:56 AM

Never did recall seeing this one, we ran Reading-Wyoming about 5 minutes ahead of its schedule, and passed something going outbound just south of Wyoming. If it was 253, it was really late.

Haverhill Train #257 (7:55am outbound) is experiencing a 25-30 minute delay. 8/6/2008 8:25 AM
Sent: 8/6/2008 8:26 AM

Haverhill Train #214 (9:03am inbound) will experience 15-20 minute delays in service. 8/6/2008 9:07 AM
Sent: 8/6/2008 9:10 AM

In retrospect, probably should have taken 208, there were no reports of delays on it, but that "I've been waiting for an hour, this train's here" instinct kicked in when 204/206 arrived.

204 and 206 both had GP40s, the 1127 was the unit on the front consist (train 204). It appeared to be running when it passed us at Andover, but at North Station it might have just been the HEP generator. The GP40 on 206's set was definitely working from the sounds of it.

I should add that 3247 was picking something out of North Station just before 9:00 am, not sure what -- but it didn't look like the 204/206 set, as the 3247 was too close in to the platforms.

Interesting article in the Globe this morning about electrical interference with the signaling system as the possible source of Haverhill line delays:

http://www.boston.com/news/local/massac ... ne_delays/

"The surges have dragged down the Haverhill line's recent on-time performance. In June and July, about one in four trains was at least five minutes late, inconveniencing thousands of commuters."

"Within the last month, National Grid brought in a consultant to try to find the origin of the problem and correct it. During the surges, current from adjacent power lines somehow electrifies the metal tracks, shorting signals along the way, said Rich Davey, deputy general manager of the Massachusetts Bay Commuter Railroad Co., which runs commuter rail under a contract with the MBTA. The tracks on the diesel-powered rail line do not normally carry high levels of electricity."

Jon

Gee, when electrification came to the commuter rail system, I never thought they'd start with the Haverhill Line...

jonnhrr wrote:Interesting article in the Globe this morning about electrical interference with the signaling system as the possible source of Haverhill line delays:

http://www.boston.com/news/local/massac ... ne_delays/

"The surges have dragged down the Haverhill line's recent on-time performance. In June and July, about one in four trains was at least five minutes late, inconveniencing thousands of commuters."

"Within the last month, National Grid brought in a consultant to try to find the origin of the problem and correct it. During the surges, current from adjacent power lines somehow electrifies the metal tracks, shorting signals along the way, said Rich Davey, deputy general manager of the Massachusetts Bay Commuter Railroad Co., which runs commuter rail under a contract with the MBTA. The tracks on the diesel-powered rail line do not normally carry high levels of electricity."

Jon

Maybe we've discovered the secret of wireless transmission of electric energy, just like Nikloai Tesla predicted.

With wireless transmission of electricity, we won't need catenary systems at all! Just electrify the tracks and place a modified electric locomotive on it to run it subway style. Now that'd be something! But thats a discussion for another thread.

how about doing it like model railroading? Send the current through the track. As long as people don't touch both tracks at once, they won't get electricuted

Has this been affecting the Amtrak Downeaster as well?

Ron Newman wrote:Has this been affecting the Amtrak Downeaster as well?

Of course. I remember taking the haverhill line on the day they were fixing the signals. They made everyone get off at andover while they bustituted the rest of the way. When I got onto the shuttle bus, I saw the commuter train pull into a siding to let the Downeaster pass. I guess the signals aren't a problem for Amtrak as long as the commuter trains aren't in their way.

More Haverhill fun (fortunately I wasn't on these, but just seeing all of the emails):

Haverhill outbound train#205 (7:40am) experiencing over 30 min delay between Lawrence and Haverhill. 8/12/2008 8:40 AM

Haverhill inbound train#214 (9:03am) experiencing over 30 min delay 8/12/2008 8:43 AM

Haverhill outbound train#205 (7:40am) experiencing over 30 min delay between Lawrence and Haverhill. Substitute bus shuttle will run between Lawrence and Haverhill. 8/12/2008 8:40 AM

Haverhill inbound train#214 (9:03am) experiencing over 30 min delay between Haverhill and Lawrence. Substitue bus service will run from Haverhill to Lawrence. 8/12/2008 8:43 AM

And again today (8/13)...258, 212, and 262 so far inbound, as well as 205 and 209 outbound, all late anywhere from 15 to 30+ minutes. The bad luck continues (mostly seems to center around 212 and 214, which out to get the hit any minute now). If this is signal problems, they seem to affect a very specific point in the day each day. :-/