by WesternNation
Tadman wrote:This is true, the worst problems happen between CUS and Gary. That said, it's infuriating to be east of Porter on 110mph lines doing 20. WTF man, not cool.If you don't mind me asking, what was your train number on the 26th? I checked out both 350 and 352 and while they had a slow start on the Michigan Line, they got up over 100 MPH after MCI. Those slowdowns on the very west end of the MI Line seem to have been corrected, as this morning's 350 got to CP 482 at 8:36 and ~10 minutes later was running at 100 MPH into MCI.
I'm shifting back to South Shore for the summer, and I even drove into the city last week. I just don't have time to screw with this.
That being said, the Michigan Services still have a timekeeping problem. It mystifies me how Amtrak could get delayed on a line with very little conflicting traffic during the day anywhere between Dearborn and Porter, other than Battle Creek. An example of this comes from today's 352. They got held by Wattles Park, on the Amtrak main. Then they were held again on the west side of Albion. There's no other Amtrak train in the vicinity, and NS runs two trains over that line: one from BC to Kalamazoo and back (B34) and another from Jackson to Kalamazoo and back (B33), and B33 doesn't go on duty until later in the evening! That leaves MOW, but from what I understand all the major trackwork from BC to the east was completed already. So I have no idea what could be causing these delays.