Operators, infrastructure managers, and speed risk: why shared data is the missing link

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.

---

This series started with a simple observation: the UK’s overspeed problem is an information gap, not a technology problem.

Our second blog showed how Zelra’s DAS solution closes that gap for the driver. Now we will conclude by considering the part of the problem that exists outside the cab.

Speed restriction information does not belong to any one single organisation. That issue is at the heart of the matter.

A shared responsibility with a weak point

Network Rail sets and communicates speed restrictions as the infrastructure manager. Train operators manage drivers, briefings, and procedures.

Each holds part of the chain that carries a restriction from the point it is imposed to the point a driver acts on it. Neither holds all of it.

The risk lives in the handover between them. When cooperation at that interface is enabled, information flows. When it is inconsistent, the chain has a weak point, and the consequences fall to the driver.

This is not a theoretical concern. When the Office of Rail and Road (ORR) convened its cross-industry meeting in December 2025, a central purpose was to improve cooperation between Network Rail and train operators on exactly this issue.

ORR has since been clear that an effective approach to overspeeding requires strong coordination between operators and infrastructure managers, supported by clear speed restriction communication. The interface is not a detail – it is the mechanism.

Its 2026 annual health and safety report goes further. It identifies organisational interfaces between operators, infrastructure managers, and the wider supply chain, as the source of some of the most significant risks on the railway. It states that these risks require active leadership rather than coordination alone.

The current context

The UK rail industry is experiencing a period of heightened attention to speed and safety. The collision between two East Midlands Railway services near Elstow on 19 June 2026, in which a driver tragically died and 162 passengers were injured, is being investigated by the RAIB.

Zelra makes no claim about its causes, which are for that investigation to establish, and no suggestion that it relates to the matters discussed here. We acknowledge it because this is the context in which our industry is now thinking about safety, and it would be wrong to write about speed risk as though that context did not exist.

The reform of the industry’s structure is also part of the backdrop. The move toward Great British Railways is intended to bring track and train under a more unified guiding mind.

We make no prediction about how that structure will finally look or when it will arrive. We note only that the direction of travel is toward closer coordination between infrastructure and operations, which is the same coordination the overspeed problem demands.

ORR has made a similar point. Its 2026 annual report describes the creation of Great British Railways as an opportunity to strengthen system leadership, simplify accountability, and improve the management of shared risks. It notes that reform, if delivered effectively, can help address longstanding weaknesses at organisational interfaces.

How Connected DAS responds to the interface problem

When ORR examined early industry progress on overspeeding, it found an over reliance on administrative controls rather than more robust or technological solutions. That is the regulator’s stated view of the direction of travel. It points toward controls that do not depend solely on briefings, paperwork, and memory.

This is where C-DAS, the connected mode of Zelra’s Driver Advisory System, becomes relevant. A standalone system already delivers strong forward-looking guidance from planned data, however a connected system does something additional. It turns a common responsibility into a shared, verified data flow.

Zelra’s C-DAS integrates with Traffic Management Systems through standards-based interfaces. A restriction issued or changed at network level can then reach the cab continuously and automatically.

It no longer depends on where in the human communication chain the handover happens to be strongest. The information takes a digital path from the network to the driver, rather than a series of manual relays.

This does not remove the need for cooperation between infrastructure managers and operators. It gives that cooperation a reliable channel to operate through. The organisations still agree what the restriction is and why, then our C-DAS system ensures the agreed information reaches the driver in a usable form, at the right moment, every time.

Achievable now, ready for what comes next

The important point for operators and infrastructure managers is that none of this depends on waiting for full system reform. The connected capability is built on a standalone platform that delivers value from day one.

An operator can deploy proven S-DAS across a fleet now, gaining immediate value as the first step. C-DAS is the destination, and it activates route by route as integration capability becomes available. There is no platform change and no driver retraining, because the interface is identical in both modes.

This sequencing matters in the current environment. It lets operators act on speed risk today, then progress to connected operation where the fullest benefit is realised. The industry is increasingly clear that connected operation is the solution to implement, and the stepping stone approach is how operators get there without delay.

The RSSB Train Protection Strategy frames the years ahead as an interim period before comprehensive ETCS fitment. A platform that delivers proven guidance now, and connects to Traffic Management as the network matures, is built for that period.

Closing the loop

Across this series, one thread has held. The overspeed problem is an information problem, and information problems are solved by getting the right information to the right person at the right moment.

For the driver, that means anticipatory in-cab guidance. For the industry, it means a reliable channel across the interface between infrastructure managers and operators.

Zelra’s C-DAS addresses both, and connected operation is where the fullest benefit is realised. The platform is deployable today as S-DAS and progresses to C-DAS as the destination. If you would like to discuss what that path could look like on your network, our team would welcome the conversation. You can also return to the first blog and second blog in this series.