Citizens' Accountability LedgerWho owned the mess? 25 years, every party, on the record

Case 64 · Public safety

Balasore train disaster. The resignation that never came

02 Jun 2023

No resignation

1,170 days since Recorded outcome: No resignation.

Human cost Est
~290+ killed and 1,000+ injured in one of India's worst rail crashes
Financial cost Est
Hard questions over safety-fund use and vacancies in safety-critical posts

What happened

A signalling failure caused a three-train collision near Balasore, Odisha, the deadliest Indian rail accident in decades.

Claim against record

What the government said

The government pointed to the inquiry and to record investment in rail safety and modernisation.

What the record shows

No resignation

With scrutiny falling on deferred safety spending and unfilled safety-critical vacancies, the Railways Minister offered words of accountability but did not resign, and the systemic questions were folded into a technical inquiry rather than a political reckoning.

What accountability should have looked like

Publish safety-fund use and vacancy data, close the signalling-integrity gaps, and treat the deadliest crash in decades as a matter of ministerial responsibility.

Ministers and office-holders responsible

Naming who held the portfolio is a matter of public record. It is not by itself a finding of personal responsibility for any death or any rupee.

Sources

T1 primary record · T2 reporting · T3 partisan

Ask them officially. File an RTI Know a better source? Add one

Cite or export this case

Citizens' Accountability Ledger, "Balasore train disaster. The resignation that never came" (02 Jun 2023), case-28. https://whoisresponsible.xyz/case/case-28/

JSON for this case The whole ledger as CSV

Quote the case id rather than the number on the card. The id never changes; the number shifts whenever an older case is added ahead of this one.