This is a close call

Cadmaster's picture

Thought that I would pass this along to the group as a whole. A friend sent this to me this morning; see the email from the engineer of the train.

"Subject: Two Trains meeting where they’re not suppose to be at the same time.

Two Trains meeting where they’re not suppose to be at the same time.   The KCK-Lincoln, a West Bound Train was stopped on Main 2 at Water Works, located just north of St. Joseph Missouri.  My Train the KCK-Pasco, also a West Bound Train was on Main 1 going through Water Works.  Both these trains had excessive “Height and Width” cars.  The Train on Main 2 was shipping Windmill Generators and my train contained Boeing Aircraft Fuselages.   Note in the photo that there is less than two inches of clearance!  The saving grace is this… If it weren’t for the fact I was running on an approach following another West Bound train certain catastrophe would have been imminent.  It certainly would have derailed and destroyed both trains and possibly lives could have been lost.  Luckily, as I was rounding the bend I was able to see a long ways up the track and noticed the train on Main 2 had High Wide Cars, and I was able to get my train stopped.   If I would have been going track speed there would have been no way of stopping.   Someone from above was certainly watching out for me that day and it wasn’t the Dispatchers."

I could only imagine what the insurance claim would have been like on that kind of damage!!

Comments

  Your lucky.  Another coat

  Your lucky.

 Another coat of paint on the freight would have changed the whole scenario.

     Pete

Talk about your lucky breaks!

Wow! that must have been one time where the crews whished they didn't come to work.

What kind of delays were caused by this?

I'm glad no one was injured, and the loads were un-damaged.

The question that comes to my mind is what did they do about the

dispatchers?  If a train has an accident, you can bet that everyone is going to look at the crew under a microscope to make sure it is avoidable in the future and if a rule was broken, someone may get some time off.  To my mind it is unexcusable that dispatchers don't know the dimensions of their oversize loads, or else the comunication is such that they are not made aware of the oversize loads of another train that they will meet and allow them to plan for the meet where there is adequate clearance.

caboose14's picture

Yikes!

Yeah I think we would have really missed those Next-Gen 737s at the Renton Plant come Monday morning! Glad everything worked out all right!

Kevin Klettke CEO, Washington Northern Railroad wnrr@comcast.net
http://wnrr.net

You are  correct Russ, there

You are  correct Russ, there is probably no or a weak system for the communications for this to even be prevented. In my former life as a quality assurance manager my goal was to prevent errors from happening. It was always process or system driven, meaing it wasn't people making mistakes, something in the process allowed a bad decision, or no decision, to be made.  (Sabotage or pure negligence excused). It would be interesting to see what if anything was done to prevent this from happening again. My guess, since there was no incident, corporate America, or Canada, will ignore it and move on.  

  If there has not been a

  If there has not been a special instruction/message for the train crews - something got 'lost' between the special loads folks and the dispatcher.  When I worked for the railroad, there was a special file opened for every 'high/wide' load, and the entire route was mapped out.  On the old CB&Q, it was a 'Cravens File'.

  The train crew was issued a special message with their clearance card/train orders describing the special load and any restrictions(speed/tracks).  Any other train operating in that territory was also issued that mesage.  Usually meets were setup on tangent trackage and the opposing train would be stopped.  I worked a train with some kind of transformer/boiler assembly for a power plant and I remember having to stop and then crawl through the Prescott, WI swing bridge with the conductor/brakeman watching the load.

Jim

I think it depends on the company, Pirosko.

Before I retired, I worked on a/c units on mow equipment, mainly ballast tampers, but some construction equipment for both the BNSF and UP as an outside vendor.  I also did warranty repairs on Carrier refrigeration equipment installed on mechanical reefers for Amtrak, BNSF, & UP.  In the case of U.P. and Amtrak, both companies told me where the equipment was and trusted me to know all applicable "blue flag" safety rules.  In the case of BNSF, I always had a supervisor with me to make sure I did things safely, and that I was always briefed on appropriate safety laws for what ever siding the equipmewnt was located on.  For instance on some sidings, the switches were locked out, so I could work on the equipment without having to worry about trains coming by on the mainline.  Other sidings were controlled by a dispatcher, so I had to keep an eye out for trains and get off the equipment and stand clear any time a train approached in case the switch was inadvertantly thrown causing the train to crash into the equipment on the siding.  I just found BNSF's attitiude about safety to be ramped up to the next level compared to the other two railroads I worked on.  Unless those are leased pool units, I suspect that incident ocurred on the BNSF and I would expect that if the engineer reported it to his supervisors, the BNSF would take steps to keep such an incident from recurring.

Well Russ, of course you are

Well Russ, of course you are correct, it does depend on the company. Maybe I should not have used such a wide paint brush with my comment. Once bitten, twice shy is the saying? I think I may have been chewed up once or twice!  

Steve

Close call

As a stockholder, thanks for your efforts!!  Glad no one was hurt!  I always wonder why nobody ever wonders what roll the dispatcher had any given mishaps.  From what I've been told, when accidents happen, it usually involved more than one thing going wrong.


>> Posts index

User login