Author Topic: BNSF head on collision  (Read 2299 times)

0 Members and 1 Guest are viewing this topic.

Lenny53

  • Crew
  • *
  • Posts: 2297
  • Respect: +2061

wazzou

  • Crew
  • *
  • Posts: 6812
  • #GoCougs
  • Respect: +1736
Bryan

Member of NPRHA, Modeling Committee Member
http://www.nprha.org/
Member of MRHA


Lenny53

  • Crew
  • *
  • Posts: 2297
  • Respect: +2061

Smike

  • Crew
  • *
  • Posts: 821
  • Respect: +198
Re: BNSF head on collision
« Reply #3 on: June 28, 2016, 11:28:29 PM »
0
One guy jumped and is stable, the 3 others are missing.  Massive pile of engines and containers.

http://amarillo.com/news/latest-news/2016-06-28/large-fire-after-two-bnsf-trains-collide-derail-near-panhandle


jmarley76

  • Crew
  • *
  • Posts: 698
  • Respect: +137
    • WNCRails
Re: BNSF head on collision
« Reply #4 on: June 29, 2016, 12:05:41 AM »
0
wow...  :o :|

C855B

  • Crew
  • *
  • Posts: 11422
  • Respect: +2886
Re: BNSF head on collision
« Reply #5 on: June 29, 2016, 12:14:59 AM »
0
I got a chill reading this in today's news. Eerily similar in location and consequences to the UP head-on four years ago almost to the day - in Goodwell, OK, on the ex-RI line not even 100 miles to the north.
...mike

http://www.gibboncozadandwestern.com

Note: Images linked in my postings are on an HTTP server, not HTTPS. Enable "mixed content" in your browser to view.

There are over 1000 images on this server. Not changing anytime soon.

eja

  • Crew
  • *
  • Posts: 1526
  • Gender: Male
  • Respect: +278
Re: BNSF head on collision
« Reply #6 on: June 29, 2016, 01:19:15 AM »
0
What is that term ... corn field meet?  How can this happen in today's technological wonderful world?

My sympathy to the crews and their families.

eja


Missaberoad

  • Crew
  • *
  • Posts: 3831
  • Gender: Male
  • Ryan in Alberta
  • Respect: +1376
Re: BNSF head on collision
« Reply #7 on: June 29, 2016, 01:42:36 AM »
0
What is that term ... corn field meet?  How can this happen in today's technological wonderful world?

With the transcon being CTC there is two main possibilities. Either the system its self failed (very unlikely since nearly any failure will set everything to stop) or crew error (much more likely).

It is impossible for the dispatcher to authorize two trains on the same track. Likely a distracted or incapacitated crew missed or ignored a signal when the other train was already in the same block.
At the end of the day the entire system still relies on the crew being attentive and unfortunately one moment of neglect can cause something like this.

Mind you this is all speculation based on knowledge of the method of control, and past accidents. It will be interesting to see the results of the investigation.

My stomach sank reading about this, the very last thing anyone wants to happen. 
« Last Edit: June 29, 2016, 01:48:39 AM by Missaberoad »

Blazeman

  • Crew
  • *
  • Posts: 1306
  • Respect: +65
Re: BNSF head on collision
« Reply #8 on: June 29, 2016, 10:16:08 AM »
0
Is it a double-track main there?  If one crew missed their stop signal, wouldn't the train have encountered a closed switch prior to the collision? Not being that close to how real trains operate, am I coming at this from a wrong perspective?

Have to think PTC would have stopped this from happening. Agreed it's technically challenging to develop and implement, RR industry image will be hammered once again for seeking extension of the deadline.

At the same time, FRA recently came out with a proposal to retain two-man crews only to encounter opposition from Ed Hamberger and AAR that it's not necessary or proven safer. I can't say which side has their point of view bolstered by this tragedy. Both lose when this kind of event occurs, but it's others who suffer the tragedy.

Missaberoad

  • Crew
  • *
  • Posts: 3831
  • Gender: Male
  • Ryan in Alberta
  • Respect: +1376
Re: BNSF head on collision
« Reply #9 on: June 29, 2016, 12:16:31 PM »
0
Is it a double-track main there?  If one crew missed their stop signal, wouldn't the train have encountered a closed switch prior to the collision? Not being that close to how real trains operate, am I coming at this from a wrong perspective?

It is double track and your line of thinking is correct. unfortunately a Locomotive is usually heavy enough to spread the points rather then derail in this situation.

and depending on how close the collision happened to the Controlled location it may not have allowed the RTC time to react (assuming his CTC system shows switch position and occupancy within controlled locations)

ksmiley

  • Crew
  • *
  • Posts: 48
  • Respect: +24
Re: BNSF head on collision
« Reply #10 on: July 06, 2016, 07:48:23 AM »
0
I was working in the Amarillo/Panhandle TX area a couple of years back and while I was there, BNSF had two accidents within a 10 mile stretch. One was a stack train that blew over, yes the winds get strong down there, and the other was a derailment that the opposing direction train got caught up in. Signaling and crews are great but sometimes stuff happens.

lock4244

  • Crew
  • *
  • Posts: 4586
  • Respect: +885
    • My train pics
Re: BNSF head on collision
« Reply #11 on: July 06, 2016, 10:03:37 AM »
0
There were two locomotives sitting on a siding almost at the exact point of impact... they were parked there after being involved in a grade crossing accident. Somewhat cursed.

jmarley76

  • Crew
  • *
  • Posts: 698
  • Respect: +137
    • WNCRails
Re: BNSF head on collision
« Reply #12 on: July 06, 2016, 04:00:37 PM »
0
There were two locomotives sitting on a siding almost at the exact point of impact... they were parked there after being involved in a grade crossing accident. Somewhat cursed.

Sounds like it...  :|