[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fL5p2KsBLwuUhwg5L7c4rwUnfKh7pYbmqa7DDyDUcc3k":3},{"lesson":4},{"id":5,"slug":6,"article_id":7,"title":8,"body":9,"prevention":10,"framework_refs":11,"status":20,"created_at":21,"published_at":22,"article":23,"tags":27,"podcasts":46},"80d51608-ce93-4a46-ac25-76887afa1c12","military-gps-jamming-exercise-blamed-in-fatal-civilian-medevac-crash","3e75c015-02ed-46b9-84f4-9bb3e0cdf9a4","Military GPS Jamming Exercise Blamed in Fatal Civilian Medevac Crash","A U.S. military GPS jamming exercise conducted without adequate civilian coordination disrupted navigation systems relied upon by a civilian medevac aircraft, ultimately contributing to a fatal crash into a New Mexico mountain. The pilots, stripped of modern GPS guidance, were forced into degraded navigation modes they were insufficiently prepared to execute under real-world stress conditions. This incident demonstrates that electronic warfare activities carry serious externalities beyond the battlefield, directly threatening civilian lives and critical air medical services. The failure to establish proper exclusion zones, notify civil aviation authorities, or assess second-order risks represents a fundamental breakdown in inter-agency risk governance. As GPS jamming and spoofing proliferate — from military exercises to adversarial drone operations — the aviation sector must treat GPS dependency as a systemic vulnerability requiring mitigation.","**Immediate Actions:**\n- Establish mandatory real-time coordination protocols between military electronic warfare exercise planners and the FAA\u002Fcivilian aviation authorities before any jamming activity begins.\n- Issue NOTAMs (Notices to Air Missions) with sufficient geographic and temporal specificity to warn all civilian aircraft, including medevac operators, of active GPS jamming zones.\n\n**Long-term Improvements:**\n- Mandate regular simulator training for all commercial and medevac pilots in degraded-GPS and GPS-denied navigation scenarios to reduce disorientation risk.\n- Develop and enforce a national policy framework that classifies GPS jamming exercises near civilian flight corridors as requiring formal risk assessments and third-party safety reviews.\n- Invest in resilient, redundant navigation infrastructure (e.g., eLoran, inertial navigation systems) as backup capabilities for aircraft operating in GPS-dependent environments.\n\n**Detection & Monitoring Measures:**\n- Deploy real-time GPS interference monitoring networks across civilian airspace to detect, geolocate, and alert on jamming events as they occur.\n- Require military exercise after-action reports to include analysis of any civilian aviation disruptions and submit findings to an inter-agency safety review board.",[12,13,14,15,16,17,18,19],"NIST SP 800-53 IR-1 (Incident Response Policy)","NIST SP 800-53 RA-3 (Risk Assessment)","CIS Control 11 – Recover Data","ICAO Annex 10 – Aeronautical Telecommunications (Radio Navigation Aids)","FAA Advisory Circular AC 90-100A – GPS Operations","NIST SP 800-53 CP-2 (Contingency Planning)","EU GNSS Vulnerability Assessment Framework (EASA)","CISA Cross-Sector Cybersecurity Performance Goal – GPS\u002FPNT Resilience","published","2026-07-30T12:22:03.784269+00:00","2026-07-30T12:22:03.665+00:00",{"id":7,"url":24,"slug":25,"title":26},"https:\u002F\u002Fwww.wired.com\u002Fstory\u002Fa-civilian-plane-crashed-in-new-mexico-was-the-militarys-tech-to-blame\u002F","a-civilian-plane-crashed-in-new-mexico-was-the-military-s-tech-to-blame-a5109b","A Civilian Plane Crashed in New Mexico. Was the Military’s Tech to Blame?",[28,34,40],{"id":29,"name":30,"slug":31,"description":32,"color":33},"182e11d5-57c4-444e-8ec8-4682ad60261b","Incident Response","incident-response","Slow detection, poor containment, missing playbooks","#14b8a6",{"id":35,"name":36,"slug":37,"description":38,"color":39},"7261eb8f-acd4-4d93-a489-7fdd652ec0ea","Security Awareness","security-awareness","Phishing, social engineering, human error","#22c55e",{"id":41,"name":42,"slug":43,"description":44,"color":45},"c0dcc566-3654-4d70-8ede-262a198e732f","Regulatory Compliance","regulatory-compliance","GDPR, NIS2, DORA, sector-specific violations","#ec4899",[]]