2017 Commuter Rail Delay Discussion Thread

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

Moderators: CRail, sery2831

Re: 2017 Commuter Rail Delay Discussion Thread

Postby Backshophoss » Wed Jun 14, 2017 8:34 pm

Need another Caffine IV for that person. :P
Backshophoss
 
Posts: 4436
Joined: Mon Mar 05, 2012 7:58 pm

Re: 2017 Commuter Rail Delay Discussion Thread

Postby RenegadeMonster » Thu Jun 15, 2017 7:46 am

Backshophoss wrote:Need another Caffine IV for that person. :P



Yup.

And is it just me, or is it always Wachusett.
RenegadeMonster
 
Posts: 203
Joined: Tue Mar 07, 2017 9:19 am

Re: 2017 Commuter Rail Delay Discussion Thread

Postby jaymac » Fri Jun 16, 2017 5:49 am

The 06-16-2017 400 was terminated at North Leominster cuzza mechanical issues, with 400's passengers boarding 402. Going under the Rte. 13 UGB at 0605, it looked like 2004 was the "power," "looked like" cuz the foliage and traffic either side were too heavy to be certain. At 0443, D-3 had acknowledged 400 had "mechanical issues" with the train set and gave permission to reverse at 335 back to the facility. Dunno what happened after that and whether the one that died was the original or a replacement. At 0627, D-3 spoke to 400's equipment, saying,"We'll see what time you get to Derby."
"A white SUV with a roof antenna just might not be a company van."
jaymac
 
Posts: 3371
Joined: Wed Mar 04, 2009 1:08 pm

Re: 2017 Commuter Rail Delay Discussion Thread

Postby BostonUrbEx » Fri Jun 16, 2017 7:38 pm

400 was late out of the facility due to wheel slip issues, then ultimately died at North Leominster, where it sat the entire time until it could continue inbound again by some miracle. As you said, 402 did grab all passengers at North Leominster. 400's equipment eventually got going as 404 was at about Fitchburg or so, but ran as a highball extra and caught up on 402 almost.

408 had to shove in at reduced speed the entire way in from the facility. 492 originated from Ayer, left Ayer the same time as 408 was arriving, and eventually left 408 (the express!) in its dust. 410 caught up and actually passed 408 on the approach to Porter Sq.
User avatar
BostonUrbEx
 
Posts: 3567
Joined: Thu Dec 03, 2009 9:55 pm
Location: Winn to MPT 8, Boston to MPN 38, and Hat to Bank

Re: 2017 Commuter Rail Delay Discussion Thread

Postby BandA » Fri Jun 16, 2017 11:46 pm

Wheel slip issues? There is a gypsy moth caterpillar infestation ramping up this year. Had cut up pieces of oak leaves and a few caterpillars walking around the ground on Wed.
User avatar
BandA
 
Posts: 1761
Joined: Thu Oct 11, 2012 11:47 am

Re: 2017 Commuter Rail Delay Discussion Thread

Postby RenegadeMonster » Tue Jun 20, 2017 8:13 am

Bad morning on the Newburyport / Rockport lines

Rockport Train 106 (7:10 am inbound) is stopped at Beverly Farms due to a tree on the tracks and is currently 10-20 minutes behind schedule.
Update: Rockport Trn 106 remains stopped at Beverly Farms due to a tree across the tracks & is currently 30-40 minutes late
Update: Rockport Train 106 (7:10 am inbound) is operating 35-40 min behind schedule between Prides Crossing and N. Station due to a tree on tracks.
Newburyport Train 160 is making unscheduled stops to accommodate passengers for Train 158

Train 158 suffered severe overcrowding from Salem on. While the conductors made several announcements apologizing for over crowding due to accommodating train 106's passengers as well as instructed people getting off before North Station to make their way to a door before Swapscott people were very upset. The aisle and vestibules were packed full. It was like riding the orange line. Once at North Station I over heard the conductors telling several people (We were giving them a earful about the overcrowding) sorry again and they can make a complaint at the customer service box about the over crowding.
RenegadeMonster
 
Posts: 203
Joined: Tue Mar 07, 2017 9:19 am

Re: 2017 Commuter Rail Delay Discussion Thread

Postby StefanW » Fri Jun 23, 2017 3:52 pm

Train 113 died at River Works more than 1 hour ago. Oddly, train 115 (also to Rockport) just sailed right past it a few moments ago on the opposite track... or appeared to. I didn't think 115 stopped at River Works long enough to transfer people from 113... if it stopped at all. There's either so few people on 113 that they all got on 115 in just a quick couple of minutes, or nobody transferred at all. Maybe the crew thinks they can get 113 moving again soon.
User avatar
StefanW
 
Posts: 474
Joined: Wed Aug 18, 2004 8:27 pm
Location: Lynn, MA / MP 11.53

Re: 2017 Commuter Rail Delay Discussion Thread

Postby sonicdoommario » Thu Jun 29, 2017 4:06 pm

An Amtrak headed outbound broke down this morning outside of Mansfield, which 843 and 803 got stuck behind. It didn't cause major inbound delays but 842 ended up being cancelled as it couldn't get down to Attleboro and ended up pushing the Amtrak I believe. 808 ended up making stops at Sharon and Hyde Park. I did see the Amtrak along with 843 and 803 as we passed by it.

Since Attleboro was still crowded with 842's passengers I couldn't get to my usual waiting spot, so I went to the opposite end in the platform. Got to ride in the control car and stood outside the cab door and got to see a first person view of the tracks and some of the train controls, it was really cool! For a guy like me it was like a kid being at Disney World. :P

The control car was 1827 I believe and I saw 90 as the speed limit. Didn't I read somewhere that we could have a 90mph train on the Providence line (or 89 technically) if we had an HSP with all Rotem cars? Those would all be 8XX and 9XX cars, right?
sonicdoommario
 
Posts: 35
Joined: Fri Jun 10, 2016 8:14 pm

Re: 2017 Commuter Rail Delay Discussion Thread

Postby RenegadeMonster » Thu Jun 29, 2017 4:25 pm

Love seeing the view through the cab car door.

Rotems would be all 8XX and 18XX. 9XX are still Kawasaki Cars

I don't know about the speed limit rules for that line though, so I can't answer that question.
RenegadeMonster
 
Posts: 203
Joined: Tue Mar 07, 2017 9:19 am

Re: 2017 Commuter Rail Delay Discussion Thread

Postby jaymac » Fri Jun 30, 2017 5:56 am

The 06-30-2017 400 with 3 flats, 1 bi, and the 2000 left Wachusett on time, but about 15 minutes later reported to D-3 that it was having power trouble, couldn't get over 50, and had low amperage. D-3 advised that he would advise Boston West. Boston West did get on the air, but was broken beyond understanding from Gardner. There was a 0540 D-3/400 exchange about still being at Ayer (20+ minutes late) and mechanical trouble, but at 0645, the only Service Alert was for 404 with signal issues.
Dunno if the 2000 is a first-time or frequent problem.
"A white SUV with a roof antenna just might not be a company van."
jaymac
 
Posts: 3371
Joined: Wed Mar 04, 2009 1:08 pm

Re: 2017 Commuter Rail Delay Discussion Thread

Postby MBTA F40PH-2C 1050 » Wed Jul 05, 2017 3:48 pm

C speeds at which the MBTA falls under ACSES are 90 mph. Our equipment is restricted to 80 mph
MBTA F40PH-2C 1050
 
Posts: 3493
Joined: Thu Mar 11, 2004 7:57 pm

Re: 2017 Commuter Rail Delay Discussion Thread

Postby Diverging Route » Thu Jul 06, 2017 6:08 am

A real mess on the NEC last evening with switch failure near Readville. Many trains > 30 minutes late.

And today didn't start out well either, with 804 failing at PVD.
User avatar
Diverging Route
 
Posts: 1556
Joined: Sat Mar 13, 2004 3:35 pm

Re: 2017 Commuter Rail Delay Discussion Thread

Postby RenegadeMonster » Fri Jul 07, 2017 3:18 pm

Is the Northside down a set or two today?

This morning all the Newburyport trains were delayed 5 to 15 minutes due to earlier mechanical issues. Per usual, the Beverly train canceled.
RenegadeMonster
 
Posts: 203
Joined: Tue Mar 07, 2017 9:19 am

Re: 2017 Commuter Rail Delay Discussion Thread

Postby Diverging Route » Mon Jul 10, 2017 5:21 am

Oh my.

Lowell Line: A telephone pole is down and blocking both tracks of the Lowell line at West Medford. Updates to follow.

Last updated: Jul 10 2017 06:14 AM
User avatar
Diverging Route
 
Posts: 1556
Joined: Sat Mar 13, 2004 3:35 pm

Re: 2017 Commuter Rail Delay Discussion Thread

Postby sonicdoommario » Mon Jul 10, 2017 11:30 pm

Providence train 801 (5:30AM outbound) was 30 minutes late. This train turns into 810, right? Probably the only turn on the Providence line I'm not fully sure on. 810 wasn't delayed this morning, and if 801 has almost an hour to turn to 810 (since it arrives at Providence at 6:30 and 810 leaves at 7:30), then a 30 minute delay wouldn't hit 810...

Also, if it does get to Providence at 6:30, what does it do for that whole hour? Sit in the station? Go back to Pawtucket and wait for 806 and 808 to pass?
sonicdoommario
 
Posts: 35
Joined: Fri Jun 10, 2016 8:14 pm

PreviousNext

Return to Massachusetts Bay Transportation Authority (MBTA)

Who is online

Users browsing this forum: No registered users and 5 guests