What happened with Train 7/27?

Discussion in 'Amtrak Rail Discussion' started by ParanoidAndroid, Feb 10, 2019.

Amtrak Unlimited Discussion Forum

Help Support Amtrak Unlimited Discussion Forum:

  1. Feb 10, 2019 #1

    ParanoidAndroid

    P

    ParanoidAndroid

    OBS Chief

    Joined:
    Feb 21, 2015
    Messages:
    620
    Location:
    Varies
    #7 is 15 hours late in clear weather, and #27 is 16 hours late in some snow. It looks like they were delayed while detouring in ND, but what were the other causes of the delays? Most Builders make it through the usual cold weather on time, so that shouldn't be the issue. Also, I'd have thought that they'd turn the train in Spokane, but they didn't do that. Now, the return #8 and #28 will likely leave early in the morning of the 10th. Pretty bad.
     
  2. Feb 10, 2019 #2

    AmtrakBlue

    AmtrakBlue

    AmtrakBlue

    Conductor Gathering Team Member

    Joined:
    May 6, 2011
    Messages:
    10,861
    Location:
    Delaware
    I THINK 7/27 took a detour in ?ND?
     
  3. Feb 10, 2019 #3

    jis

    jis

    jis

    Conductor AU Lifetime Supporter Gathering Team Member

    Joined:
    Aug 24, 2003
    Messages:
    23,882
    Location:
    Space Coast, Florida, Area code 3-2-1
    Apparently it was impossible to arrange bussing at Spokane due to snowstorm. So Amtrak decided to run the train through instead of stranding passengers in the middle of inclement weather. Seems like they did the right thing for once.
     
  4. Feb 10, 2019 #4

    esmeralda

    e

    esmeralda

    Joined:
    Oct 19, 2010
    Messages:
    1
    7 was late out of the gate in Chicago due to the ice/winter storm on Tuesday and Wednesday.  The crew ran out of hours and had to wait for a new crew east of La Crosse which delayed them by several hours in addition.  They then had to maneuver through the massive snow drifts from the blizzard on the cutoff between Fargo and Minot.  The remainder of delay was most likely gradually added while being stuck in rail traffic in MT and ID. 8 also had to take the cutoff between Minot and Fargo and was stuck for several hours northwest of Fargo due to a Seattle to Chicago Z train collision with a car.  Also 8 had to maneuver through the after effects of the blizzard in ND. 
     
  5. Feb 10, 2019 #5

    oregon pioneer

    oregon pioneer

    oregon pioneer

    Conductor

    Joined:
    Feb 15, 2011
    Messages:
    2,031
    Location:
    near Seneca, Oregon
    I expected they might just cancel yesterday afternoon's 8/28, given that passenger loads are usually light this time of year. But no, the OP guessed correctly. #28 departed PDX at 4:20am, and #8 departed SEA at 6:53am. They are not showing on the status maps, nor listed as a service disruption. Trains 7/27 arriving today are running about 4 hours late, and the following day on time (so far). So I guess they wanted that consist and crew to go back in proper order, another good call IMO.

    Glad I wasn't waiting at WIH for *that* one!
     
  6. Feb 11, 2019 #6

    ParanoidAndroid

    P

    ParanoidAndroid

    OBS Chief

    Joined:
    Feb 21, 2015
    Messages:
    620
    Location:
    Varies
    How did you figure out those departure times?
     
  7. Feb 11, 2019 #7

    oregon pioneer

    oregon pioneer

    oregon pioneer

    Conductor

    Joined:
    Feb 15, 2011
    Messages:
    2,031
    Location:
    near Seneca, Oregon
    Amtrak.com "Track Train", using departure station PDX or SEA, train #28/8, and the departure date 2/9.
     
    Last edited by a moderator: Feb 11, 2019

Share This Page



arrow_white