Forecast report
Will a single India–Pakistan cross-border incident between 1 Jan 2026 and 30 Sep 2026 produce at least 20 confirmed deaths per ACLED?
Forecast
P(Yes): 12.1%; P(No): 87.9%.
Distribution
Analysis
TL;DR
I estimate a 12% chance that ACLED records at least one qualifying single India–Pakistan cross-border event with 20 or more fatalities by 30 September 2026.
Context
The relationship is frozen, but the shooting front has been quiet in 2026. ACLED describes the May 2025 Pahalgam-to-Operation Sindoor cycle as some of the most intense India–Pakistan fighting in decades, and says the 22 April 2025 Pahalgam attack killed at least 26 tourists before India struck targets across Pakistan and Pakistan-administered Kashmir on 7 May 2025.
As of 31 May 2026, I found no public evidence of a qualifying 2026 event already in the books. The best open proxy is SATP: its Jammu & Kashmir table shows 9 killing incidents and 12 total terrorism-related deaths in 2026 through 28 May 2026, with 0 civilian deaths and 1 security-force death, and its Pakistan table shows only 1 fatality in Azad Kashmir and 4 in Gilgit-Baltistan in 2026 in the current-vintage state table. ()
Evidence
The historical backbone is a rare-event base rate. Since ACLED India coverage begins in 2016, the clean modern analogues are Uri in September 2016, Pulwama in February 2019, and Pahalgam in April 2025. Uri is just over the line if attackers are included in the same event: SATP records 18 security-force deaths and 4 militant deaths, or 22 total, in the LoC/Uri attack on 18 September 2016. Pulwama is clearly over the line: SATP describes at least 44 CRPF personnel killed by a suspected Jaish-e-Mohammed VBIED on 14 February 2019. Pahalgam is clearly over the line: SATP says TRF, an LeT offshoot, killed at least 26 people at Baisaran meadow on 22 April 2025. (satp.org)
That gives 3 qualifying-style single events over about 10.4 years from January 2016 through May 2026, or 0.29 events per year. Applied to the 122 days from 1 June through 30 September 2026, a constant-hazard Poisson model gives about 9%. If I count one May 2025 Operation Sindoor military strike or exchange as a fourth analogue despite ACLED row-splitting uncertainty, the same model gives about 12%. I put more weight on the 3-event model because the question requires one ACLED row, not an aggregate crisis death toll.
The long-run fatality trend says not to use the early-2000s massacre rate directly. SATP’s Jammu & Kashmir fatalities series is current-vintage, provisional, compiled from news reports, and the 2026 observation runs only through 28 May 2026. It shows a steep decline from thousands of annual deaths in 2000–2003 to 92 in 2025 and 12 so far in 2026. ()
| Year | Incidents of killing | Civilians | Security forces | Terrorists/insurgents/extremists | Not specified | Total deaths |
|---|---|---|---|---|---|---|
| 2000* | 1,385 | 641 | 441 | 1,708 | 9 | 2,799 |
| 2001 | 2,084 | 1,024 | 628 | 2,345 | 14 | 4,011 |
| 2002 | 1,642 | 837 | 447 | 1,758 | 56 | 3,098 |
| 2003 | 1,427 | 563 | 319 | 1,504 | 121 | 2,507 |
| 2004 | 1,061 | 437 | 318 | 962 | 72 | 1,789 |
| 2005 | 1,004 | 454 | 220 | 987 | 56 | 1,717 |
| 2006 | 694 | 256 | 172 | 607 | 90 | 1,125 |
| 2007 | 427 | 127 | 119 | 498 | 0 | 744 |
| 2008 | 261 | 71 | 85 | 382 | 0 | 538 |
| 2009 | 208 | 53 | 73 | 247 | 0 | 373 |
| 2010 | 189 | 34 | 69 | 258 | 0 | 361 |
| 2011 | 119 | 33 | 31 | 117 | 0 | 181 |
| 2012 | 70 | 19 | 18 | 84 | 0 | 121 |
| 2013 | 84 | 19 | 53 | 100 | 0 | 172 |
| 2014 | 91 | 28 | 47 | 114 | 0 | 189 |
| 2015 | 86 | 19 | 41 | 115 | 0 | 175 |
| 2016 | 112 | 14 | 88 | 165 | 0 | 267 |
| 2017 | 163 | 54 | 83 | 220 | 0 | 357 |
| 2018 | 206 | 86 | 95 | 271 | 0 | 452 |
| 2019 | 135 | 42 | 78 | 163 | 0 | 283 |
| 2020 | 140 | 33 | 56 | 232 | 0 | 321 |
| 2021 | 153 | 36 | 45 | 193 | 0 | 274 |
| 2022 | 151 | 30 | 30 | 193 | 0 | 253 |
| 2023 | 72 | 12 | 33 | 87 | 2 | 134 |
| 2024 | 61 | 31 | 26 | 69 | 1 | 127 |
| 2025 | 35 | 28 | 17 | 46 | 1 | 92 |
| 2026** | 9 | 0 | 1 | 10 | 1 | 12 |
*SATP says 2000 data begin on 6 March 2000. **SATP says 2026 data are through 28 May 2026. ()
The current indicators cut both ways. Risk is higher than an ordinary quiet year because ACLED’s April 2026 report says militant activity has shifted toward Jammu, that civilians such as Hindus and non-Kashmiris face heightened risk of headline-grabbing mass-fatality attacks, that three militant attacks accounted for half of civilian fatalities over the prior three years, and that renewed India–Pakistan confrontation remains a high-risk consequence of such targets. Indian official signaling is also harder than before: on 7 May 2026 India reiterated its right to defend itself against Pakistan-backed cross-border terrorism, and Pakistan extended its airspace restrictions on Indian aircraft into June 2026. (pakistantoday.com.pk)
Risk is lower than the rhetoric suggests because the realized 2026 fatality path is very low. SATP’s 2026 J&K major-incident table lists only 1 major incident through late May, with 3 militants killed and no civilian or security-force deaths. SATP’s 2026 infiltration log has border or LoC episodes on 30 January, 19 February, 4 March, 10 March, 15 March, and 12 May, but the 12 May Mankote incident killed only 1 suspected LeT intruder and the other entries are also far below the threshold. India’s defence ministry also told parliament that Indian Army battle casualties in border areas were 5 in 2025 and 0 so far in 2026. (m.thewire.in)
I used three channels for the remaining four months. First, a Pulwama/Pahalgam-style mass-casualty attack by a Pakistan-based or Pakistan-linked militant group: 7.5%. Second, a smaller militant event that triggers an Indian or Pakistani cross-border military event with 20 or more deaths in one ACLED row: 3.5%. Third, an untriggered artillery, drone, missile, or air clash, plus reporting/coding surprise from January–May: 1.5%. Combining these as overlapping hazards gives about 12%:
I round the prose estimate to 12%. The precise submitted probability is 12.1%.
What's non-obvious
The most likely YES path is not a planned interstate clash. It is one successful militant attack on a concentrated target: pilgrims, tourists, a security convoy, or a security camp. ACLED’s own analysis says the conflict is low-volume but tail-heavy because a few mass-fatality attacks now drive much of the civilian death burden.
The main trap is to forecast a crisis instead of the resolution rule. A repeat of May 2025 could kill many people and still resolve NO if ACLED splits deaths by date, location, and strike site. This pushes the probability below what the diplomatic freeze and harsh rhetoric imply.
Limitations
I could not directly inspect the full ACLED row-level India and Pakistan event data for 1 January–31 May 2026. ACLED says its data files require a myACLED account, and the API documentation confirms that the resolution-relevant fields include event date, actors, location, notes, and fatalities. This matters because ACLED could split a multi-site exchange into sub-20 rows, or lump a multi-hour exchange at one location into a qualifying row.
SATP is a strong cross-check but not the primary resolver. Its figures are provisional news-report compilations, while the question resolves on ACLED data available by 15 October 2026. The largest remaining uncertainty is not data lag. It is whether the post-Pahalgam security surge has disrupted the small number of actors capable of one high-fatality attack before the Amarnath Yatra and post-monsoon infiltration windows pass.
Sources
- Domain Expert Search · mcp
Found 9 subagent groups for 'India Pakistan Kashmir conflict security militancy Line of Control escalation risk 2026':
- Major incidents of terrorist violence in Jammu and Kashmir 2016 · openai
- Pakistan extends airspace ban on Indian flights - Pakistan Today - Pakistan Today · openai
- ‘No Data on Civilian Deaths,’ Govt on Casualties in Pakistan Cross-Border Firing - The Wire · openai
- Domain Expert Research Task · mcp
Job domain_expert_research_task_3bdae97020 done after 507721ms.
- satp.org · tool
- satp.org · tool
- channelnewsasia.com · tool
- pib.gov.in · tool
- pib.gov.in · tool
- archive.ph · tool
- satp.org · tool
- documents.un.org · tool
- satp.org · tool
- satp.org · tool
- nia.gov.in · tool
- moneycontrol.com · tool
- satp.org · tool
- acleddata.com · tool
- en.wikipedia.org · tool
- britannica.com · tool
- satp.org · tool
- satp.org · tool
- everycrsreport.com · tool
- satp.org · tool
- en.wikipedia.org · tool
- acleddata.com · tool
- pib.gov.in · tool
- everycrsreport.com · tool
- aljazeera.com · tool
- pib.gov.in · tool
- satp.org · tool
- apnews.com · tool
- satp.org · tool
- satp.org · tool
- satp.org · tool
- satp.org · tool
- satp.org · tool
- satp.org · tool
- satp.org · tool
- satp.org · tool
- satp.org · tool
- satp.org · tool
- investing.com · tool
- satp.org · tool
- euronews.com · tool
- theprint.in · tool
- aa.com.tr · tool
- satp.org · tool
- satp.org · tool
Question Details
Description
The India–Pakistan relationship is in its longest sub-war freeze since 2019. In May 2025 the two nuclear-armed neighbours fought a 4-day shooting war (Operation Sindoor) triggered by the 22 April 2025 Pahalgam attack in Indian-administered Kashmir that killed 26 civilians. Pakistan confirmed at least 31 people killed inside its territory by Indian strikes and cross-border firing, and total reported fatalities on both sides exceeded 70. A DGMO-level ceasefire announced on 10 May 2025 has held — commercial flights and local normalcy have returned — but the diplomatic posture remains hostile: the Indus Waters Treaty is in abeyance, the Attari–Wagah crossing is closed, Pakistan keeps its airspace shut to Indian carriers, and bilateral trade and most visas remain suspended. As of the first anniversary of Pahalgam on 22 April 2026, PM Modi, Defence Minister Rajnath Singh and the Indian Army publicly declared that 'Operation Sindoor continues' and that any future attack traceable to Pakistan-based groups would be met with an 'immediate and decisive response'. Pakistani ministers responded with sharp counter-rhetoric. India's Ministry of Defence reports zero Indian soldier deaths on the Pakistan front so far in 2026 and five in 2025, and ACLED has not recorded a mass-casualty India–Pakistan cross-border incident since the May 2025 ceasefire. Analysts (Chatham House, CSIS, Atlantic Council) judge the ceasefire 'shaky' and flag the Pahalgam anniversary window and monsoon/post-monsoon infiltration season as the highest-risk periods before end-September 2026. This question asks whether, between 1 January 2026 and 30 September 2026 inclusive, ACLED records at least one single India–Pakistan cross-border event with ≥ 20 fatalities. The threshold is meant to capture a clearly 'cross-border dispute' class of incident — a militant cross-LoC raid, artillery/mortar exchange, airstrike, drone/missile salvo, or conventional clash — rather than routine small-scale ceasefire violations. Purely internal Indian or internal Pakistani events (e.g., a bombing inside a city with no direct cross-border military component) are excluded.
Resolution Criteria
Resolves YES if, on or before 23:59 UTC on 30 September 2026, the ACLED Explorer/Curated Data for India and/or Pakistan (https://acleddata.com/explorer/ and https://acleddata.com/curated-data-files/) records at least one discrete event, with event date between 1 January 2026 and 30 September 2026 inclusive, satisfying ALL of the following: (a) the Actor1 and Actor2 fields reference at least one of {Military Forces of India, Military Forces of Pakistan, Pakistani state-sponsored or Pakistan-based militant groups (e.g., Lashkar-e-Taiba, Jaish-e-Mohammed, The Resistance Front, Hizbul Mujahideen) operating across the International Border / Line of Control, or Indian state forces operating across the IB/LoC}; (b) the location is within 50 km of the India–Pakistan International Border or Line of Control, OR is a direct strike by one country's forces into the other's territory (including Pakistan-administered or India-administered Kashmir); (c) ACLED's 'fatalities' field for that single event is ≥ 20. Resolves NO otherwise. Primary resolution source: ACLED (https://acleddata.com/). If ACLED is unavailable or has not updated through 30 September by the time of resolution (ACLED typically publishes with a ~1-week lag), the South Asia Terrorism Portal fatalities datasheets (https://www.satp.org/datasheet-terrorist-attack/fatalities/india and https://www.satp.org/datasheet-terrorist-attack/fatalities/pakistanSI) may be used as fallback, requiring ≥ 20 confirmed deaths in a single identifiable cross-border incident over the same window. Resolution will use data as available on 15 October 2026.
Fine Print
Fatalities are counted per ACLED's single-event fatality field; they include combatants and civilians on either side. Multiple small simultaneous events that ACLED records as separate rows do NOT aggregate — the threshold is ≥ 20 in a single ACLED event. A sustained exchange that ACLED lumps into one event (e.g., a multi-hour artillery duel at a single location) DOES count as one event. Events involving third parties (e.g., Afghanistan–Pakistan border clashes, internal Pakistani TTP attacks, Baloch insurgency, Indian internal Maoist violence) are excluded, even if they occur near a border. A cross-border terror attack inside India by a Pakistan-based group (with ACLED attributing the attack to such a group) counts even if it occurs more than 50 km from the border — e.g., a repeat of the 2008 Mumbai or 2019 Pulwama pattern qualifies. If ACLED and SATP disagree on whether a single incident crossed 20 deaths, ACLED governs. Question resolves NO if no qualifying single event is recorded by 15 October 2026 regardless of later revisions.