Sharm el-Sheikh bombings (2005)
Dossier page | Last updated: 2026-01-25
At a glance
Date: [to be confirmed]
Location: [to be confirmed]
Incident type: Bombing/Explosive attack
Tags: explosives
What happened
Case facts: Incident type: Bombing/Explosive attack
[to be confirmed] What is still needed: a verified minute-by-minute sequence of key actions, victim locations, and law enforcement response milestones.
[to be confirmed] What is still needed: a verified minute-by-minute sequence of key actions, victim locations, and law enforcement response milestones.
[to be confirmed] What is still needed: a verified minute-by-minute sequence of key actions, victim locations, and law enforcement response milestones.
Victims and impact
Fatalities: [to be confirmed]
Injuries: [to be confirmed]
Named victims (where appropriate): [to be confirmed]
Community impact and survivor outcomes vary by case and should be documented with verified sources.
What we still need: verified victim roster (where appropriate), injury breakdown, and memorial/community impact documentation.
Pre-attack indicators
- Warning behavior domains to audit: fixation/identification, leakage, last-resort framing, novel aggression, and pathway behaviors (planning, preparation, acquisition, rehearsal).
- [details pending] What we still need: documented leakage/threat communications, procurement steps, and any rehearsal/surveillance behavior.
What we still need: primary-source documentation of pre-incident behaviors, communications, and procurement steps where not already verified.
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.