Commuter Rail Delay Tracker/ Discussion (RETIRED)

Since the amount of delayed trains has increased over the last week... I am going to try a sticky dedicated to the subject. Please do not create a new thread about delays on your line. Thanks!

well, to start

The Fitchburg/South Acton Commuter Rail is experiencing delays during evening 6:30 pm to close of service for 25-30 minutes due to N/A


Commuter Rail Framingham/Worcester - Train #P531 (6:20pm outbound) experiencing 10-15 minute delays 12/11/2007 6:36 PM


Commuter Rail Franklin/Forge Park - Train #723 (6:15pm outbound) experiencing 10-15 minute delays 12/11/2007 6:32 PM

Commuter Rail Needham - Train #627 (6:25pm outbound) experiencing 10-15 minute delays 12/11/2007 6:34 PM


Commuter Rail Providence/Stoughton - Train #923 (6:30pm outbound)experiencing 10-15 minute delays 12/11/2007 6:35 PM

what a joke. honestly.

They're blaming Guilford for the Fitchburg Line delays:

Commuter Rail Fitchburg/South Acton - Train #429 (5:20pm outbound) experiencing over 30 minute delays 12/11/2007 6:47 PM

Commuter Rail Fitchburg/South Acton outbound train 429 (5:20pm) and outbound train 431 (5:40pm) are experiencing 25-30 min delays due to Guilford freight train interference near Ayer station. 12/11/2007 7:18 PM

Commuter Rail Fitchburg/South Acton inbound trains 434 (725pm) and train 436 (8:22pm) are experiencing 20-25 min delays due to earlier Guilford freight train interference. 12/11/2007 8:38 PM

Saving these emails is building quite the dossier on the Fitchburg Line's troubles so far this month...

Lately they have been very vague as to why the train is late/ canceled. As in, franklin forge park 10 - 15 min delays.. "due to equipment/ mechanical/ track/ signal failure etc". Is the "T alert team" becoming embarrassed to explain whats gong on, or do they think we can asume what happend?

they need more equipment. its only been this bad since greenbush opened.

and for some reason, it takes like years to get equipment.

They are usually beating around the bush, and often for good reason. They aren't going to publicly announce if there is a fatality or accident, especially on a mobile alert when a person receiving the alert could possibly be on the train involved. They also aren't going to get into detail about something like a train had to stop to replace an air hose, or can't go above 15mph because a car has serious flatspots. The general public doesn't understand or care that a signal failure means that the train needs to proceed at restricted speed after stopping to receive permission to do so until a more favorable signal is passed. So those are "mechanical" and "signal" problems. It is usually not the T hiding the truth, although when it is, it is usually for good reason.

They have just been saying train so and so is late, they have dropped the mechanical failure, signal problems and what not excuses. Seems to be their way of getting out of telling the truth.

Today I saw them blame a delay on a Guliford freight train. I guess CSX isn't the only other railroad they blame.

Commuter Rail Middleborough/Lakeville - inbound train#008 (7:20am) canceled 12/10/2007 7:23 AM

Commuter Rail Middleborough/Lakeville - Train #012 (9:38am inbound) experiencing over 30 min delays 12/10/2007 10:12 AM

Commuter Rail Middleborough/Lakeville - Train #015 (2:15pm outbound) experiencing 25-30 minute delays 12/10/2007 2:33 PM

Commuter Rail Middleborough/Lakeville - Train #041 (2:40pm outbound) experiencing 15-20 minute delays 12/10/2007 2:44 PM

Commuter Rail Middleborough/Lakeville - Train #018 (3:27pm inbound)experiencing over 30 minute delays 12/10/2007 3:54 PM

Commuter Rail Middleborough/Lakeville outbound train #019 (4:40pm) is experiencing 15-20 min delays. 12/10/2007 4:56 PM

Commuter Rail Middleborough/Lakeville Train #019 (4:40pm outbound)experiencing over 30 minute delays 12/10/2007 5:06 PM

Commuter Rail Middleborough/Lakeville train #021 (5:10pm) outbound is experiencing 15-20 min delays. 12/10/2007 5:24 PM

Commuter Rail Middleborough/Lakeville outbound train #023 (5:56pm) is experiencing over 30 min delays. 12/10/2007 7:03 PM


They stopped explaining why, thats for sure.


I know we had an ice storm and that certainly screwed up my day at work running boats, but was this a systemwide issue or was there something in particular about Middleboro/Lakeville? I only get commuter rail alerts for that line so I'm not sure how everyone else fared. Its also interesting that the outbounds had the most delays, I would have figured the inbound runs are more apt to run behind, unless of course there was an issue at south station.

Heres an intresting one
Commuter Rail Providence/Stoughton - Train #814 (9:43am inbound) experiencing 15 minute delay departing mansfield 12/14/2007 10:37 AM
More shocking on the Readville/fairmount line!
Commuter Rail Fairmount - Train #754 (9:55am inbound) experiencing over 35 minute delays 12/14/2007 10:28 AM

Commuter Rail Fairmount - Train #753 (9:21am outbound) departed 35 minutes late from South Station 12/14/2007 9:57 AM

And heres more, each on separate lines

Commuter Rail Haverhill - Train 232 (4:32pm inbound) is experiencing over 30 minute delays. 12/14/2007 5:19 PM

Commuter Rail Middleborough/Lakeville - Train 018 (3:27pm inbound) experiencing 15-20 minute delays. 12/14/2007 4:32 PM
back to top

Commuter Rail Needham - Train 621 (4:40pm outbound) is experiencing over 30 minute delays. 12/14/2007 5:14 PM

Commuter Rail Newburyport/Rockport - Train 67 (4:45pm outbound) and train 68 (5:40pm inbound) have been cancelled. The following trains will accommodate customers. 12/14/2007 4:34 PM

Needham takes it again...

Commuter Rail Needham - Train 622 (5:40pm inbound) has been canceled. 12/14/2007 5:57 PM

Commuter Rail Needham - Train 621 (4:40pm outbound) has been canceled. The following train 623 (5:20pm outbound) will accommodate customers.

This train usually has a too-big set: either three doubles and three singles or five doubles and two singles, when a six-car set of singles is plenty.

HEYYYYYY!!! It looks like there back to reasons
Commuter Rail Haverhill - All trains are experiencing over 30 minute delays due to a signal problem. 12/14/2007 9:54 PM

Over a 30 minutes are being nice! A major signal failure between Lawrence and Haverhill tonight delayed ALL Haverhill service since 3pm. Some trains being up to 2 hours late!