9/12 #90's engines shut down in Okeechobee

Amtrak Unlimited Discussion Forum

Help Support Amtrak Unlimited Discussion Forum:

This site may earn a commission from merchant affiliate links, including eBay, Amazon, and others.
Status
Not open for further replies.

Miami Joe

Lead Service Attendant
Joined
Aug 22, 2002
Messages
420
Location
Miami,Fla
Man, was yesterday a baaad day! :(

#90 departed on time, got a phone call around 7:45 pm. The train's brakes were applied and would not release. Tried to troubleshoot over the phone, translating defect codes on the engine and relaying possible remedies. After numerous "re-boots"of the computers, the call was made to drop the lead engine, and proceed N/B.

Ten minutes later, the second engine failed. This time the engine would not "load" and the phone calls started again. Tried "re-booting" on this engine and could not get the engine to "load". :(

At 11:00 pm, it was decided to send a tech to Okeechobee by car and try to make repairs. Don't know what the problem was, but the train rolled at 1:50am, taking a 5 hr delay.

This caused #89 to stop in Tampa for crew rest, they bussed the people to Miami and the crew is dead-heading the train to Miami.

#91 arrived on time today, but #89 is still on the rail at this time. We have to build #98 and steal 3 coaches, a lounge and a mail car from #91.

So, how was your day?? :blink:
 
I left ALX here at about 20:00 and it still had not arrived...due at 15:48.
 
This one's really weird!!! :blink:

Just talked to the tech and he say that when they got to Okeechobee, that #90 was already gone. From what they heard on the radio, it seems that the engineer set the parking brake at the next station and couldn't figure out how to release them!!! Evidently, they finally got rolling again but didn't notify the tech enroute.

They techs turned back to go work the engine that wouldn't "load". Keep in mind, that after shutting down the engine, you pull the battery breaker. So, upon closing the breaker and starting the engine, you are starting with "fresh"computers. After running diagnostics, they couldn't find anything wrong and the engine "loaded".

Crazy night was had by all. I can only guess that the crew was having a "bad"day or the two engine"s computers sent error codes back and forth between them. ;)

B)
 
Status
Not open for further replies.
Back
Top