Home Open Account Help 284 users online

Passenger Trains > #5(26) service disruption - washout west of Ottumwa, IA not fixed


Pages:  [ 1 ][ 2 ] [ Next ]
Current Page:1 of 2


Date: 06/26/15 19:32
#5(26) service disruption - washout west of Ottumwa, IA not fixed
Author: illini73

Today's WB California Zephyr #5(26) has been placed in Service Disruption at Burlington, IA.  BNSF track is still washed out at Melrose, Iowa and not expected to re-open until midnight tonight (one main track - other to open at 0600 tomorrow morning).  Train is still on the move nearing Mt. Pleasant, IA and will no doubt wait at Ottumwa until the track is opened. Melrose is 30 mi. west of Ottumwa.   Info. from Amtrak and BNSF.



Date: 06/26/15 19:53
RE:
Author: 4400horsepower

Saw #5 here at Burlington, in case anyone is wondering, locomotives were 183 and 158. Normal consist.

Brian
 



Date: 06/26/15 20:29
Re: #5(26) service disruption - washout west of Ottumwa, IA not f
Author: SandHouseTalk

Adding insult to injury, the BNSF ballast train at the work site derailed!



Date: 06/26/15 21:16
Re: #5(26) service disruption - washout west of Ottumwa, IA not f
Author: GenePoon

Train 5(26) is currently (1115pm) at track speed approaching Ottumwa.

From Ottumwa it is about 35 miles to Melrose where BNSF estimated open track around midnight.



Date: 06/27/15 04:03
Re: #5(26) service disruption - washout west of Ottumwa, IA not f
Author: wpjones

#5 is still at Ottumwa waiting for open track. BNSF has 46 trains tied down because of washout. Belt train did derail and now has burned belt off. Amtrak Crew is dead and none available. No estimate for train to move at this time. I was told the ex Miwauke to KC was not an option.
Steve



Date: 06/27/15 05:21
Re: #5(26) service disruption - washout west of Ottumwa, IA not f
Author: joemvcnj

This is becoming an anuual curse on the  old Q main line, in some ways worse than the heaving on the Grand Forks line.
Need to at least think about a permanent reroute onto the UP, C&NW, or the II.



Date: 06/27/15 06:26
Re: #5(26) service disruption - washout west of Ottumwa, IA not f
Author: brc600

   #5 is stalled at Ottumwa, Iowa, will leave @ 10AM SAT, ETA Omaha 130pm. #6 is ETA Omaha 1055AM SAT. Both will use the CB&Q/BN/BNSF. Amtrak #3/4 have been using the MP/UP KCY-STL and GM&O/UP STL-CHI. Tim Vana
Omaha,NE
wpjones Wrote:
-------------------------------------------------------
> #5 is still at Ottumwa waiting for open track.
> BNSF has 46 trains tied down because of washout.
> Belt train did derail and now has burned belt off.
> Amtrak Crew is dead and none available. No
> estimate for train to move at this time. I was
> told the ex Miwauke to KC was not an option.
> Steve



Date: 06/27/15 07:14
Re: #5(26) service disruption - washout west of Ottumwa, IA not f
Author: wpjones

As of 09:12 ct there is no estimate for 5 to leave Ottumwa
Just decieded 6 will detour over the C&NW OMA to CHI
Steve



Date: 06/27/15 09:25
Re: #5(26) service disruption - washout west of Ottumwa, IA not f
Author: brc600

Thanks for the update, Steve!

wpjones Wrote:
-------------------------------------------------------
> As of 09:12 ct there is no estimate for 5 to leave
> Ottumwa
> Just decieded 6 will detour over the C&NW OMA to
> CHI
> Steve



Date: 06/27/15 09:29
Re: #5(26) service disruption - washout west of Ottumwa, IA not f
Author: RutledgeRadio

I was on 5 last night, and boy it was an experience. BNSF didn't know what to do with us. First off we departed Chicago over an hour late. Got into Galesburg and spent probably a half hour there (my guess is this was when they first discovered the derailment issue). Got on the move and had to wait for a freight outside town. Finally arrived in Burlington, and the conductor announced that we would be running the engines around the train and heading back to Galesburg, per BNSF's instructions. They got the HEP down and were about ready to move the engines when BNSF decided to change their minds and let us continue into Ottumwa. Left Burlington after dark. Running through Fairfield our train went into emergency and we screeched to a stop, and sat in town by the old CB&Q depot for at least a half hour while they figured that out. I guess an air hose snapped. Started creeping west and finally got up to speed around Batavia/Agency. Heading into Ottumwa we stopped again less than a 1/4 mile before the station. We were running on main #2 and I guess they didn't know if they had permission to enter the station (??). Finally pulled in at 11:30. I was very thankfull I was getting off here. The train is still in the station as far as I know.



Date: 06/27/15 09:32
Re: #5(26) service disruption - washout west of Ottumwa, IA not f
Author: wpjones

New Update, Engineer on 5 will die at 16:00. There are no Available Engineers. This train will fleet with other freight traffic. No special treatment.
6 is at East Berks waiting for crew due there at 11:45.
Now #6 will not detour UP
They will not take train with current crew situation.
Steve



Date: 06/27/15 09:48
Re: #5(26) service disruption - washout west of Ottumwa, IA
Author: Agent

Track A Train show that #5 has left the station in Ottumwa.  Right now its stopped on the west edge of the town.



Date: 06/27/15 09:56
Re: #5(26) service disruption - washout west of Ottumwa, IA
Author: wpjones

They were allowed to move in antisipation of things opening up. They will be behind any "Z" trains that are out there.
Steve



Date: 06/27/15 11:06
Re: #5(26) service disruption - washout west of Ottumwa, IA
Author: illini73

As of 12:55 p.m. CT train is sitting near Albia, IA.  Not even up to the washout site at Melrose, IA yet.  Earlier this morning, BNSF changed the projected opening time at Melrose to Noon today, 12 hrs later than previously projected.  Second MT projected to open at 6 p.m. this evening.  From other chatter it seems #5 may require another re-crew before it even gets to Omaha.

I feel bad for the passengers.



Date: 06/27/15 11:25
Re: #5(26) service disruption - washout west of Ottumwa, IA
Author: amtrakwolverine

Amtrak should just cancel the train at the next station and bus passengers back to chicago and put them up in hotels and try again another day.



Date: 06/27/15 13:30
Re: #5(26) service disruption - washout west of Ottumwa, IA
Author: dan

5 is going east and been for awhile, not a good time to ride the CZ east of omaha



Date: 06/27/15 13:47
Re: #5(26) service disruption - washout west of Ottumwa, IA
Author: illini73

amtrakwolverine Wrote:
-------------------------------------------------------
> Amtrak should just cancel the train at the next station and bus passengers back to chicago and put them up in hotels and try again another day.

It appears they are taking your advice, as the train is returning to Ottumwa.  Whether it will get there before the engineer goes on HOS at 1600 as suggested earlier in this thread, is another matter.



Date: 06/27/15 14:18
Re: #5(26) service disruption - washout west of Ottumwa, IA
Author: rockislander

What is happening to 5(27) and 6 at Omaha?

Posted from iPhone



Date: 06/27/15 14:27
Re: #5(26) service disruption - washout west of Ottumwa, IA
Author: illini73

rockislander Wrote:
-------------------------------------------------------
> What is happening to 5(27) and 6 at Omaha?

#6 is headed east at Red Oak, IA toward an uncertain fate.  Meanwhile #5 has reversed direction and gone back to Ottumwa at Restricted Speed, where it is just now arriving.  Perhaps our local correspondent RutledgeRadio can look into the matter and give us an update?



Edited 3 time(s). Last edit at 06/27/15 14:35 by illini73.



Date: 06/27/15 14:59
Re: #5(26) service disruption - washout west of Ottumwa, IA
Author: GenePoon

Oh, and as for "uncertain," Train 5(27) is approaching Kewanee IL, about 50 min. late.

...but just think, it's a clean train with full provisions, and a crew that will be good to Omaha!



Edited 1 time(s). Last edit at 06/27/15 15:15 by GenePoon.



Pages:  [ 1 ][ 2 ] [ Next ]
Current Page:1 of 2


[ Share Thread on Facebook ] [ Search ] [ Start a New Thread ] [ Back to Thread List ] [ <Newer ] [ Older> ] 
Page created in 0.1328 seconds