1956 Santiago rail crash

The 1956 Santiago rail crash occurred on February 14, 1956, at 4:00 a.m.[1] near the Chilean capital Santiago on the branch to Cartagena and killed 23 people.

1956 Santiago rail crash
Details
DateFebruary 14, 1956
4:00 a.m
LocationSantiago
CountryChile
LineSantiago - Cartagena
OperatorEmpresa de los Ferrocarriles del Estado
Incident typerear collision
CauseSignal passed at danger
Statistics
Trains2
Deaths23
Injuries198

Two trains left the capital twelve minutes apart. Seven kilometres into their journeys, the second train ran into the back of the first; destroying a wooden, third-class carriage. 23 people were killed and 198 injured. President Carlos Ibáñez del Campo ordered an immediate enquiry; the driver of the rear train was found to be at fault.

The accident happened just seven months after a very similar accident at San Bernardo twenty kilometers south of the city killed 38 people.

Sources

gollark: Originally only for 32-bit x86 CPUs, the first x86_64 installation ISO was released in April 2006.
gollark: Inspired by CRUX, another minimalist distribution, Judd Vinet started the Arch Linux project in March 2002. The name was chosen because Vinet liked the word's meaning of "the principal," as in "arch-enemy".
gollark: Arch Linux has comprehensive documentation, which consists of a community wiki known as the ArchWiki.
gollark: Pacman, a package manager written specifically for Arch Linux, is used to install, remove and update software packages. Arch Linux uses a rolling release model, meaning there are no "major releases" of completely new versions of the system; a regular system update is all that is needed to obtain the latest Arch software; the installation images released every month by the Arch team are simply up-to-date snapshots of the main system components.
gollark: Arch Linux is a Linux distribution created for computers with x86-64 processors. Arch Linux adheres to the KISS principle ("Keep It Simple, Stupid"). The project attempts to have minimal distribution-specific changes, and therefore minimal breakage with updates, and be pragmatic over ideological design choices and focus on customizability rather than user-friendliness.

References

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