Incident · Other
Russian Su-27 collided with a US MQ-9 Reaper over the Black Sea, forcing it down
On Mar 14 2023 a Russian Su-27 dumped fuel on a US MQ-9 Reaper over international waters in the Black Sea and then struck its propeller during an intercept; operators ditched the damaged airframe (deliberately sunk to deep water, not recovered). No casualties. An adversary-action operational loss, not a system/safety fault (the single discrete, primary-DoD-sourced MQ-9 loss recorded; aggregate Houthi-theater losses are excluded as combat attrition).
Occurred 2023-03-14 · MQ-9 Reaper · General Atomics Aeronautical Systems
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/mq9-reaper-black-sea-su27-collision-2023.md
- JSON-LD: embedded in this page’s head
- REST API: /v1/incidents/61aa56ba-accc-4552-b29a-77cc0fb6aa94
- Data documentation: /data
- Query this programmatically: Deploy MCP
Outcomes (1)
- property damageverified
Revision history (4)
- 2026-06-05 · loss_cost_class · reported_press
- 2026-06-05 · fatality_count
- 2026-06-05 · property_damage_estimate_usd · reported_press
- 2026-06-05 · outcome_class
Outcome rows carry verification_posture independently. Revision events carry basis (verified_court_filing, verified_insurance, reported_press, estimate, undisclosed). The framework records outcomes only when verifiable; absence is honest absence, not a claim of no-impact.
Sources (2)
Common questions
- What happened in Russian Su-27 collided with a US MQ-9 Reaper over the Black Sea, forcing it down?
- On Mar 14 2023 a Russian Su-27 dumped fuel on a US MQ-9 Reaper over international waters in the Black Sea and then struck its propeller during an intercept; operators ditched the damaged airframe (deliberately sunk to deep water, not recovered). No casualties. An adversary-action operational loss, not a system/safety fault (the single discrete, primary-DoD-sourced MQ-9 loss recorded; aggregate Houthi-theater losses are excluded as combat attrition).
- When did this incident occur?
- The incident is recorded as occurring on March 14, 2023 on the DEPLOY registry. The date reflects the underlying real-world event, not the registry record's creation date.
- What robot was involved in Russian Su-27 collided with a US MQ-9 Reaper over the Black Sea, forcing it down?
- MQ-9 Reaper by General Atomics Aeronautical Systems is the recorded robot involved in this incident.
- Has anyone responded to Russian Su-27 collided with a US MQ-9 Reaper over the Black Sea, forcing it down?
- No responses to this incident are recorded on the DEPLOY registry. Operators, manufacturers, or affected parties can submit responses to the editorial team; absence is not a guarantee no response was issued.
- What is the current status of Russian Su-27 collided with a US MQ-9 Reaper over the Black Sea, forcing it down?
- This incident is an active record on the DEPLOY registry; no retraction or correction has been issued.
Methodology: Verified · 2 sources (1 primary) · last reviewed 2026-06-24
Verification posture
Verified
High confidence
Review state
Stable
Last reviewed 2026-06-24
Sources by quality tier
- 1
- primary-government-record
- Government record
- 1
- unclassified
- Unclassified source
The framework is documented at /methodology. Corrections at /corrections. Reviewer: DEPLOY editorial team.
Methodology surface for Russian Su-27 collided with a US MQ-9 Reaper over the Black Sea, forcing it down.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 61aa56ba-accc-4552-b29a-77cc0fb6aa94