Railroad Forums 

  • 2018 Commuter Rail Delay Thread

  • Discussion relating to commuter rail, light rail, and subway operations of the MBTA.
Discussion relating to commuter rail, light rail, and subway operations of the MBTA.

Moderators: sery2831, CRail

 #1478213  by dth9269
 
GP40MC1118 wrote:Sherman Street is no longer a "quiet zone" crossing, hence train legally required to sound
horns..
OK, but according to the FRA Inventory History, it *hasn't* been a quiet zone crossing since at least 2002, including at the most recent update in November, 2017. So...why the sudden change?

Basing this statement on FRA report generator at https://safetydata.fra.dot.gov/Officeof ... ssing.aspx, and inventory # 052313H.

Dan
 #1478435  by jaymac
 
(late posting)
The 07-04-2018 Service Alerts showed 1400 45-55 late -- earlier posting much less -- cuzza 22K experiencing power difficulties on 1 at Fitchburg platform. More complete details at the 0800/07-04-2018 Gardner Gawking.
 #1479041  by KevinSun242
 
408 was late about 10 minutes today. Twice during the trip, the train came to a complete stop. The conductor said something on the intercom along the lines of the equipment thinking that the train was speeding when it really wasn't, so they had to stop and get approval from dispatch to proceed.

1531 was the cab car.
 #1479844  by BostonUrbEx
 
402 was running late enough this morning that local 402 and express 404 pulled into Porter side-by-side. Must have been quite the crush load going down to the Red Line!
 #1479885  by KevinSun242
 
408 was late by around 5 minutes today due to mechanical issues.

Not a great PM rush hour for the system. Fitchburg had delays due to mechanical problems and late equipment arrivals. Flooding in Natick. Police activity on Fairmount and Franklin. Signal issues on Greenbush.
 #1481200  by jaymac
 
The 07-30-2018 402 was posted for a 20-25 delay account fire department activity -- 2 rail-grinding tie-fires east of Shirley across from High School and between Walker and MacPherson. D-3 gave 402 the OK to continue at 0623 after being held at Derby.
 #1482476  by cpf354
 
8/9/18-Train 423 was cursed. 11 minutes late out of North Station due to a paperwork issue. Then at Porter Square the head end power conked out. Engineer tried to start it but was unsuccessful so rolled out to Belmont where another unsuccessful attempt was made. Back on the move with no lights or A/C the crew gave us the option of taking the following train at Waltham if we needed lights and A/C. Was getting stuffy when I got off at Concord-whew :wink: 1064 was the culprit IIRC.
 #1483801  by KevinSun242
 
I heard that 408 passed 406 yesterday.

402 was late today due to mechanical issues. 406 ended up being cancelled due to mechanical issues, and 408 was initially reported also as late due to mechanical issues. Once 491 arrived at Littleton, they decided to turn it around immediately at 7:40 and run it inbound, making all local stops as if it were a late 406 it seems. 408 ended up making all local stops as well as if it were a late 492. And an extra train originated at Lincoln sometime between the 492 and the 408.

Both 406 and 408 were reported in the MBTA Rail app as having 1824 as the control car, so it sounds like they either used 406's set or used 408 as a rescue train?

Thankfully, one of the crewmembers of 492 saw me walking down the ramp at Littleton and waved at me to get on before the train left.
 #1484397  by Diverging Route
 
#WaitWhat?

Lowell Line train cancelled
Lowell Train 302 (6:31 am from Anderson/Woburn) is cancelled today due to a mechanical issue. Passengers may consider Train 302 (6:31 am from Anderson/Woburn).

Affected direction: Inbound
Last Updated: Aug 30 2018 05:18 AM
 #1484399  by CRail
 
As of 6:05am:
Lowell Train 302 (6:10 am from Lowell) is no longer cancelled today and will originate at Wilmington. Updates to follow.
 #1486266  by BostonUrbEx
 
BO-1 died right at Salem station today on their way to Peabody. Train 162 had to push them through the tunnel to the #1 track, go back to Salem, and then continue in on the #2 track. A significant delay was the result for Train 162.
  • 1
  • 6
  • 7
  • 8
  • 9
  • 10