Incident · Malfunction
USAF MQ-9 Reaper crashed off the coast of South Korea
An MQ-9 Reaper drone assigned to Kunsan Air Base crashed into the sea near Maldo-Ri Island, South Korea, while performing a routine mission in November 2025. The incident was reported by U.S. Forces Korea.
Occurred 2025-11-24 · MQ-9 Reaper at United States Air Force (global operations) · General Atomics · United States Air Force (global operations) · Drones
How to read this record
Incident records on DEPLOY are compiled from public sources (regulatory filings, news reports, and operator disclosures) and reflect what has been reported and tracked to date. They are not legal findings, determinations of fault, or safety ratings, and may be updated as new information is verified. See the sources below for the underlying references.Machine-readable surfaces
- Markdown mirror: /incidents/mq-9-reaper-crash-south-korea-2025.md
- JSON-LD: embedded in this page’s head
- REST API: /v1/incidents/ab78c91c-c73f-44e5-aede-01c211c1173d
- Data documentation: /data
- Query this programmatically: Deploy MCP
Sources (1)
- US Air Force Reaper drone crashes off South Korea · https://www.cnn.com/2025/11/24/asia/us-reaper-drone-crash-south-korea-intl-hnk-ml · 2025-11-24
Common questions
What happened in USAF MQ-9 Reaper crashed off the coast of South Korea?
When did this incident occur?
What robot was involved in USAF MQ-9 Reaper crashed off the coast of South Korea?
Has anyone responded to USAF MQ-9 Reaper crashed off the coast of South Korea?
What is the current status of USAF MQ-9 Reaper crashed off the coast of South Korea?
Methodology: Verified · 1 source (no primary) · last reviewed 2026-08-21
Verification posture
Verified
Low confidence
Review state
Stable
Last reviewed 2026-08-21
Sources by quality tier
- 1
- unclassified
- Unclassified source
The framework is documented at /methodology. Corrections at /corrections. Reviewer: DEPLOY editorial team.
Methodology surface for USAF MQ-9 Reaper crashed off the coast of South Korea.Deploy Watch
Track this incident.
We notify you when the regulator updates the record, the remedy status changes, or a related incident surfaces.
Canonical ID ab78c91c-c73f-44e5-aede-01c211c1173d