montana mike
Conductor
I see train 8/28 of 3/22 was totally cancelled? First time I have seen that in a long time. What happened? Mudslides in Washington again?
7/27 were also cancelled (or today’s) due to the storm that’s hitting ND.I see train 8/28 of 3/22 was totally cancelled? First time I have seen that in a long time. What happened? Mudslides in Washington again?
They did it only a month ago. I arrived on 7(2/22), which was 13 hours late. I was really surprised there was no bustitution from SPK westward, because we were so late. I guess the reason was that they had already decided to cancel 8(2/25). I believe they cancelled the EB in both directions that day, and offered passengers the alternative of going on the CS/CZ, or waiting till the next day.First time I have seen that in a long time.
Yet another example of Entropy leading us to inevitable heat death.It is a new day. No more run and rescue in inclement weather. Additionally, it isnt always feasible to run a long distance train part of the route, particularly if it costs way more to operate than your normal loss.
They've canceled for rain and wind as well. Wind is more dangerous than the snow. Hundreds of trains were cancelled in the Northeast a few days ago before the first snow flake fell from the sky.I understand fully the liability issue. What I dont understand is canceling the Empire Builder for nothing more than a normal winter snow storm in North Dakota. Or canceling the crescent for a normal snow storm in Virginia. Both cases the weather was nothing out of the ordinary for the area.
If that is the case why even risk running at all in the winter? Just close it all down until the summer. If you can cancel a train that travels for thousands of miles over the course of a route for a storm that only affects a hundred or so miles, then where does it end?
What about rain? wind? lighting? dust? Where does end.?
That's not true at all. They've operated and left people stranded, held trains in stations, canceled them en route. This was just as recent as a few weeks ago. So, it is far from figured out. The difference is you have a for profit CEO that has basically stated enough is enough. We are not going to continue to lose the limited money we have attempting to operate a train in these conditions for a small number of people, that we'll ultimately end up giving vouchers to anyway.Amtrak has managed to figure it out for almost 50 years with very few issues. But Anderson arrives and there are all sorts of reasons not too. It seems like he tries to find reasons not to run the train.
I just heard back from my BNSF contacts again, and he mentioned that they were surprised to hear of Amtrak's cancellation, especially since most of the winter weather was to be well south of the Hi-Line route (eg. Minot had indeed received several inches of snow during the day today, with perhaps another inch or two in the forecast before ending early this evening, long before the EB from either direction would have arrived, with a temperature in the low 30's), but this weather event was nothing compared to the normal winter storms that North Dakota experiences. Gosh, I have been on the EB in Minot in the winter on perhaps a half dozen occasions, when it was below zero, the wind howling at 40 mph and heavy snow coming down and the EB arrived on time! He reiterated that BNSF trains were moving close to normal along the entire route and they were not anticipating any significant issues. In fact he said along about 90% of the entire route it was either dry or just wet, with only parts of ND and a small area in the Cascades seeing snow.
Oh, well, I wonder if this is going to be the new norm for Amtrak, to cancel trains when ANY winter event is forecasted along a LD route. If this is the case the EBs will be cancelled quite often in the winter. Footnote: We received 120 inches of snow in Whitefish this winter with 4 blockbuster bone fide Blizzards and during each one, the Empire Builders arrived and departed (yes, some were several hours late), but all made it to the ultimate destinations with decent timekeeping.
PS: #7 made it thru all of the supposed "bad weather" today without any significant issues and is scheduled to arrived in WFH almost on time this evening!
It might be that 87 passengers are affected when the train is canceled. But in the future, it could that 29 passengers are affected, because 2/3 of passengers decide to use other transportation. Yes, other forms of transportation get canceled, but that's when conditions are bad or are almost sure to get bad, not when conditions might get bad or have a chance of getting bad. If Mr Anderson is thinking as Thirdrail7 suggests, he could be putting the long distance trains on a path to a self-fulfilling prophecy of no one caring about long distance service.As much as I don't like it, maybe Mr. Anderson thinks the resources are better spent on other services and is tired of paying through the nose for 87 passengers (of which half will want refunds or credits), without any receiving anything from the hosts that butcher the trains and drives up costs. After all, he is a for profit (remember, that was part of PRIIA and Amtrak's original mandate) CEO. There is no room for nostalgia in his mind. It is strictly business and what are the numbers going to say?Oh, well, I wonder if this is going to be the new norm for Amtrak, to cancel trains when ANY winter event is forecasted along a LD route. If this is the case the EBs will be cancelled quite often in the winter. Footnote: We received 120 inches of snow in Whitefish this winter with 4 blockbuster bone fide Blizzards and during each one, the Empire Builders arrived and departed (yes, some were several hours late), but all made it to the ultimate destinations with decent timekeeping.
Perhaps his continued terminations will either cause the affected ridership base to complain to their representatives and they will demand funding and penalties against the hosts, (a la Kay Hutchinson) or will prove what some already suspect: No one really cares about long distance service and it will end.
If we had been talking about the storm of the century, or even the season, your points would have been valid, but snowfall amounts ranged from nothing along almost all of the route of the EB to 6" in a few parts of ND. BNSF freights operated normally. I was a very frequent flier of NW Airlines when I lived in Michigan and Mr. Anderson was President of that airline during part of that time. One of his polices was to use weather conditions or "mechanical" issues to cancel flights that were "light loads" (ie. not many pax booked on the flight) and rebook them on later flights. This of course made good economic sense for the airline, but it wreaked havoc on peoples' travel plans. I suspect these EBs may have suffered the same fate, since they were weekday runs in the off season and were lightly booked. Assuming Amtrak could accommodate most of the LD pax on these two trains on later runs, Amtrak would save some $$ to just cancel the trains. This snow event may just have been a catalyst for them to do so.They've canceled for rain and wind as well. Wind is more dangerous than the snow. Hundreds of trains were cancelled in the Northeast a few days ago before the first snow flake fell from the sky.I understand fully the liability issue. What I dont understand is canceling the Empire Builder for nothing more than a normal winter snow storm in North Dakota. Or canceling the crescent for a normal snow storm in Virginia. Both cases the weather was nothing out of the ordinary for the area.
If that is the case why even risk running at all in the winter? Just close it all down until the summer. If you can cancel a train that travels for thousands of miles over the course of a route for a storm that only affects a hundred or so miles, then where does it end?
What about rain? wind? lighting? dust? Where does end.?
That's not true at all. They've operated and left people stranded, held trains in stations, canceled them en route. This was just as recent as a few weeks ago. So, it is far from figured out. The difference is you have a for profit CEO that has basically stated enough is enough. We are not going to continue to lose the limited money we have attempting to operate a train in these conditions for a small number of people, that we'll ultimately end up giving vouchers to anyway.Amtrak has managed to figure it out for almost 50 years with very few issues. But Anderson arrives and there are all sorts of reasons not too. It seems like he tries to find reasons not to run the train.
For all of the comments, do any of you have the actual passenger counts for these trains?
.
I just heard back from my BNSF contacts again, and he mentioned that they were surprised to hear of Amtrak's cancellation, especially since most of the winter weather was to be well south of the Hi-Line route (eg. Minot had indeed received several inches of snow during the day today, with perhaps another inch or two in the forecast before ending early this evening, long before the EB from either direction would have arrived, with a temperature in the low 30's), but this weather event was nothing compared to the normal winter storms that North Dakota experiences. Gosh, I have been on the EB in Minot in the winter on perhaps a half dozen occasions, when it was below zero, the wind howling at 40 mph and heavy snow coming down and the EB arrived on time! He reiterated that BNSF trains were moving close to normal along the entire route and they were not anticipating any significant issues. In fact he said along about 90% of the entire route it was either dry or just wet, with only parts of ND and a small area in the Cascades seeing snow.
Oh, well, I wonder if this is going to be the new norm for Amtrak, to cancel trains when ANY winter event is forecasted along a LD route. If this is the case the EBs will be cancelled quite often in the winter. Footnote: We received 120 inches of snow in Whitefish this winter with 4 blockbuster bone fide Blizzards and during each one, the Empire Builders arrived and departed (yes, some were several hours late), but all made it to the ultimate destinations with decent timekeeping.
PS: #7 made it thru all of the supposed "bad weather" today without any significant issues and is scheduled to arrived in WFH almost on time this evening!
That is why 7(22) was not canceled. It was anticipated to push through. Did your "contact" volunteer to send and finance the extra engines that BNSF requests(and when I say requests, it is actually a demand) during certain weather events? Did your contact offer to reimburse Amtrak for the delays if BNSF can't get them through? Did your contact offer to reimburse the passengers when they state they were delayed and they want vouchers? Did your contact offer to split the costs of the crew overtime or the recrews if the trains are delayed? You see, all of those costs go against the train and Amtrak's bottom line. As much as I don't like it, i don't see anyone ponying up more to compensate for these issues. When the money is out, the money is out and it doesn't seem like Congress will help.
As much as I don't like it, maybe Mr. Anderson thinks the resources are better spent on other services and is tired of paying through the nose for 87 passengers (of which half will want refunds or credits), without any receiving anything from the hosts that butcher the trains and drives up costs. After all, he is a for profit (remember, that was part of PRIIA and Amtrak's original mandate) CEO. There is no room for nostalgia in his mind. It is strictly business and what are the numbers going to say?
Perhaps his continued terminations will either cause the affected ridership base to complain to their representatives and they will demand funding and penalties against the hosts, (a la Kay Hutchinson) or will prove what some already suspect: No one really cares about long distance service and it will end.
We'll find out soon enough.
Amtrak has managed to figure it out for almost 50 years with very few issues. But Anderson arrives and there are all sorts of reasons not too. It seems like he tries to find reasons not to run the train.
If we had been talking about the storm of the century, or even the season, your points would have been valid, but snowfall amounts ranged from nothing along almost all of the route of the EB to 6" in a few parts of ND. BNSF freights operated normally. I was a very frequent flier of NW Airlines when I lived in Michigan and Mr. Anderson was President of that airline during part of that time. One of his polices was to use weather conditions or "mechanical" issues to cancel flights that were "light loads" (ie. not many pax booked on the flight) and rebook them on later flights. This of course made good economic sense for the airline, but it wreaked havoc on peoples' travel plans. I suspect these EBs may have suffered the same fate, since they were weekday runs in the off season and were lightly booked. Assuming Amtrak could accommodate most of the LD pax on these two trains on later runs, Amtrak would save some $$ to just cancel the trains. This snow event may just have been a catalyst for them to do so.They've canceled for rain and wind as well. Wind is more dangerous than the snow. Hundreds of trains were cancelled in the Northeast a few days ago before the first snow flake fell from the sky.I understand fully the liability issue. What I dont understand is canceling the Empire Builder for nothing more than a normal winter snow storm in North Dakota. Or canceling the crescent for a normal snow storm in Virginia. Both cases the weather was nothing out of the ordinary for the area.
If that is the case why even risk running at all in the winter? Just close it all down until the summer. If you can cancel a train that travels for thousands of miles over the course of a route for a storm that only affects a hundred or so miles, then where does it end?
What about rain? wind? lighting? dust? Where does end.?
That's not true at all. They've operated and left people stranded, held trains in stations, canceled them en route. This was just as recent as a few weeks ago. So, it is far from figured out. The difference is you have a for profit CEO that has basically stated enough is enough. We are not going to continue to lose the limited money we have attempting to operate a train in these conditions for a small number of people, that we'll ultimately end up giving vouchers to anyway.Amtrak has managed to figure it out for almost 50 years with very few issues. But Anderson arrives and there are all sorts of reasons not too. It seems like he tries to find reasons not to run the train.
For all of the comments, do any of you have the actual passenger counts for these trains?
.
I just heard back from my BNSF contacts again, and he mentioned that they were surprised to hear of Amtrak's cancellation, especially since most of the winter weather was to be well south of the Hi-Line route (eg. Minot had indeed received several inches of snow during the day today, with perhaps another inch or two in the forecast before ending early this evening, long before the EB from either direction would have arrived, with a temperature in the low 30's), but this weather event was nothing compared to the normal winter storms that North Dakota experiences. Gosh, I have been on the EB in Minot in the winter on perhaps a half dozen occasions, when it was below zero, the wind howling at 40 mph and heavy snow coming down and the EB arrived on time! He reiterated that BNSF trains were moving close to normal along the entire route and they were not anticipating any significant issues. In fact he said along about 90% of the entire route it was either dry or just wet, with only parts of ND and a small area in the Cascades seeing snow.
Oh, well, I wonder if this is going to be the new norm for Amtrak, to cancel trains when ANY winter event is forecasted along a LD route. If this is the case the EBs will be cancelled quite often in the winter. Footnote: We received 120 inches of snow in Whitefish this winter with 4 blockbuster bone fide Blizzards and during each one, the Empire Builders arrived and departed (yes, some were several hours late), but all made it to the ultimate destinations with decent timekeeping.
PS: #7 made it thru all of the supposed "bad weather" today without any significant issues and is scheduled to arrived in WFH almost on time this evening!
That is why 7(22) was not canceled. It was anticipated to push through. Did your "contact" volunteer to send and finance the extra engines that BNSF requests(and when I say requests, it is actually a demand) during certain weather events? Did your contact offer to reimburse Amtrak for the delays if BNSF can't get them through? Did your contact offer to reimburse the passengers when they state they were delayed and they want vouchers? Did your contact offer to split the costs of the crew overtime or the recrews if the trains are delayed? You see, all of those costs go against the train and Amtrak's bottom line. As much as I don't like it, i don't see anyone ponying up more to compensate for these issues. When the money is out, the money is out and it doesn't seem like Congress will help.
As much as I don't like it, maybe Mr. Anderson thinks the resources are better spent on other services and is tired of paying through the nose for 87 passengers (of which half will want refunds or credits), without any receiving anything from the hosts that butcher the trains and drives up costs. After all, he is a for profit (remember, that was part of PRIIA and Amtrak's original mandate) CEO. There is no room for nostalgia in his mind. It is strictly business and what are the numbers going to say?
Perhaps his continued terminations will either cause the affected ridership base to complain to their representatives and they will demand funding and penalties against the hosts, (a la Kay Hutchinson) or will prove what some already suspect: No one really cares about long distance service and it will end.
We'll find out soon enough.
If we had been talking about the storm of the century, or even the season, your points would have been valid, but snowfall amounts ranged from nothing along almost all of the route of the EB to 6" in a few parts of ND. BNSF freights operated normally. I was a very frequent flier of NW Airlines when I lived in Michigan and Mr. Anderson was President of that airline during part of that time. One of his polices was to use weather conditions or "mechanical" issues to cancel flights that were "light loads" (ie. not many pax booked on the flight) and rebook them on later flights. This of course made good economic sense for the airline, but it wreaked havoc on peoples' travel plans. I suspect these EBs may have suffered the same fate, since they were weekday runs in the off season and were lightly booked. Assuming Amtrak could accommodate most of the LD pax on these two trains on later runs, Amtrak would save some $$ to just cancel the trains. This snow event may just have been a catalyst for them to do so.
.
Enter your email address to join: