Hey, there! Log in / Register

Let this be a lesson: Always take your Sudafed

At 1:35 p.m., the MBTA sent out this tweet:

Lowell Train 319 (1:15 pm outbound) is operating 15-25 minutes behind schedule between North Station and Lowell due to terminal congestion.

Neighborhoods: 
Topics: 


Ad:


Like the job UHub is doing? Consider a contribution. Thanks!

Comments

just happened to be the pre-printed excuse that the alerts writer's dart hit today.

up
Voting closed 0

In response to somebody asking about "terminal congestion," the T wrote:

Hello! There was traffic departing North Station due to a mechanical issue w/set of equipment that was outside the station.

Which for those of us not well versed in train lingo means, I think, a train died on the tracks, keeping other trains from using those tracks, but I'm sure Roadman will know for sure.

up
Voting closed 0

Ok, so it's not congestion. It's a mechanical breakdown on a different train.

It would be very hard to have simple congestion mid-day on the commuter rail, since trains run so infrequently.

up
Voting closed 0

is exactly correct. North Station has many tracks that shrink into few tracks as trains leave - the switches at this track reduction are known as a "throat" in railroad lingo (no kidding here), and it's entirely possible that a disabled train within the "throat" could prevent a departing Lowell train from accessing the specific track they need to proceed north.

Of course, the T's alert person could have just said "due to a disabled train" to describe the problem instead of trying to sound impressive.

up
Voting closed 0

Or maybe it might not have been a disabled train? There are other causes for congestion.

up
Voting closed 0

(which Adam posted above):

due to a mechanical issue w/set of equipment that was outside the station.

Plus, if there wasn't really a disabled train, it wouldn't be the first time the T blamed something on a non-existent mechanical issue. They do it all the time when Keolis decides to cancel trains for their convenience.

up
Voting closed 0

Mechanical issue =/= disabled train. Keolis knows more about the situation than you do, so I'm sure they had a reason for deciding that "terminal congestion" was a more logical reason than "disabled train".

Disabled train typically implies a disabled train on the line the alert is for. But if there's a disabled train that's just being moved from North Station to BET, for example, and it just happens to take up a track in the North Station yard, meaning other trains have to shift around it, that would create congestion that might impact the Lowell train, even if the disabled train is not a Lowell train, and is not on tracks Lowell trains would normally use, and is therefore irrelevant to the Lowell train, apart from causing congestion that impacts it.

Also, please cite evidence that proves Keolis has ever cancelled trains "for their convenience".

up
Voting closed 0

Well, there were at least 2 trains cancelled on the Rockport line this morning, with NO explanations offered...just sayin'

up
Voting closed 0

Similar terminology is used in aviation. And the terminology can also be ambiguous / unclear.

'Congestion' generally implies there are more planes arriving and departing than there is space in the air to handle them safely. So, to maintain safety, departures get held on the ground. Sometimes, like after a thunderstorm shuts down an airport, it can take an hour or so to get all delayed departures on their way, without an aircraft being disabled.

up
Voting closed 0

It would take some serious skill to cause congestion with the sparse mid-day schedule.

Here's what leaves North Station during the two hours leading up to 1:15 pm:
11:15 Lowell
11:20 Newburyport
11:30 Fitchburg
12:00 Rockport
12:15 Lowell
12:30 Haverhill
1:00 Fitchburg
1:15 Lowell

It's not exactly the busiest railroad in the world.

up
Voting closed 0

Terminal Congestion

Isn't that what did in the Bronte sisters?

up
Voting closed 0

It was mechanically 'challenged'. There was a mechanically challenged train causing delays.

up
Voting closed 0