Incident · Fatality
OSHA: Worker asphyxiated after robot started up in un-locked-out cell at JR Wheel (2001)
On December 29, 2001, an employee at JR Wheel Inc. was cleaning up at the end of his shift and entered a robot cell that was not locked out. When the robot machinery started up, it grabbed his neck and pinned him under a wheel rim, asphyxiating him. OSHA accident investigation, inspection 304487655.
Occurred 2001-12-29 · Investigated by OSHA
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/osha-jr-wheel-robot-cell-asphyxia-fatality-2001.md
- JSON-LD: embedded in this page’s head
- REST API: /v1/incidents/b645434d-f1d5-49b5-ba21-80c6c0c7b996
- Data documentation: /data
- Query this programmatically: Deploy MCP
Sources (2)
Common questions
What happened in OSHA: Worker asphyxiated after robot started up in un-locked-out cell at JR Wheel (2001)?
When did this incident occur?
Has anyone responded to OSHA: Worker asphyxiated after robot started up in un-locked-out cell at JR Wheel (2001)?
What is the current status of OSHA: Worker asphyxiated after robot started up in un-locked-out cell at JR Wheel (2001)?
Methodology: Verified · 2 sources (no primary) · last reviewed 2026-07-22
Verification posture
Verified
Low confidence
Review state
Stable
Last reviewed 2026-07-22
Sources by quality tier
- 2
- unclassified
- Unclassified source
The framework is documented at /methodology. Corrections at /corrections. Reviewer: DEPLOY editorial team.
Methodology surface for OSHA: Worker asphyxiated after robot started up in un-locked-out cell at JR Wheel (2001).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 b645434d-f1d5-49b5-ba21-80c6c0c7b996