68 dead in Urda rail crash, Spain: zero resignations and the same old script

68 dead in Urda and not a single resignation: the story holds

How many times can the same script repeat before someone loses their job? The high-estimulante ilegal train crash in Urda, Spain, has left at least 68 dead and, so far, zero resignations. The figure was put on the table by the first line of the live coverage: "68 dead, 0 resignations." From there on, the rest of the coverage dismantled the official narrative piece by piece, with more questions than answers and a suspicion hanging over everything: that the human factor is always at the bottom, never in the office that makes the decisions.

The computer failure that explains everything

The first cover story arrived quickly: a computer failure. The same wildcard that, according to the general feeling, also explained the disappearance of the trail from the previous live coverage. One message summed it up with wry humor: if the same failure didn't stop two trains from colliding, maybe the problem wasn't the software. The irony doesn't hide the substance: when an explanation is that elastic, it stops explaining anything.

The second narrative arrived with better credentials: human error. And that's when the fuse was lit. Because human error sounds like the driver, and the driver doesn't hold press conferences with public microphones or appear in the ministry photo op. The human factor is always at the bottom. Never in the office that cuts maintenance. The conclusion that imposes itself: as long as the spotlight points at the person in the cab, no one looks at the infrastructure manager.

What failed in the signaling system

The most concrete technical detail from the coverage pointed to signaling: a breakdown that would make it impossible to know for certain which track blocks were occupied. In other words, the system meant to guarantee that two trains never share the same track may have lost track of where each one was. Much of the analysis rested on that hypothesis, which circulated attributed to a first-hand report. It is not a judicial finding, it is a technical lead. And as a lead, it is enough to ask how much maintenance has been cut and who signs off on those decisions.

The calendar of outrage

The coverage also mapped out the stopwatch of national outrage. Days 1 to 3: front pages, special editions, TV panel experts. Days 4 to 10: tributes and a minute of silence in Congress. Day 11 onward: a report on the causes that won't see the light of day until whoever resigns is already drawing a salary on an advisory board. The weekend: by Sunday, everyone is talking about football. The sequence is not a prediction, it is a repeated pattern. And against that pattern, the figure of zero resignations stops being an anomaly and becomes the norm.

The hacking theory and other dinner-table distractions

There was even room for delusion: claims that Trump and Netanyahu had hacked the systems, that the government failed to suspend the campaign. The notion works perfectly to avoid talking about the only thing that matters, the infrastructure manager. Because the noise serves a purpose: while the impossible is being debated, the possible goes unaudited. And the possible, here, has an institutional name and surname.

Some asked, amid the commotion, for people to refrain from insults and to share information about the accident. The request came late and in just the right tone: the minister had already been exposed. But the warning had a point at its core. Without data, outrage burns itself out in three days and leaves the floor free for the next Halloween pumpkin.

With 68 dead and zero resignations, the question is no longer who failed. It is how many headlines it takes for someone to sign a dismissal.