Train overspeeding caused passenger injuries due to falling luggage

Half of the passenger injuries were as a result of falling luggage that had been stowed in the overhead luggage racks

The Rail Accident Investigation Branch (RAIB) has issued its report into a train overspeeding at Spital Junction, Peterborough, 17 April 2022.

The incident took place at around 10:20 on 17 April 2022 when the 08:20 Lumo service from Newcastle to London King’s Cross passed over three sets of points at Spital Junction at the northern approach to Peterborough station at excessive speed. The maximum permitted speed over the junction is initially 30mph (48km/h) reducing to 25mph (40km/h). The data recorder from the train indicated that the points had been traversed at a speed of 76mph (122km/h).

The speed of the train over the junction resulted in sudden sideways movements of the coaches, which led to some passengers being thrown from their seats and luggage falling from the overhead storage, with some passengers receiving minor injuries. Although the train did not derail, and no damage was caused, post-incident analysis has indicated that the train was close to a speed that would have led to it overturning, and it was likely that some of the wheels of the vehicles lifted off the rails.

Location of the incident and a schematic diagram of the main features on the north approach to Peterborough station

RAIB’s investigation found that the overspeeding was caused by the driver of train 1Y80 not reacting appropriately to the signal indication they had received on approach to the junction. This signal indication was a warning that the train was to take a diverging route ahead which had a lower speed limit than the straight-ahead route which they were expecting to take. The driver’s awareness of the signal conditions that could be presented on approach to this junction and their training were not sufficient to overcome this expectation.

RAIB found that Lumo had not assessed and controlled the risk associated with trains being unexpectedly routed on a slower, diverging route at this location and that it had not adequately trained the driver to prepare for this eventuality.

The train passed over the points leading to the Slow platform at nearly three times the permitted speed

Network Rail had also neither assessed nor effectively controlled the risk of overspeeding at locations where there is a long distance between the protecting signal and the junction itself.

The investigation also found that half of the passenger injuries were as a result of falling luggage that had been stowed in the overhead luggage racks.

Recommendations

RAIB has made four recommendations. The first recommendation is for Lumo to review its processes to ensure that it effectively controls the risk of overspeeding at diverging junctions.

The second recommendation asks Network Rail to identify junctions where there is a greater potential for overspeeding to occur and to work with operators to share information on the associated risks.

The third recommendation asks Network Rail and train operators to consider and implement risk control measures at those junctions identified in the second recommendation.

The fourth recommendation is intended to ensure that Lumo minimises the risks from falling luggage on its services.

RAIB has also identified two learning points. These relate to the need for drivers to maintain alertness when approaching junction signals and that train operator emergency plans should specifically include processes to deal with the aftermath of overspeeding incidents.

Second overspeeding incident

At around 13:00 on 4 May 2023, another overspeeding incident occurred at the same location involving the 09:54 Sunderland to King’s Cross service, operated by Grand Central.

The train involved, which was travelling in the same direction and on the same line as that involved in the April 2022 incident, passed over the three sets of points at a speed of around 65mph (104km/h). The excessive speed over the points led to the train lurching sideways and minor injuries to at least one person. The train did not derail during the incident and subsequently came to a stand at Peterborough station under emergency braking. Inspections carried out following the incident found that no damage had been caused to the railway infrastructure, or to the vehicles involved.

As a result, RAIB issued urgent safety advice to Network Rail and transport undertakings that operate trains on the East Coast main line through Peterborough station. This advised duty holders to take immediate steps, either operationally, or by technical means, to mitigate the risk of overspeeding beyond P468 signal at Spital Junction.

Andrew Hall, RAIB.

Andrew Hall, Chief Inspector of Rail Accidents said: “The overspeeding incident at Spital junction in April 2022, led to a number of minor injuries. Some passengers were thrown from their seats and some hit by luggage falling from overhead racks. However, the outcome could have been much worse, as analysis showed the train was close to overturning.

“A similar event occurred at the same junction in May 2023, albeit a little slower and involving a train operated by a different train operating company.

“As designed, the signal protecting the junction cleared from red to green and displayed an indicator showing which way the junction was set as the train approached. The risk associated with a train then accelerating to an excessive speed over the associated diverging junction, when the driver has an expectation of taking a through route with a much higher permissible speed, had previously been illustrated when a light locomotive derailed in similar circumstances at Bletchley in February 2012. The risk associated with particular junctions and drivers, varies with infrastructure configuration and driver expectation.

“It is therefore absolutely necessary that Network Rail and train operating companies work together to mutually understand and sufficiently mitigate risks of this type at specific locations, accounting for the rolling stock and operations involved.”

Be the first to comment

Leave a Reply

Your email address will not be published.


*