Hey, there! Log in / Register
Another train from Haverhill is dead; weary riders wish they could have fled
By adamg on Mon, 01/11/2016 - 7:50am
Train 204 from Haverhill is sitting in Malden going nowhere fast.
Meanwhile, west of town, a locomotive sighs and dies in Wellesley, leaving riders on train 506 out of Worcester wondering when they'll get into town.
Like the job UHub is doing? Consider a contribution. Thanks!
Double fail on the Western Route...
...aka the Haverhill line.
204 with it's aforementioned delay at Malden.
206 (express via Wilmington) had issues up in the Haverhill/Lawrence area, was running about 60 late. 208 got stuck in the mess as well and was ~30 mins late as well.
Trains that originated from Reading
ran late as well. 8:00 from Reading ran 25 minutes late and 8:30 from Reading was shown as running 30 minutes late.
And what idiot at the T decided to reference only the train numbers and not (i.e.) "8:00 From Reading" in the alert messages posted at the stations? Had nearly everyone at Melrose Highlands this morning staring at the boards in confusion.
BTW, best message fail I've seen in some time:
Message: Train 262 Running 25 To 30 Minutes Late Due To Earlier Mechanical Failure
Immediately followed by: Next Train To Boston In 4 Minutes
Stuck on the train. And in
Stuck on the train. And in the words of Rick James, "...it was too damn cold an' funkayyy!"