[SystemSafety] Train wreck

Bruce Hunter brucer.hunter at gmail.com
Wed Nov 7 23:52:24 CET 2018


It's good our Australian press got it correct this time. There was a
similar incident in Tasmania earlier this year which was reported as a "
driverless train". https://www.abc.net.au/news/2018-09-21/train-derails-in-
devonport/10289726. Australia does not quite yet have autonomous trains.
There is current trial of "driverless" ore trains by a different mining
company the Pilbara and Sydney Metro is being commissioned.

BHP trains have been entered in the Guinness Book of Records as the world's
longest trains, so when they derail it's not a pretty sight. People in Port
Hedland keep an ore train timetable so not to get caught at the railway
crossings when they pass.

Remote derailment at safe location is probable the safest option as post
loss-of-control consequence mitigation for these run-away trains. Incidents
of drivers leaving the cab do raise Human Factors considerations and the
thorny issue of Human Reliability Assessment.

Could this be a new topic for discussion?

Bruce Hunter

On Wed, 7 Nov 2018 at 21:45, Peter Bernard Ladkin <ladkin at causalis.com>
wrote:

> Some "nice" video of the world's largest/longest train wreck.
>
> No one was hurt. The driver had stepped out of the cab to do something
> trackside and the train took
> off on its own, and was deliberately derailed 92km later.
>
>
> https://www.theguardian.com/australia-news/2018/nov/07/mangled-wreckage-of-bhp-runaway-train-revealed-in-video-footage
>
> PBL
>
> Prof. Peter Bernard Ladkin, Bielefeld, Germany
> MoreInCommon
> Je suis Charlie
> Tel+msg +49 (0)521 880 7319  www.rvs-bi.de
>
>
>
>
>
> _______________________________________________
> The System Safety Mailing List
> systemsafety at TechFak.Uni-Bielefeld.DE
> Manage your subscription:
> https://lists.techfak.uni-bielefeld.de/mailman/listinfo/systemsafety
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.techfak.uni-bielefeld.de/mailman/private/systemsafety/attachments/20181108/33bfc473/attachment.html>


More information about the systemsafety mailing list