Full Report
Image: Screen capture from YouTube – Azerbaijan Air 8243 What’s new: A LinkedIn post by our friend and colleague Ramsey Faragher, Director (CEO) of the Royal Institute of Navigation. He relates that many people have not fully realized GPS jamming has cost lives. And that it could well happen again. In case you missed it – It’s Christmas Day, 2024, and Russian forces at Grozny are jamming GPS. The jamming disables ADS-B so they can not identify Azerbaijan Air 8243 as a friendly. The Russians fire a missile and severely damage the airliner. It crash lands and, when all is said and done, 38 are dead. Why it’s important: The loss of life on Azerbaijan Air 8243 should have been a wakeup call for all GNSS providers, users, and especially aviation authorities. Little has been done to mitigate the impacts of GPS disruption. Aircrews have been warned and received a bit […]
Analysis Summary
# Incident Report: Kinetic Impact Resulting from GPS Jamming (Azerbaijan Air 8243)
## Executive Summary
On December 25, 2024, Azerbaijan Air flight 8243 was severely damaged by a missile strike after Russian forces engaged in GPS jamming near Grozny. The electronic interference disabled the aircraft's ADS-B capabilities, preventing identification of the plane as a friendly civilian vessel. The incident resulted in a crash landing and the deaths of 38 individuals.
## Incident Details
- **Discovery Date:** December 25, 2024
- **Incident Date:** December 25, 2024
- **Affected Organization:** Azerbaijan Air
- **Sector:** Aviation / Critical Infrastructure
- **Geography:** Grozny region (Caucasus)
## Timeline of Events
### Initial Access
- **Date/Time:** December 25, 2024 (Christmas Day)
- **Vector:** Electronic Warfare (EW) / Signal Interference
- **Details:** Russian forces deployed GPS jamming equipment in the Grozny area.
### Lateral Movement
- **N/A:** This was a signal-based kinetic attack rather than a network intrusion. The "movement" involved the propagation of jamming signals across the PNT (Position, Navigation, and Timing) spectrum.
### Data Exfiltration/Impact
- **Details:** The jamming caused the failure of the Automatic Dependent Surveillance–Broadcast (ADS-B) system. This led to a failure in the Identification Friend or Foe (IFF) process by ground forces.
### Detection & Response
- **Detection:** The incident was identified immediately upon the missile impact and subsequent crash landing of Azerbaijan Air 8243.
- **Response Actions:** Emergency crash landing procedures were initiated by the aircrew. Post-incident reporting by the Royal Institute of Navigation highlighted the systemic failure.
## Attack Methodology
- **Initial Access:** Signal Jamming (Electronic Warfare).
- **Persistence:** Continuous broadcasting of interference signals on GNSS frequencies.
- **Defense Evasion:** Jamming rendered the civilian aircraft "invisible" or "unidentifiable" to safety systems, effectively masking its status.
- **Impact:** Denial of Service (DoS) of critical navigation and identification signals, leading to kinetic engagement (missile strike).
## Impact Assessment
- **Financial:** Total loss of airframe; significant legal and compensatory liabilities.
- **Data Breach:** None (Physical/Kinetic impact).
- **Operational:** Total loss of flight operations for the affected route; disruption of regional airspace safety.
- **Reputational:** Massive loss of public trust in aviation safety within contested electronic environments.
- **Human:** 38 fatalities.
## Indicators of Compromise
- **Behavioral Indicators:** GNSS signal loss, "unidentified" status on military radar despite civilian flight paths, ADS-B signal dropout.
## Response Actions
- **Containment:** Aircrews warned of GPS disruption in the region.
- **Eradication:** N/A (Military jamming requires diplomatic or kinetic cessation).
- **Recovery:** Implementation of basic aircrew training for GPS-denied environments.
## Lessons Learned
- **Systemic Vulnerability:** ADS-B and IFF systems are dangerously dependent on unencrypted, easily jammed GNSS signals.
- **Warning Fatigue:** Despite previous warnings about GPS vulnerability, authorities failed to implement hardware-level changes before the loss of life occurred.
- **Identification Failure:** In modern warfare, the lack of a resilient PNT foundation leads directly to "blue-on-blue" or "friendly-on-civilian" casualties.
## Recommendations
- **Technical Redundancy:** Accelerate the adoption of resilient PNT alternatives, such as eLoran, to provide a backup to GPS.
- **Hardware Hardening:** Mandate system and hardware upgrades for commercial airliners to operate in contested electronic environments.
- **Regulatory Action:** Aviation authorities must treat GPS interference as a critical safety-of-life threat rather than a peripheral technical issue.
- **Policy Advocacy:** Decision-makers should recognize PNT as the "quiet backbone" of critical infrastructure and fund its protection accordingly.