Sign up for the Today newsletter
Get everything you need to know to start your day, delivered right to your inbox every morning.
By Darin Zullo
The MBTA dispatched shuttle buses to replace Red Line service between Alewife and Harvard for nearly four hours Monday after a train became disabled near Davis.
At 11:22 a.m., the MBTA announced on X that there would be “delays of about 20 minutes” due to the disabled train. Approximately half an hour later, they announced that shuttle buses had been dispatched to replace service between Alewife and Harvard and to expect delays.
Red Line Update: Shuttle buses are replacing service between Alewife and Harvard due to a disabled train near Davis. https://t.co/anrjGK2200
— MBTA (@MBTA) January 20, 2025
Shuttle buses continued to replace service for the next four hours as crews worked to remove the disabled train.
By 3:25 p.m., the MBTA had resumed service between the two stations but still estimated 20-minute delays as shuttle buses continued to supplement service. The shuttle buses were phased out shortly afterwards.
Red Line Update: Service between Alewife and Harvard has resumed with delays of about 20 minutes after a disabled train was removed from service at Davis. https://t.co/e3wI0ocmrt
— MBTA (@MBTA) January 20, 2025
The delays were officially cleared just before 6:30 p.m.
Passengers who were on the disabled train reported hearing a “loud crash,” according to WCVB. The source of this noise was another train coupling to the disabled train so the tracks could be cleared, according to an MBTA spokesperson.
“Coupling a train entails towing a disabled train with a functional one in order to clear the tracks,” the spokesperson said. “The noise passengers heard were two trains attempting to hitch.”
The disabled train has been removed from service, the MBTA said.
Get everything you need to know to start your day, delivered right to your inbox every morning.
Stay up to date with everything Boston. Receive the latest news and breaking updates, straight from our newsroom to your inbox.
To comment, please create a screen name in your profile
To comment, please verify your email address
Conversation
This discussion has ended. Please join elsewhere on Boston.com