Western Railroad Discussion > Two UP trains collide in Missouri

http://www.komu.com/news/mshp-trains-collide-in-gasconade-county-causing-injuries

Not much info out as of yet, one train reportedly rear-ended the other near Morrison on the Jeff City Sub. Happened around 1:40pm, and reported to have 2 injuries. Amtrak obviously interrupted for the Missouri River Runner as well.

Photo credit @KRCG13 twitter.



Edited 2 time(s). Last edit at 08/15/17 14:44 by djm448.

---

---

---

"Initial reports said that rail cars were off the tracks and lying on both sides of the track, according to Reinsch, although that has not been confirmed."

I think the photos confirm that.

Pump



Edited 1 time(s). Last edit at 08/15/17 14:34 by UPTRAIN.

Very graphic pictures. How were you able to get up that close among the wreckage?

Not a good day for UP in the Heartland. A northbound from Coffeyville (KS) struck a low-boy with a large Cat track-hoe high-centered on the grade crossing on Peoria St. in Paola about 11:30 this morning. No injuries.

Note that above photos he credits them to the local TV stations twitter feed.
In other words, I doubt he took them.

Stephen

Looks like a violation of a restricted speed situation.

How do things like this happen in this day and age?

Bill Deaver
Tehachapi, CA

MojaveBill Wrote:
-------------------------------------------------------
> How do things like this happen in this day and
> age?


That's what I don't understand.It also happens much more frequently on western roads who don't use radios as much.



Edited 1 time(s). Last edit at 08/15/17 16:10 by NS19K.

MojaveBill Wrote:
-------------------------------------------------------
> How do things like this happen in this day and
> age?

Fatigue?

Whatever the cause this certainly the motivation behind PTC. Almost looks like a red signal violation
into a train entering a siding but hard to tell from the pictures.

Out

Happened in 2 MT CTC territory. MNPPB 14 was on duty at Jefferson City at 1125, departed at 1208. QNPINP 14 on duty at 1200 in Jeff City, departed at 1239. I believe the collision would have taken place shortly before 1400. First train shows by Morrison Jct. at 1314, the next at 1342. As far as I can tell it was the QNPINP that ran into the rear of the MNPPB.

Pump



Edited 2 time(s). Last edit at 08/16/17 06:56 by UPTRAIN.

UPTRAIN Wrote:
-------------------------------------------------------
> Happened in 2 MT CTC territory. MNPPB 14 was on
> duty at Jefferson City at 1125, departed at 1208.
> QNPINP 14 on duty at 1200 in Jeff City, departed
> at 1239. I believe the collision would have taken
> place shortly before 1600. First train shows by
> Morrison Jct. at 1314, the next at 1342. As far
> as I can tell it was the QNPINP that ran into the
> rear of the MNPPB.


If lineups nowadays sucked, it would be an improvement. On duty time is generally irrelevant when considering fatigue, whether or not FRA, NTSB, and the company see it that way.

TAW

Once the restricting signal is passed at 15 mph or less as required by PTC the requirement to stop short rest solely with the crew. PTC does not keep track of other trains in the same block.

TAW Wrote:
-------------------------------------------------------
> If lineups nowadays sucked, it would be an
> improvement

This is true. It is also worth noting that both of these crews originated at their AFHT.


1ST_OUT Wrote:
-------------------------------------------------------
> Once the restricting signal is passed at 15 mph or
> less as required by PTC...

Is this on every railroad, or does it allow *up to* 20 as per GCOR? I won't say that PTC is not cut in on the Jefferson City Sub., but I will say, I would be highly surprised if it is.

Pump



Edited 1 time(s). Last edit at 08/16/17 07:00 by UPTRAIN.

MojaveBill Wrote:
-------------------------------------------------------
> How do things like this happen in this day and
> age?

Since they have cars now that will apply the brakes if one forgets to stop.

Any word on the crew? That looks like a pretty good hit to roll the locomotive. Hope they're OK.

I wonder if it would be possible to add another layer of defense by putting in some kind of proximity warning for a nearby EOT device? It would beep when a train passes on an opposing track, of course. But a one or two minute warning could save lives.

1ST_OUT Wrote:
-------------------------------------------------------
> Once the restricting signal is passed at 15 mph or
> less as required by PTC the requirement to stop
> short rest solely with the crew. PTC does not keep
> track of other trains in the same block.

Excellent point..... PTC does not keep track of other trains out there, it will only make sure you don't exceed 20mph during restricted speed. Its still up to the crew to stop within half the range of vision of anything in front of them.

The inward facing camera will tell UP what the crew was doing at the time the accident occurred. The time a crew comes on duty is no indicator of weather they are more or less fatigued. You can be tired if your called in at 12pm if the factors are right.

CS

MojaveBill Wrote:
-------------------------------------------------------
> How do things like this happen in this day and
> age?

Probably for the same reason that airplanes still crash on occasion. Stuff happens......!

The difference is that pilots usually know when then are going to work and have a lot better chance of showing up rested.

Pilots usually know when they're going to work. Ha! Usually is the key word. NOT always the case. I think there are more fatigued pilots out there than train crews. (I retired from a major airline after 40 years and spent 20 in Naval Aviation). I worry now about pilot's readiness more than ever in my life. Management doesn't care, they have insurance for such events.

Ed

Auburn_Ed Wrote:
-------------------------------------------------------
> Management doesn't care, they have
> insurance for such events.

...and folks who calculate the cost of dead and wrecked people and bent iron vs prevention.

TAW