Departure time switched to TBD?

[MsCarolyn]

I was just rechecking tomorrow’s departure time for the Illini 393 out of Chicago, and found that the time has been reset from 4:06pm or something like that to TBD (To Be Determined).

Any ideas as to what might be up with that?

 

[acelafan]

Did you see that "TBD" posted on Amtrak's status page? There's been oddities on that recently.

But it looks like #393 left Chicago on time after all.

 

[MsCarolyn]

Did you see that "TBD" posted on Amtrak's status page? There's been oddities on that recently.

But it looks like #393 left Chicago on time after all.

I did, but it changed back to the original departure time the morning of the trip. My SCA on the LSL said that it was probably concern about the weather. But it ended up leaving right on time, just as the LSL was right on time arriving in Chicago.

 

[trimetbusfan]

I was just rechecking tomorrow’s departure time for the Illini 393 out of Chicago, and found that the time has been reset from 4:06pm or something like that to TBD (To Be Determined).

Any ideas as to what might be up with that?

Did you see that "TBD" posted on Amtrak's status page? There's been oddities on that recently.

But it looks like #393 left Chicago on time after all.

My app did this for a Cascades trip I took the last weekend. The day before the trip the ETA was TBD with a red ‘warning’ symbol above the train status, however, when the day of travel came that all went away. I’m guessing it’s some glitch lately. (In my case, it was only showing on the ticket screen of the Amtrak app. When I checked the status on the Amtrak website itself, everything was showing fine).

 

[Peter_Travels]

Like others have noted, I saw the same thing. Took the Chief out of Chicago last Sunday, big TBD beforehand with a service disruption notice. It disappeared the morning of.

Possibly just a train they were monitoring the weather for - before making a determination whether it would run?

 

[trimetbusfan]

Like others have noted, I saw the same thing. Took the Chief out of Chicago last Sunday, big TBD beforehand with a service disruption notice. It disappeared the morning of.

Possibly just a train they were monitoring the weather for - before making a determination whether it would run?

I think it has to do with the recent app update that integrates the train status into the screen that shows your tickets.

In my case on the west coast I knew there was was no whether impending cancellations, and yet my app still displayed the ‘TBD’ so I really don’t think this has to due with the Midwest whether.