Case 75 · National security

Pahalgam. 26 dead, a lapse admitted, nobody moved

22 Apr 2025

Responsibility taken, no resignation

480 days since Nobody has been held to account.

Human cost

26 killed, 25 Indians and one Nepali citizen, among them a local pony operator shot while trying to stop the gunmen; the injured count is reported inconsistently

Financial cost Est

Never costed publicly. The attack broke a tourism-led recovery in the valley; no compensation figure has been published

What happened

On the afternoon of 22 April 2025, gunmen attacked tourists at Baisaran meadow, a walk-in-only site about five kilometres from Pahalgam. Two attackers who had mingled with the crowd herded people towards two more armed men, who segregated victims by religion before shooting them. Twenty-six people were killed.

Claim against record

What the government said

The government's position is that this was a Pakistan-sponsored attack designed to create a communal divide and wreck Kashmir's tourism recovery, that it briefed all parties on the lapses within 48 hours, that the route had been opened by tour operators in April without permission on terrain reachable only after a two-hour walk, and that it delivered accountability through Operation Sindoor on 7 May 2025, the killing of the three attackers in July, and NIA chargesheets naming the Lashkar-e-Taiba leadership.

What the record shows

Responsibility taken, no resignation

At an all-party meeting two days later, Home Ministry and IB officials briefed leaders on where the lapses had occurred, and said tourists had gone to Baisaran without police permission. Reporting a year on notes such permission had not historically been sought, and that the meadow carried no deployment at all. On 14 July 2025 the Lieutenant Governor said he took full responsibility for what was 'undoubtedly a security failure', and remained in office. The government has never published what the lapses were, what was fixed, or who was answerable. The only public documents are the NIA chargesheets, which address the terror conspiracy, not the security failure.

Contested / alleged

A report that a CRPF company assigned to Baisaran was redeployed shortly before the attack is attributed to unnamed sources and remains unverified.

What accountability should have looked like

A published inquiry naming the decision that left a known tourist site unguarded, and a convention under which accepting full responsibility for 26 deaths carries a consequence.

Ministers and office-holders responsible

Security of J&K; lapses briefed to parties, never publishedMinistry of Home Affairs
Lieutenant Governor, J&K; accepted full responsibility, did not resignManoj Sinha

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, "Pahalgam. 26 dead, a lapse admitted, nobody moved" (22 Apr 2025), case-53. https://whoisresponsible.xyz/case/case-53/

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.