Air India Flight 182 Bombing (1985)
Dossier page | Last updated: 2026-01-25
At a glance
Date: 1985-06-23
Location: Off the coast of Ireland (Air India Flight 182)
Incident type: Bombing/Explosive attack
Tags: aviation, explosives
What happened
Case facts: Incident type: Bombing/Explosive attack
On June 23, 1985, Air India Flight 182 was destroyed by an explosive device over the Atlantic off Ireland, killing all 329 people on board. Britannica summarizes the total fatalities and the core facts of the disaster.
Canada's Commission of Inquiry produced a multi-volume final report examining pre-bombing conditions, intelligence and evidence challenges, investigative response, aviation security, and systemic lessons. The report is a primary source for prevention and disruption mapping in this dossier context.
What we still need: a dossier-ready synopsis of the Commission's key findings tied to intelligence failures, aviation security gaps, and the investigation/prosecution challenges, with direct section references.
Victims and impact
Fatalities: [to be confirmed]
All 329 passengers and crew were killed. What we still need: a verified breakdown of nationality/demographics and a memorialized list appropriate for public use, sourced from an authoritative compilation.
Pre-attack indicators
- Attack planning required infiltration of aviation security and baggage/cargo pathways, creating potential signals in screening and chain-of-custody.
- Cross-border logistics and communications associated with an organized plot created intelligence opportunities if effectively triaged and shared.
- What we still need: confirmed Commission-identified warning indicators and the precise points where intelligence and evidence handling diverged.
Weapons and methods
[details pending]
Detection and prevention
Detection opportunities
- [details pending]
Prevention lessons
- [details pending]
Missed intervention opportunities
- [details pending]
Response and aftermath
Response actions
Immediate life-safety response, scene stabilization, victim services, and investigative coordination (to be specified per case)
After-action findings
Operational lessons, interagency coordination findings, and public-safety recommendations (to be specified per case)
Policy changes
Security/process changes enacted post-incident (to be specified per case)
Sources
Sources: Internal C-STAD dataset and tier pages (no external citations for this case).
Prevention / disruption opportunities
- [details pending] What we still need: case-specific intervention points (contacts, policies, access controls, reporting pathways).
Detection and response
- Identify handoff failures: where information should have moved but did not (school/work/clinician/police).
- [details pending] What we still need: verified response timeline, initial notification method, and investigation/prosecution outcomes.
Aftermath and changes
- Late disruption after access and capability were already established.
- [details pending] What we still need: documented policy, security, or procedural changes linked to this case.