The context in which we publish this blog series has recently changed. On 19 June 2026, two East Midlands Railway services collided near Elstow in Bedfordshire. Train driver Shaun Burton died and 162 passengers were injured. Our thoughts are with everyone affected by this tragic event.
The Rail Accident Investigation Branch (RAIB) is currently investigating the collision, and it would be wrong to draw any conclusions before this work is complete. We make no suggestion that the Elstow collision was the result of overspeeding and note the RAIB’s interim report finding that Mr Burton’s train was travelling below the maximum permissible speed at this location.
Something is not working in how speed restriction information reaches train drivers in Great Britain.
This is not a new problem. The pattern of incidents documented across 2025, and the regulatory response during the months that followed, suggests the question can no longer be deferred.
Zelra has been developing and operating digital in-cab advisory systems in live UK passenger rail for over a decade. This blog is the first in a three-part series examining the overspeed information gap. We look at how it arises, why it persists, and what it will take to close it.
We start with what the evidence shows.
In 2025, the RAIB documented four overspeed incidents across two distinct failure modes. The specific causes differ. The underlying problem does not.
Across four incidents and two separate failure modes, one thing recurs. In each case, the driver arrived at a speed restriction without the adequate information to act on it correctly.
The Office of Rail and Road (ORR) responded to the accumulating pattern directly. In December 2025, it convened a cross-industry meeting with Network Rail and train operators. The meeting focused on two things: improving cooperation between Network Rail and train operators, and increasing the rate of progress on open RAIB recommendations from the earlier Spital Junction investigations.
In early 2026, HM Chief Inspector of Railways Richard Hines set out his position publicly. He said he had formed the view that the current response to overspeed risk was not achieving what it should be.
He confirmed that the regulator would be constructively challenging, and that enforcement action remained an option if the industry did not move faster. The signal from ORR was clear. Concern had become intervention.
In its annual health and safety report published in 2026, ORR restated overspeeding as one of the most significant and insufficiently controlled risks on the railway. It described the challenge as one of execution and system leadership rather than knowledge. It called for the industry to move from analysis to action, focusing on known high-risk locations.
The surface causes of these incidents are different. It is worth being precise about what they do have in common.
The South Wales incident was a Blanket Speed Restriction communication failure. Restrictions were imposed at route control level in response to forecast weather. The processes for communicating them onward to drivers and signalling staff were inadequate. The drivers arrived at the restriction without knowing it applied to them.
The Grantham South Junction and Cambridge Junction incidents represent a different category of junction Permanent Speed Restriction failure. In each case, the train was signalled onto a diverging route carrying a much lower speed limit than the through route. RAIB found that the drivers had not received sufficient, timely, and unambiguous information about the restriction ahead of them at the moment when it mattered.
The information gap is not about whether speed restrictions exist in the system. It is about how they reach the driver, in a usable form, at the right moment.
ORR’s attention to the interface between infrastructure managers and train operators is significant, because speed restriction information does not sit neatly within any single organisation’s control.
Network Rail sets and communicates restrictions. Train operators manage drivers and procedures. Each holds a part of the information chain. When that chain has a weak link, the consequences fall to the driver.
The Rail Safety and Standards Board (RSSB) published an updated Train Protection Strategy in November 2025. It sets out a framework for managing overspeed and Signal Passed at Danger risk during the interim period before comprehensive fitment of the European Train Control System. The strategy acknowledges that these events are rare but potentially high-consequence. It also acknowledges the gap that current arrangements leave open.
Network Rail has reached a similar conclusion. Its Speed Management Programme exists to develop an approach that provides real-time, in-cab information about speed restrictions of all types. The programme’s own documentation notes that the current method of informing drivers has barely changed in 100 years.
Paper-based and voice-based communication processes were not designed for today’s network. Restrictions can be imposed at short notice. Drivers approach high-speed through routes with diverging low-speed junctions.
The consequences of a missed instruction can be severe. Zelra’s Driver Advisory System (DAS) exists to help close exactly this gap. It has been operating in live UK passenger rail for over a decade, as well as in France and New Zealand.
It provides drivers with real-time information about permanent, temporary, emergency, and blanket speed restrictions, directly within the cab. It is an advisory tool that supports the driver, and the driver retains full authority over the train at all times.
The technology to help bridge the information gap is not in development. It is in service today. What has lagged is the pace at which operators and infrastructure managers have moved to deploy it at scale.
In our next blog, we look at the mechanism. We examine:
You can read it here, or contact our team to start a conversation.
Blogs
Freight Rail, Passenger Rail
Driving Advice System (DAS)
Australia/New Zealand, European Union, United Kingdom
6 minutes