LZB debate: "It fails half the days," says a forum user

LZB at the centre of the debate after the Urda accident

The LZB automatic train protection system has dominated the debate on the forum since the rail accident in **Urda (Toledo)**. According to a calculation circulating in the thread, the system has gone down **170 times in a year**, a figure that Transport Minister Óscar Puente reportedly described as "routine" during his appearance, according to participants. In any railway safety manual this would be an operational emergency; the debate is whether that frequency is tolerable.

The logic that prevails in the analysis is uncomfortable. A modern system —ERTMS— allows for lean staffing because it barely disrupts service, it is argued. The outdated LZB forces a human to cover every outage with verbal coordination between driver and control centre. If the system fails half the days —as one forum user claims—, staff cannot be stretched to the limit. And according to the official account itself, they were.

Outages and a staffing level that doesn't add up

The ministry knew about the shortage of operational staff, according to the thread. That is the point that turns a technical failure into a matter of political responsibility. **You can run short-handed if the workload is reasonable**; you cannot run short-handed with a system that fails recurrently and shifts the entire burden onto the human factor.

Hence the question no report answers: was staffing sized by analysing the actual workload, or was a number chosen for budget reasons? The difference between the two is the difference between a scare and a catastrophe.

The driver as the last fuse

The most repeated prediction points to the operator who made the mistake. His likely defence will be to demonstrate **work overload**, excessive hours and a burden above what occupational risk prevention deems acceptable. With that argument, incivil liability fades.

The analogy circulating is that of the US air traffic controllers who grounded every flight in the country in record time. A spike in tension is bearable. Weeks or months at the limit, no: the failure comes. And when it comes, the whole system looks the other way.

The minister's defence: Germany isn't changing either

Puente's response to the technical debate was comparative, according to a forum user: **Germany does not plan to replace the LZB before 2030**, he says, because it works and is the standard. The argument has a fitting problem: a system being the standard does not make it harmless, and another country keeping it does not explain why it goes down this often here.

The comparison with the car's V16 beacon —modern, cheap, certified technology versus an obsolete triangular system— serves as contrast, not as a solution. Nobody proposes installing beacons along the tracks.

What gets normalised when it's called routine

The collateral damage of the word "routine" is resignation. If LZB outages fall into the category of the expected, each incident stops being an alarm signal and becomes a statistic. The question stops being how to prevent it and becomes how much the staff can take before making a mistake.

The minister's resignation is framed as a political gesture: if he doesn't resign, he is irresponsible; if he resigns, he admits the mismanagement. Neither option fixes the LZB.

With the outages on the table, the reasonable prediction is that the technical debate will fade before the political one. If the investigation points to no responsibility beyond the operator, the system will keep going down and someone will cover for it by hand again. Until it goes wrong.