Sloterdijk train collision

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
Sloterdijk train collision
The two trains involved in the collision near Westerpark
The two trains involved in the collision near Westerpark
Date 21 April 2012 (2012-04-21)
Time 18:30 local time (16:30 UTC)
Location Sloterdijk, Amsterdam
Coordinates Lua error in package.lua at line 80: module 'strict' not found.
Country Netherlands
Rail line Oude Lijn
Operator Nederlandse Spoorwegen
Type of incident Head-on collision
Cause Suspected SPAD
Statistics
Trains 2
Passengers 136
Deaths 1
Injuries 116 (12 critical, 43 or 44 serious, < 60 minor)
Route map
To Amsterdam Muiderpoort
Amsterdam Centraal
Singelgracht
Site of accident
Isolatorweg
A10 motorway
Amsterdam Sloterdijk
Amsterdam Sloterdijk (Hemboog)
De Vlugtlaan
Amsterdam Metro Lijn 50
Westpoort
To Schiphol
To Den Helder
To Haarlem

On 21 April 2012 at 18:30 local time (16:30 UTC), two trains collided head-on at Westerpark, near Sloterdijk, in the west of Amsterdam, Netherlands. Approximately 117 people were injured, one of whom later died in a hospital. The collision is thought to have been caused by the driver of one of the trains having passed a red signal.

Accident

In the early evening a local train (an NS Sprinter Lighttrain) had just left Amsterdam Centraal and collided with a double-decker NS VIRM Intercity train travelling in opposite direction on the same track. Initial reports varied with potentially between 33 and 136 passengers injured, with up to 20 of them seriously although a member of the fire service later corrected this to 56. The actual figures were reported at 117 injuries (13 critical, 43 or 44 serious, less than 60 minor).[1][2][3][4][5] On 22 April, a 68-year-old woman died from her injuries.[6] There were sixteen people still in hospital.[7][8] On Wednesday 23 May, the last train victim in hospital was sent home.[9]

The trains involved were an NS Class 2600 electric multiple unit, number 2658,[10] and an NS VIRM double-deck electric multiple unit, number 8711.[11][12] Neither of the two trains derailed. Passengers were reported to have been thrown against walls, seats, windows, and other passengers.[3][4] Just before the crash, witnesses said one of the trains sounded a long hoot of its horn.[4] Photographs show that the VIRM unit received moderate damage, with deformation at the rear of the first and front of the second carriage.

The accident occurred between Amsterdam Centraal and Amsterdam Sloterdijk stations, near Westerpark, suspending railway services between Amsterdam and The Hague as well as to Schiphol Airport on one of the busiest rail routes in the Netherlands. The local train was travelling between Amsterdam and Uitgeest whilst the Intercity train was travelling between Den Helder and Nijmegen.[2][3] By Sunday afternoon, traffic was partially restored with a full service expected by that evening. The stretch of line where the accident occurred is where trains do not travel at full speed.[7] It is estimated that at the moment of the collision the intercity was travelling at 25–30 km/h (16–19 mph) and the local train at about 20 km/h (12 mph). [13] Bus services were laid on to get people to their destinations during the suspension.[4]

<templatestyles src="Template:Quote_box/styles.css" />

Ik vrees dat ik een rood sein heb gemist.
I fear I missed a stopping signal.
– Driver of the SLT train.[14]

A reporter from de Volkskrant travelled on board the SLT train, immediately behind the cab. He reported the driver of that train stated she feared that she had just missed a red signal.[14]

Emergency response

Location of Sloterdijk in Amsterdam
File:Treinongeluk Westerpark - Schade aan de Intercity.JPG
Damage to the cab of the Class 8700 after the other train had been removed

Emergency services were swiftly on the scene. Many people were rescued from the train wreckage either by using cranes or by being placed in a protective wrap, with some carried out on stretchers. A trauma helicopter was used to take some of the people to a nearby hospital. Many of the injured were treated on a bridge nearby. Those that had only minor injuries were taken to an Amsterdam hotel. People were reported to have suffered broken bones, bruising and neck injuries.[1][3][4]

Investigations

Two separate investigations are being carried out into whether the train collision was by human error or by a technical fault on one of the trains. By 22 April, the damaged trains had been towed away by locomotives allowing technicians to inspect the track for damage. The director of Nederlandse Spoorwegen, nl (Bert Meerstadt), stated it was still too early to guess the actual cause of the incident and it was best to await the concluding observartions of the researches.[7] The Dutch Safety Board (DSB, in Dutch: Onderzoeksraad Voor Veiligheid, OVV) is conducting one of the investigations,[15] whilst the other is being conducted by the Human Environment and Transport Inspectorate (Inspectie Leefomgeving en Transport, ILT).[16] The data recorders were recovered from both trains.[8]

ILT accident research

The circumstance the driver may have failed to obey a signal at danger was incorporated in the ILT's researches. However, Transport Minister Melanie Schultz van Haegen said to await further researches to see if the initial findings should be confirmed.[17] De Telegraaf reports that the driver may not face prosecution however as a report submitted by ProRail, the operator of the line, to the ILT, showed the signal in question was part of an older system and it is guessed that if it had been one of the more modern signals, fitted with upgraded safety equipment, the train would have stopped in time.[18]

DSB researches

The Dutch Safety Board research overlooked a number of questions. In particular, they investigated why the trains collided as well as the accident caused over 100 injuries and one fatality considered the marginal speed at the crash site. Prevention of accidents starts with an accurate time schedule. The presence of signal at dangers in regular circumstance has had little priority in the past . The driver as well as the signalman could have intervened but the DSB put in question why they did not do so or why the security system did not activate. Finally it continued to also focus on the visibility of the actual signal.[19]

In December 2012 DSB published its final report.[13] It deduced the accident could be reduced in the driver of the local train missing a signal at danger. The driver fairly expected a stopping signal, but she could have been distracted by a freight train passing nearby. That particular train only carried a single rear light, which she wanted to report.

Shortly after passing the signal at danger the safety system allowed the local train to accelerate to 60 km/h (37 mph). This was the speed limit transmitted to the intercity. Under normal circumstances the second train entering a section of track should short the track circuit, giving both trains a warning, but because of a set of points in the track this didn't happen until the local train passed the points. When the respective drivers suspected the preceding danger, the intercity train travelled at 53 km/h (33 mph) and the local train at 43 km/h (27 mph). By applying the emergency brake the trains managed to decelerate to 25–30 km/h (16–19 mph) and 20 km/h (12 mph) respectively.

There were several contributing factors to the cause and severity of the collision. Because of scheduled maintenance only a single track was available between the lower level platforms of Amsterdam Sloterdijk and Amsterdam Centraal station. In the modified timetable the intercity and the local train were supposed to use that short section of single track only three minutes after each other, for which the local train was supposed to wait for one minute at the signal before passing. Three minutes is the minimum time interval for passages over single track sections allowed by regulation. Because of a delayed freighter train the intercity was two minutes late, causing the trains to arrive at the single track section simultaneously.

The railyard the collision approached is protected using ATB First Generation, which only warns for signals at danger and enforces a low approach speed. An improvement, ATB-Vv (Verbeterde versie or Improved version) exists and could have stopped the local train before passing the signal. Although this system had been installed on the train and the signal in question was planned to support ATB-Vv, it had not been installed there yet. The DSB questioned the slow rate at which ATB-Vv is implemented in the Netherlands.

Despite both trains collided at a low speed the number and severity of the injuries was considerable. After the collision people were catapulted through the train and hit objects such as panels, seats and tables, causing severe injuries, and a single fatality. The DSB argued those objects have not been adequately designed for possible crashes. It recommended train constructors to consider an improved crash-proof design in passenger carriages.

Aftermath

Prorail and NS paid indemnification to alleged victims. One person tried to claim for a Stradivarius violin, which turned to be an iPad.[20]

See also

References

  1. ↑ 1.0 1.1 Lua error in package.lua at line 80: module 'strict' not found.
  2. ↑ 2.0 2.1 Lua error in package.lua at line 80: module 'strict' not found.
  3. ↑ 3.0 3.1 3.2 3.3 Lua error in package.lua at line 80: module 'strict' not found.
  4. ↑ 4.0 4.1 4.2 4.3 4.4 Lua error in package.lua at line 80: module 'strict' not found.
  5. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  6. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  7. ↑ 7.0 7.1 7.2 Lua error in package.lua at line 80: module 'strict' not found.
  8. ↑ 8.0 8.1 Lua error in package.lua at line 80: module 'strict' not found.
  9. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  10. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  11. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  12. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  13. ↑ 13.0 13.1 Lua error in package.lua at line 80: module 'strict' not found.
  14. ↑ 14.0 14.1 Lua error in package.lua at line 80: module 'strict' not found.
  15. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  16. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  17. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  18. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  19. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  20. ↑ Lua error in package.lua at line 80: module 'strict' not found.

External links

Retrieved from "https://infogalactic.com/w/index.php?title=Sloterdijk_train_collision&oldid=714266450"