The Dreaded Service Disruption - Question

Phil S said:

Is there some benefit to Amtrak of declaring a "service disruption", even when the train is running on time? Yesterday, #8 was listed as service disruption, I assume because it departed Everett instead of Seattle. But half way across Montana it was keeping almost perfect time. Do maybe Amtrak rules permit doing nasty (or even nice) things to passengers once "SD" is declared? I hope it isn't simply that Amtrak's programmers can't figure out how to display status for a train that, for example, didn't depart from it's scheduled departure point.

Click to expand...

jis said:

Phil S said:

Is there some benefit to Amtrak of declaring a "service disruption", even when the train is running on time? Yesterday, #8 was listed as service disruption, I assume because it departed Everett instead of Seattle. But half way across Montana it was keeping almost perfect time. Do maybe Amtrak rules permit doing nasty (or even nice) things to passengers once "SD" is declared? I hope it isn't simply that Amtrak's programmers can't figure out how to display status for a train that, for example, didn't depart from it's scheduled departure point.

Click to expand...

AFAICT it is mostly that. It has more to do with the lacking capabilities of Amtrak's IT system than anything else.
I wonder if one can request and get full refund when a train is publicly declared to be in Service Disruption, even though it is running on time.

Click to expand...