Zanthus train collision

The Zanthus train collision occurred at a crossing loop on the Trans-Australian Railway between Perth and Sydney on 18 August 1999. It is located 739 km (459 mi) east northeast of Perth and 202 km (126 mi) east of Kalgoorlie in Western Australia, on the Nullarbor Plain.

Zanthus accident - showing 'Indian Pacific' passenger train and derailed carriages

Zanthus train collision
Details
Date18 August 1999
LocationZanthus, Western Australia
739 km (459 mi) ENE from Perth, Western Australia
CountryAustralia
LineTrans-Australian Railway
OperatorNational Rail Corporation, Great Southern Rail
Incident typeCollision
CauseDriver error
Statistics
Trains2
Deaths0
Injuries21

Incident

On 18 August 1999 an eastbound freight train was waiting at the departure end of the crossing loop for the westbound Indian Pacific passenger train to pass through.[1]

The second engineman was waiting at the control panel for the points for the opposing train to pass through. Out of habit he had the control panel box unlocked and opened. Unfortunately, out of habit, he pressed the button to operate the points at an inappropriate time, and the opposing train was diverted at a speed of about 40 km/h (25 mph) into the loop where it could not stop in time to avoid a head-on collision. The actual speed of impact as recorded by the locomotive data logger on NR 15 was 27 km/h.

Injuries and damage

Twenty-one passengers and crew from the Indian Pacific were airlifted by the Royal Flying Doctor Service to Kalgoorlie Hospital from the remote Coonana airstrip, 40 km (25 mi) from the crash site. Only two passengers were admitted for overnight observations. Westrail provided two Prospector railcars to transfer the remainder of the passengers back to Kalgoorlie.

All nineteen coaches of the Indian Pacific received varying degrees of damage, from minor internal damage to the write-off of luggage/smoking car HM311; some abandoned wrecked carriages are still at the site.[2] At the time, Great Southern Rail estimated the damage to the coaches to be of the value of $5 million. National Rail Corporation estimated the damage to locomotives NR15 and NR51 at around $1 million.

Aftermath

Since the accident, the operation of the points at this and other crossing loops has been altered so that the point indicator lights will not operate until the access process is completed,[3] and this gives all trains time to stop at the red point indicator lights.

The simplified overview of process is:

  1. access box - 120-180 second delay all line points are/changed to red
  2. door opens
  3. 60-90 second delay until point control inputs are accepted, points can then be changed.
  4. close door/seal box, lights are changed to indicate point positions.

All traffic then proceeds as directed.

This accident happened because the points were not fully interlocked, and were merely a kind of power-assisted hand lever, with automatic normalisation.

gollark: *Or* I can ignore it and add it as an alias in potatOS...
gollark: ```PotatOS OS/Conveniently Self-Propagating System/Sandbox/Compilation of Useless Programs We are not responsible for- headaches- rashes- persistent/non-persistent coughs- virii- backdoors- spinal cord sclerosis- hypertension- cardiac arrest- regular arrest, by police or whatever- death- computronic discombobulation- loss of data- gain of data- frogsor any other issue caused directly or indirectly due to use of this product. Best viewed in Internet Explorer 6 running on a Difference Engine emulated under MacOS 7. Features:- Fortunes/Dwarf Fortress output/Chuck Norris jokes on boot (wait, IS this a feature?)- (other) viruses (how do you get them in the first place? running random files like this?) cannot do anything particularly awful to your computer - uninterceptable (except by crashing the keyboard shortcut daemon, I guess) keyboard shortcuts allow easy wiping of the non-potatOS data so you can get back to whatever nonsense you do fast- Skynet (rednet-ish stuff over websocket to my server) and Lolcrypt (encoding data as lols and punctuation) built in for easy access!- Convenient OS-y APIs - add keyboard shortcuts, spawn background processes & do "multithreading"-ish stuff.- Great features for other idio- OS designers, like passwords and fake loading (set potatOS.stupidity.loading [time], est potatOS.stupidity.password [password]).- Digits of Tau available via a convenient command ("tau")- Potatoplex and Loading built in ("potatoplex"/"loading") (potatoplex has many undocumented options)!- Stack traces (yes, I did steal them from MBS)- Backdoors- er, remote debugging access (it's secured, via ECC signing on disks and websocket-only access requiring a key for the other one)- All this useless random junk can autoupdate (this is probably a backdoor)!- EZCopy allows you to easily install potatOS on another device, just by sticking it in the disk drive of another potatOS device!- fs.load and fs.dump - probably helpful somehow.```
gollark: <@236628809158230018> https://pastebin.com/RM13UGFa
gollark: It, um, teaches you not to trust any OSes?
gollark: Not even Windows is this crazy… yet.

See also

Notes
  1. "Rail Safety Investigation Report 001 - Collision between Indian Pacific Passenger Train 3AP88 and Freight Train 3PW4N". Australian Transport Safety Bureau, Department of Transport and Regional Services, Government of Australia. Retrieved 9 June 2007.
  2. "Zanthus train wreck". The Degree Confluence Project. Retrieved 30 September 2008.
  3. "Independent Investigation report section" (PDF). section 1.12.2 pg 20.CS1 maint: others (link)

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.