Incident · Property damage
Crane-suspended Unitree H1 thrashed during a factory test and toppled nearby equipment
In viral footage surfacing in early May 2025, a Unitree H1 suspended from a crane/stand began thrashing its limbs without warning, dragged its stand, and knocked a computer and other items to the floor; no injuries. A handler attributed it to running a full-body control policy while the robot's feet were off the ground (an incorrect operating mode). Cap-flags: exact event date undetermined (footage surfaced ~May 1-8 2025); explanation is handler-sourced with no official Unitree statement; root cause could also map to human_operator_error/teleoperation_failure.
Occurred 2025-05-01 · Unitree H1 · Unitree Robotics
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/unitree-h1-crane-test-thrash-2025.md
- JSON-LD: embedded in this page’s head
- REST API: /v1/incidents/ab13a2d5-f6cb-4821-8496-5b81bad0e95b
- Data documentation: /data
- Query this programmatically: Deploy MCP
Outcomes (1)
- property damageverified
Revision history (1)
- 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)
- Robotics & Automation News · https://roboticsandautomationnews.com/2025/05/08/ai-robot-attacks-worker-viral-video-shows-unitree-humanoid-going-berserk/90524/
- Interesting Engineering · https://interestingengineering.com/culture/humanoid-robot-freaks-out-in-viral-video
Common questions
- What happened in Crane-suspended Unitree H1 thrashed during a factory test and toppled nearby equipment?
- In viral footage surfacing in early May 2025, a Unitree H1 suspended from a crane/stand began thrashing its limbs without warning, dragged its stand, and knocked a computer and other items to the floor; no injuries. A handler attributed it to running a full-body control policy while the robot's feet were off the ground (an incorrect operating mode). Cap-flags: exact event date undetermined (footage surfaced ~May 1-8 2025); explanation is handler-sourced with no official Unitree statement; root cause could also map to human_operator_error/teleoperation_failure.
- When did this incident occur?
- The incident is recorded as occurring on May 1, 2025 on the DEPLOY registry. The date reflects the underlying real-world event, not the registry record's creation date.
- What robot was involved in Crane-suspended Unitree H1 thrashed during a factory test and toppled nearby equipment?
- Unitree H1 by Unitree Robotics is the recorded robot involved in this incident.
- Has anyone responded to Crane-suspended Unitree H1 thrashed during a factory test and toppled nearby equipment?
- 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 Crane-suspended Unitree H1 thrashed during a factory test and toppled nearby equipment?
- This incident is an active record on the DEPLOY registry; no retraction or correction has been issued.
Methodology: Verified · 2 sources (no primary) · last reviewed 2026-06-24
Verification posture
Verified
Low confidence
Review state
Stable
Last reviewed 2026-06-24
Sources by quality tier
- 2
- unclassified
- Unclassified source
The framework is documented at /methodology. Corrections at /corrections. Reviewer: DEPLOY editorial team.
Methodology surface for Crane-suspended Unitree H1 thrashed during a factory test and toppled nearby equipment.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 ab13a2d5-f6cb-4821-8496-5b81bad0e95b