A MassDOT report concludes the driver of the infamous train was to blame for it heading towards town by itself, but notes the T is also aiming to fix the condition that led him to leave the train in the first place - problems with an old cabling system leased from Verizon that was making signals fail and trains stop on the tracks south of North Quincy. Read more.
More signal problems, this time at Alewife. J Patience reports:
I boarded at Park between 6 - 6:05. Now starting to stand by at Harvard. 6:47.
For a holiday morning, one Red Line train seemed a bit crowded this morning, Charles Cherney reports.
This is apparently an issue for Philadelphia as well:
The T's reporting some travails getting riders into town from Braintree due to a train that decided to join Elijah. This was after earlier signal problems near JFK/UMass.
The T reports it's busing Red Line riders between Alewife and Harvard due to a power problem at Harvard. Word came right after Gov. Baker, in a snow news conference, said, "The T actually had a pretty good morning."
There's a dead train somewhere on the Orange Line (the T isn't saying where) and a train that breathes no more at Quincy Center on the Red Line. Passengers are not happy, but whadaya gonna do?
UPDATE, 7 a.m.: Equipment removed, T reports "minor" residual delays.
The T is running shuttle buses between North Quincy and JFK/UMass due to "disabled work equipment" at Savin Hill. A T spokesman adds:
MBTA crews are on scene, working hard to get the piece of equipment off the main line. Customers may also board Commuter Rail trains at Braintree, Quincy Center and JFK for service into South Station. Customers are asked to allow extra time to commute.
The T warned riders yesterday that delays related to the reconstruction of the Longfellow Bridge would continue today. What they optimistically didn't warn riders about, however, were the signal problems between North Quincy and JFK/UMass - of the sort the Braintree line has been having for a couple of months now.
From the north, though, the trains are running well over the bridge.
UPDATE: The MBTA warns Longfellow-related slowdowns could last two to three days.
Red Line trains in both directions are moving kind of slow this morning, due to the weekend track work on the Longfellow Bridge.
At 7:40 a.m., Justlippe reported:
I left Central at 7:10am. We're just now hanging half out of the tunnel headed to MGH.
First responders from both Cambridge and Boston and divers from Boston rushed to the Charles River near the Longfellow Bridge around 6:30 p.m. on what appeared to be a report that two people might be in the river. Read more.
Ailing signals are keeping southbound Red Line commuters from dinner tonight, but possibly driving them to drink.
The T is advising "moderate" delays into town on the Red Line from Braintree due to a train that just could not make it past Quincy Center, and "minor" delays into town on the Orange Line from Forest Hills, due to a train that ascended to the pearly gates at Mass. Ave.
UPDATE: Another Blue Line train died, at Airport. More trolleys died, at Waban and Arlington.
So far this morning, trains have shuffled off this mortal coil on the Green Line (Brookline Village and Reservoir on the D and Washington Street on the B) and the Blue Line (State Street). Riders on the Orange and Red lines didn't miss any of the fun, however, due to what the T says are now fixed signal issues near Wellington and JFK/UMass (the Blue Line also had some signal woes). Red Line riders also saw trains slow due to the ongoing work on the Longfellow.