2021 Salisbury rail crash

2021 Salisbury rail crash
Aerial view of the crashed trains Diagram of the crash by the Rail Accident Investigation Branch
Details
Date	31 October 2021 (2021-10-31) 18:45
Location	Fisherton Tunnel 1 mi (1.6 km) north east from Salisbury
Coordinates	SU 150 309 51°04′39.2″N 1°47′08″W / 51.077556°N 1.78556°W / 51.077556; -1.78556
Country	United Kingdom
Line	Wessex Main Line West of England Main Line
Operator	Great Western Railway South Western Railway
Owner	Network Rail
Service	Portsmouth Harbour–Bristol Temple Meads (GWR) London Waterloo–Honiton (SWR)
Incident type	Sidelong collision and derailment
Cause	Signal passed at danger due to low railhead adhesion
Statistics
Trains	2
Passengers	92
Crew	4
Deaths	0
Injured	14 (1 serious)
Location diagram Wessex Main Line to Southampton West of England line to Basingstoke N S Laverstock North and South Junctions Salisbury Tunnel Junction Fisherton Tunnel Salisbury Wessex Main Line to Bristol Temple Meads West of England line to Exeter St Davids This diagram: view talk

On 31 October 2021, two trains, travelling on converging lines, collided at Salisbury Tunnel Junction, approximately 1 mile (1.6 km) northeast of Salisbury railway station in Wiltshire, United Kingdom. Fifteen people, including one of the train drivers, were taken to hospital.

Incident[]

158762 pictured in 2021

158763 pictured in 2020

159102 pictured in 2010

On 31 October 2021, Great Western Railway's (GWR) 17:08 Portsmouth Harbour to Bristol Temple Meads service (reporting number 1F30) operated by two-carriage Class 158s 158762 and 158763 was passing through Salisbury Tunnel Junction where the Wessex Main Line converges with the West of England Main Line. At the same time, the South Western Railway's (SWR) 17:20 London Waterloo to Honiton service (reporting number 1L53) operated by three-carriage Class 159 159102 was approaching the junction.^[1][2] The SWR train failed to stop at signal SY31, 240 yards (220 m) from Salisbury Tunnel Junction, which was displaying a red aspect.^[3][4][5]

At 18:45, the leading carriage of the SWR train collided into the side of the third carriage of the GWR train, causing both trains to derail as they entered Fisherton Tunnel. The rear two carriages of the GWR train and front two carriages of the SWR train were derailed.^[5][4]

Emergency services, including Wiltshire Police and the British Transport Police, attended the scene,^[6] as did the Dorset & Wiltshire Fire and Rescue Service who declared a major incident. National Police Air Service and HM Coastguard despatched helicopters to the scene.^[7] The railway lines through the tunnel were closed as a result of the incident.

The accident was the first involving a collision between two moving in-service passenger trains in the United Kingdom since the Ladbroke Grove rail crash on 5 October 1999.^[8]

Passengers and crew[]

Of the 92 passengers on board the trains,^[5] 13 were injured.^[9] All bar one were taken by ambulance to Salisbury District Hospital.^[10] Four of those taken to hospital were admitted, with three of them being discharged later, and nine were treated for their injuries before being sent home.^[10] Thirty other people walked to a temporary casualty centre established in a local church.^[10] The driver of the SWR train was initially trapped in his cab before being freed and taken to hospital, where his injuries were described as life-changing.^[7][10][11] He was flown to Southampton General Hospital for treatment.^[5]

Aftermath[]

The accident closed both the Wessex Main Line and West of England Main Line, affecting services between Portsmouth Harbour and Westbury and between Basingstoke and Exeter St Davids respectively.^[12] Network Rail stated that the track at the junction required heavy refurbishment and that the track through the tunnel may also need to be relaid.^[13] Unit 158762 was the leading unit of 1F30.^[5] It was not damaged,^[14] and was removed by rail on 4 November. One of the remaining five carriages was removed from the site that day. It was lifted from the railway by a large crane and removed by road.^[15] Class 59 locomotive 59003 was used to drag the derailed carriages out of the tunnel.^{[citation needed]} The A30 London Road was closed until 9 November to allow for the recovery of the carriages and for investigators to carry out their work.^[16] The line through the tunnel reopened on 16 November.^[17]

Investigations[]

The Rail Accident Investigation Branch (RAIB) deployed a team of inspectors to the scene. The Office of Rail and Road are also investigating.^[18] The British Transport Police also opened an investigation.^[19]

On 2 November the RAIB stated that initial evidence indicated that, although the SWR driver had applied the brakes, his train had failed to stop at a signal and collided with the GWR train; wheel slide, as a result of low railhead adhesion, was the most likely cause.^[3][20] Announcing a formal investigation on 3 November, the RAIB said that the On Train Data Recorder showed that the driver had made an emergency brake application twelve seconds after he initially applied the brakes, and that a further emergency brake demand had been made by the Train Protection & Warning System fitted to the train.^[4]

RAIB will examine how Network Rail managed the risk of loss of adhesion at the track site and also any SWR policy for preventing or mitigating wheel slip on their trains. SWR commented that its driver had acted in an "impeccable way in a valiant attempt to keep passengers safe".^[21] The West of England Line had not had a Rail Head Treatment Train over it since 29 October, although one had been scheduled to travel over the line before the accident occurred.^[22] An interim report was published on 21 February 2022.^[9]

RAIB Interim report[]

The interim report found that the driver of 1L53 approached signal SY29R at 90 miles per hour (140 km/h) and shut off power. The line at this point was on a 1 in 169 falling gradient. The signal was displaying a double yellow aspect. About a mile (1,600 m) past the signal the train was travelling at 86 miles per hour (138 km/h) and a brake application was made and the wheels began to slide. A full service brake application was followed by an emergency brake application. As the train approached signal SY31, the overspeed sensor fitted to the train detected that the train was travelling in excess of the 34.5 miles per hour (55.5 km/h) permitted when a red aspect was displayed and the TPWS demanded emergency braking, which was already being applied by the driver. The front carriage of 1L53 collided with the rear carriage fo 1F30 at a speed between 52 and 56 miles per hour (84 and 90 km/h).^[9]

The collision caused the coupling between units 158762 and 158763 to break. The unit at the front of the train was undamaged and came to a halt inside the tunnel. Both carriages of the unit at the rear of 1F30 were derailed against the tunnel wall. The front two of the three carriages of 159102 were derailed. The driver of 1L53 was knocked unconscious and trapped in his cab. The alarm was raised by the driver of 1F30 using the GMSR radio system.^[9]

Subsequent analysis of the railway line approaching Salisbury Tunnel Junction revealed that the line was contaminated by the residue of fallen leaves between 80 miles 32 chains (129.39 km) and 82 miles 36 chains (132.69 km) (distances measured from London Waterloo). A coefficient of friction of between 0.2 and 0.02 was recorded, with most of the readings towards the lower end of the scale. The last Rail Head Treatment Train had passed over the line at 11:06 on 30 October, and the next one was scheduled to pass over at 23:00 on 31 October. The gap of 36 hours was in excess of Network Rail Wessex's requirement to treat the line at least once every 24 hours.^[9]

Reporting of the story[]

A Rail Head Treatment Train cleaning tracks at the crash site during a scheduled visit a few weeks later

Initial reports of the accident, based on a leaked Network Rail log, led to highly inaccurate reporting of the accident in its immediate aftermath. The Evening Standard reported that a derailed locomotive had been left a sitting duck for seven minutes after the rear carriage of a train derailed and was then run into by another train after signalling failed. Rail editor Nigel Harris pointed out that the only facts in the story were the location and services involved. The leak led to the MailOnline reporting similarly, with a "senior Network Rail manager" quoted as saying "According to my system, the signalling system was aware seven minutes before impact. It should've automatically stopped the train. It should've automatically set all signals to red. If the driver didn't see the signal, the system should've made the train stop." An initial statement put out by Network Rail also contained incorrect facts. Although it was quickly corrected, Harris said that "the genie was already out of the bottle". The Network Rail log initially reported that the GWR driver had reported hitting an obstruction and derailing. The log was updated seven minutes later to record the collision, which is where the press got their "seven minutes sitting duck" scenario. Under the current system, Train Operating Companies, the British Transport Police, and the Office of Rail and Road can all issue statements.^[23] Rail contributor Christian Wolmar also criticised the early coverage. In his opinion, the initial errors were made worse by Network Rail's Safety and Engineering Director Martin Frobisher, who appeared on BBC Radio 4's Today programme on 1 November and did not correct any of the errors at a time when, according to Wolmar, he must have known them to be untrue. Wolmar praised the RAIB for publishing its initial report just three days after the accident.^[24]

See also[]

• 1906 Salisbury rail crash

Further reading[]

• "Why can leaves cause train delays? The chemistry of leaves on the line". Compound Interest. 22 October 2018. Retrieved 1 December 2021.

References[]