AI Risk Wire

Cases › physical harm › LR-2026-0579

Shield AI V-BAT drone crashes and injuries at Silicon Valley military startup

Preliminary Why: Publisher not yet named · subject to change

Developing: a major or severe case captured in the last 72 hours. Later changes are logged on the corrections page.

Status: no action reported

Severity major
Reported 5 Jun 2026
Developer and model Shield AI · V-BAT
Industry military

No source states: loss or records, agent tool, could do, deployer.

Severity major: tier: the source names two affected parties, U.S. and Romanian Navy officials, and states bodily injuries to them.

Shield AI's V-BAT military drone was operating in training exercises with U.S. and Romanian Navy officials. The monitor describes the V-BAT as an AI system: an unmanned aerial vehicle with autonomous or semi-autonomous capabilities used for military purposes. What went wrong: the drone caused severe injuries, including severed fingers, despite previous safety improvements. Multiple crashes, ongoing safety complaints and whistleblower allegations of concealed technical flaws are reported, and the latest incident occurred off the Texas coast. The monitor classed the case as an AI incident because the reported injuries were direct physical harm from the system's use. The sources do not state how the events were detected or contained, what remediation followed, or any investigation outcome.

What happened

1 · What went wrongThe drone caused severe injuries, including severed fingers, to U.S. and Romanian Navy officials despite previous safety improvements.

What was done

No source states an action or fix.

Risks

Read from the sources; not yet reviewed by a person.

Controls

Not yet read for controls. Controls that mitigate the primary risk:

Harness

Stop control

Application

Physical safety interlocks · Human approval for high-impact actions · Live behaviour monitoring · Adversarial testing before deployment

Evidence

No source states: what the AI was doing, what it reached or did, how it was caught, when it happened, when it was found, how many records were exposed, the direct loss, a count of the other parties affected, any court case, the cause, what set it off, what was done.

Show the full account: 2 items from the primary sources

What happened, in order

Not dated in the sources:

  • Previous safety improvements were made before the injuries.
  • Multiple crashes and ongoing safety complaints occurred, with whistleblower allegations of concealed technical flaws.
Show every field, with its source and grade

The AI system

Model
V-BAT
C one secondary source states it
Developer
Shield AI
C one secondary source states it
What it was for
military purposes
C one secondary source states it

What happened

Earliest source we hold
2026-06-05
D inferred by us from the described behaviour, reason shown
What went wrong
physical harm
C one secondary source states it
primary risk
RK18
D inferred by us from the described behaviour, reason shown

Impact

Severity
major
D inferred by us from the described behaviour, reason shown
Kind of harm
bodily harm
C one secondary source states it
Who was affected
U.S. and Romanian Navy officials
C one secondary source states it
Why this severity
tier: the source names two affected parties, U.S. and Romanian Navy officials, and states bodily injuries to them.
D inferred by us from the described behaviour, reason shown

Context

Industry
military
C one secondary source states it

Notes on gaps

Whistleblower allegations of concealed flaws are reported as allegations, not findings. No remediation is stated. The record's timeline ordering follows the source's narrative, not dates.

LR-2026-0579 · version 1 · published 2026-11-01 after automatic checks; not yet checked field by field by a person · JSON