Submit incident
Documented

A Factory Robot Killed a Worker Because Nobody Had to Prove It Was Safe to Approach

July 2, 2015
Curated by Team Raidu · Reviewed by Shiva Ganesh
aiid:69View source ↗
LinkedInX

What happened

A machine crushing a worker at an auto-parts plant reads like a routine industrial accident, the kind logged by safety inspectors thousands of times a year and forgotten just as fast. But look closer at what happened at the SKH Metals factory in Manesar, India, and the story narrows to something more specific and more fixable: a robot that had no way of knowing a person had entered its reach.

On July 2, 2015, 24-year-old Ramji Lal was working the line when a piece of metal jammed in the machine near him. He did what workers in that position often do. He reached behind the equipment to clear the obstruction himself, rather than waiting for a formal stoppage. The robot's arm caught him and pierced through his body, killing him at the scene.

The tragedy here is not that a machine malfunctioned. It didn't need to. The robot did exactly what it was built to do, repeat a welding motion on schedule, with no awareness that a human body now occupied the space it was about to move through. That gap, between a machine executing its task and a machine sensing what's actually around it, is where the death happened. A basic presence sensor or a proximity-triggered stop would have caught what human judgment, under production pressure, did not.

This is also a story about process, not just hardware. Nothing in the record suggests Lal followed a lockout procedure before reaching into the machine's zone, and nothing suggests the factory had a system that would have stopped him if he hadn't. Manufacturing floors run on the assumption that workers will occasionally step into a robot's path to fix a small problem quickly. When that assumption isn't paired with an enforced check, a jammed part becomes a fatality.

Ramji Lal's death is a governance failure dressed up as a mechanical one. There was no verification step confirming the machine was actually safe to approach, no record of who cleared it, and no accountability trail after the fact beyond a coroner's report. That absence is precisely the gap accountability infrastructure is meant to close: a provable record of what a system did, who checked it before a human got near it, and when. Without that record, every factory floor is one jammed part away from repeating this.

Reported impact

Affected parties
Not publicly disclosed
Harm type
Not publicly disclosed
Scale
Not publicly disclosed
Financial impact
Not publicly disclosed
Regulatory action
Not publicly disclosed

Classification

Organization
Not publicly disclosed
AI system
Not publicly disclosed
Industry
Not publicly disclosed
Country
Not publicly disclosed
Provider
Not publicly disclosed
Incident type
Not publicly disclosed

Relevant governance controls

Governance control mapping is not available for this record.

  • No controls mappedNot publicly disclosed

Control mapping is analytical. It does not state that any control would have prevented the incident.

Sources and evidence

This record was researched and written by the Index. The event is also catalogued in the following database, which is listed for cross-reference.

AI Incident Database
Also catalogued in
A Factory Robot Killed a Worker Because Nobody Had to Prove It Was Safe to Approach
2015-07-02