Clapham Junction rail crash

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
Clapham Junction rail crash
Clearing up after the collision
Clearing up after the collision
Date 08:10, 12 December 1988 (UTC) (1988-12-12T08:10Z)
Location near Clapham Junction
Country United Kingdom
Rail line South Western Main Line
Operator Network SouthEast
Cause Unprotected wrong side signal failure
Statistics
Trains 3
Deaths 35
Injuries 69 serious, 415 minor
List of UK rail accidents by year

The Clapham Junction rail crash was a multiple train collision just south of Clapham Junction railway station in London that occurred at about 08:10 on 12 December 1988.[1] A crowded passenger train crashed into the rear of another train that had stopped at a signal, and an empty train, travelling in the other direction, crashed into the debris. 35 people died and nearly 500 were injured.

The collision was caused by a signal failure due to a wiring fault. New wiring had been installed, but the old wiring had been left connected at one end, and loose and uninsulated at the other. An independent inquiry, chaired by Anthony Hidden, QC, found that the signalling technician responsible had not been told his working practices were wrong and his work had not been inspected by an independent person. He had also worked a seven-day week for the previous thirteen weeks. Critical of the Health and Safety culture within British Rail at the time, Hidden's recommendations included ensuring that work was independently inspected and that a senior project manager be made responsible for all aspects of any major, safety-critical project such as re-signalling work.

British Rail was fined £250,000 for violations of health and safety law in connection with the accident.

Collisions

On 12 December 1988 the 07:18 from Basingstoke to London Waterloo, a crowded train made up from three four-car 4Vep electric multiple units, was approaching Clapham Junction when the driver saw the signal ahead of him change from green proceed to red danger. Unable to stop at the signal, he stopped his train at the next signal and then reported to the signalbox by telephone. He was told there was nothing wrong with the signal. At this point the following train, the 06:30 from Bournemouth, made up of a 4-REP and two 4TC multiple units, collided with the Basingstoke train. A third train, carrying no passengers and made of two four-car 4Vep units, was passing on the adjacent line in the other direction and hit the wreckage. The driver of a fourth train, coasting with no traction current, saw the other trains and managed to come to a stop behind the other two and the signal that should have protected them, which was showing a yellow caution aspect instead of a red danger aspect.[2]

As a result of the collisions, 35 people died, 69 were seriously injured and another 415 received minor injuries.[3]

Aftermath

The driver of the Basingstoke train was standing by the telephone when his train was pushed forward several feet by the collision. He picked up the receiver and spoke to the signalman, informing him of the collision and asking him to call the emergency services. The signalman immediately switched all the signals he could to 'danger', and signalled to the adjacent signal boxes he had an obstruction on the line. However he had no control over automatic signals, and was not able to stop the fourth train. He then called the Clapham Junction station manager and asked him to call the emergency services.[4] The accident had tripped the high-voltage feed to the traction current. The operator in the electrical control suspected there had been a derailment and re-configured the supply so that the nearby Wimbledon line trains could still run.[5]

Pupils and teachers from the adjacent Emanuel School were first on the scene of the disaster.[6] They were commended for their service by the then Prime Minister, Margaret Thatcher.[7] As the accident was in central London, the first calls to the Police came from members of the public, using public telephones and car-phones.[8] The first of the emergency services to arrive were the Fire Brigade, who were on scene by 08:17. From a bridge over the railway the station officer was able to see the wreckage, and immediately asked for eight fire appliances. At 08:19 and 08:20 he asked for eight ambulances and a surgical team to be sent and at 08:27 declared that it was a major incident.[9] Ambulances arrived at 08:21 and by 08:36 twelve ambulances had been sent.[10] The Metropolitan Police helicopter was used to fly doctors to the site.[11] Rescue was hampered because the railway was in a cutting, with metal fence at the top and a wall at the bottom of a wooded slope, so the local authority cut away the fence, trees and shrubs on the slope into which it cut steps. A mobile canteen was organised by the Salvation Army.[12] The last casualty was taken to hospital at 13:04 and the last body was removed at 15:45.[3]

Inquiry

An initial internal investigation showed that a wiring fault meant that the signal would not show a red danger aspect when the track circuit immediately in front of the signal was occupied.[13] Work associated with the Waterloo Area Resignalling Scheme meant new wiring had been installed,[14] but the old wiring had been left connected at one end, and loose and uninsulated at the other.[13]

An independent inquiry was chaired by Anthony Hidden, QC for the Department for Transport. A 1978 British Rail Southern Region report had concluded that due to the age of the equipment the re-signalling was needed by 1986, however approval was given in 1984 after a report of three wrong side signal failures.[15] The re-signalling project had been planned assuming more people were available and employees felt that the programme was inflexible and under pressure to get the work done.[16] Installation and testing was carried out at weekend during voluntary overtime, the technician having worked a seven-day week for the previous thirteen weeks.[17] The re-wiring had been done a few weeks previously, but the fault had only developed the previous day when equipment had been moved and the loose and uninsulated wire had created a false feed to a relay. The signalling technician who had done the work had not cut back, insulated nor tied back the loose wire and his work had not been supervised, nor inspected by an independent person as was required.[18] In particular, a wire count that would have identified that a wire had not been removed was not carried out.[19] There had been inadequate training, assessment, supervision and testing and, with a lack of understanding of the risks of signalling failure, these were not monitored effectively.[20]

Memorial at the site of the crash

Critical of the Health and Safety culture within British Rail at the time,[20] Hidden recommended that unused signal wires needed to be cut back and insulated, and that a testing plan be in place, with the inspection and testing being done by an independent person. Signal technicians needed to attend refresher courses every five years, and testers needed to be trained and certified. Management were to ensure that no one was working high levels of overtime,[21] and a senior project manager made responsible for all aspects of the project.[22] Unprotected wrong side signal failures – where the failure permitted a train to go beyond where it was permitted – had to be reported to the Railway Inspectorate.[23] Cab radios, linking driver and signalman, were recommended[24] and to begin installing public address system on existing trains that were not expected to be withdrawn within five years.[25]

Legacy

Testing was mandated on British Rail signalling work[26] and the hours of work of employees involved in safety critical work was limited.[27] Although British Rail was fined £250,000 for breach of the Health and Safety at Work etc. Act,[28] there was frustration that there was no prosecution for manslaughter. In 1996 the collision was one of the events cited by the Law Commission as reason for new law on manslaughter, resulting in the Corporate Manslaughter and Corporate Homicide Act 2007.[29]

A memorial marking the location of the crash site is atop the embankment above the railway on Spencer Park, Battersea.[30]

The Basingstoke train stopped at the next signal after the faulty signal, in accordance with the rule book. As of 1999, the rule book had not been changed. If the Basingstoke train had carried on to the next signal then the crash would not have happened (because the Basingstoke train would have been protected by a working track circuit).[31]

References

Notes

  1. Hidden 1989, pp. iv, 1, 4.
  2. Hidden 1989, pp. 23–25.
  3. 3.0 3.1 Hidden 1989, p. 5.
  4. Hidden 1989, p. 27.
  5. Hidden 1989, p. 28.
  6. Hidden 1989, p. 35.
  7. Lua error in package.lua at line 80: module 'strict' not found.
  8. Hidden 1989, pp. 33–34.
  9. Hidden 1989, p. 36.
  10. Hidden 1989, p. 38.
  11. Hidden 1989, p. 40.
  12. Hidden 1989, p. 42.
  13. 13.0 13.1 Hidden 1989, p. 51.
  14. Hidden 1989, pp. 147–151.
  15. Vaughan 2000, p. 78.
  16. Hidden 1989, p. 165.
  17. Hidden 1989, pp. 148–149.
  18. Hidden 1989, pp. 147–152.
  19. Hidden 1989, p. 62.
  20. 20.0 20.1 Hartley 2001, p. 23.
  21. Hidden 1989, pp. 166–167.
  22. Hidden 1989, corrections.
  23. Hidden 1989, pp. 120, 169.
  24. Hidden 1989, p. 171.
  25. Hidden 1989, p. 174.
  26. Vaughan 2000, p. 82.
  27. Lua error in package.lua at line 80: module 'strict' not found.
  28. Hartley 2001, p. 24.
  29. Lua error in package.lua at line 80: module 'strict' not found.
  30. Lua error in package.lua at line 80: module 'strict' not found.
  31. Tracks to Disaster, Adrian Vaughan,ISBN 0-7110-2985-7, page 84

Bibliography

  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.

Further reading

  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.

External links

Lua error in package.lua at line 80: module 'strict' not found.