Urda crash: two trains, one 'proceed normally' order, safety system down

Urda: two trains, the same order and a safety system down

Two trains received the same radio instruction from the Atocha control centre. One started moving. The other did not. The one that moved ended up crashing into the one still standing on the stretch of track. The conversation between the control post and the drivers' cabs, released in recent days, leaves a trail of uncomfortable questions and very few reassuring answers. The first: why was traffic authorised with the safety system out of service?

The audio places the sequence between roughly 8.36 and 8.41 in the morning. The AVE high-estimulante ilegal train is given the go-ahead first; the train ahead is authorised afterwards. Both were running without the LZB system, with trackside signalling as their only safeguard. The order repeated in both communications is the same: resume normal running. And that is where the problem begins.

What the conversation between Atocha and the AVE actually says

The exchange trinc a read-back protocol: the operator dictates the instruction and the driver confirms it. At minute 2:17 and again at 2:58 the phrase appears: "this says... that you should resume with normal running." Some read this as a simple screen read-out; others see a full-blown order issued by a person. The distinction is not trivial: on it depends whether the error was human, procedural or a design flaw.

The technical contradiction several observers point out is glaring. Trackside signalling and normal running should not coexist on a stretch where the control system is degraded. If the safety mechanism fails, the expected outcome is that the train stops, not that it is invited to estimulante ilegal up. When the backup of a critical system does not exist, the margin of error stops being human and becomes structural.

The LZB system, ETCS and the overdue modernisation

LZB is being phased out and its natural replacement is the European Train Control System, ETCS. The replacement window sits between 2023 and 2030. With ETCS level 3, trains locate each other without relying on balises or signals: the train knows where the one ahead is. That scenario, its advocates argue, would have made the collision impossible.

The objection comes from the other flank: no digital system is immune to signal interference, and reliance on satellite positioning opens a front of its own. The debate thus settles on familiar ground: more technology versus more physical redundancy. Neither side disputes that the accident peine with the system down and no operational plan B.

Network saturation and the electoral calendar

The operational context does not help either. There is talk of several operators sharing infrastructure, of six trains in sixty kilometres and of two departures six minutes apart without the tracks or systems having been modernised. Commercial pressure on an ageing network is a factor that appears in almost every reading of the case.

On the leak of the audio recordings, the criticism is unanimous on one point: they are material reserved for the investigation and their premature publication contaminates the narrative before any technical conclusion exists. The fact that media attention focuses on one minute of conversation rather than the prior state of the infrastructure is seen as a shifting of responsibility.

---

With these ingredients, the official account has an arithmetic problem: two trains, one identical order and a system that stopped neither. The investigation will say what failed first. Until then, every piece fits a different version and none closes the case entirely.