A Thai Factory Worker Was Crushed by a Robot Arm, and the Company Blamed Him for It

What happened

In March 2024, a worker at the Vandapac plastics factory in Chonburi province, Thailand, was laying out sheets of metal when a robotic arm slammed down and pinned him to a workbench. Rescuers gave first aid at the scene and transported him to hospital, where he died from his injuries. That much is documented.

The robotic system's manufacturer has not been identified publicly. The arm's age, its safety certifications, and what kind of proximity or motion sensing it was equipped with have all been kept from the public record. What is known is that the robot operated in a zone where a worker was actively handling materials, and that its downward motion met no mechanical barrier and triggered no automatic stop.

Vandapac's response after the death was immediate and unambiguous. A company official told local media that the robot had been functioning correctly and that the man had ducked under the arm at the wrong moment. The official added that the company would provide no further information, and that employees accepted responsibility for accidents that occurred while working. That statement, made in the days after the death, read less like an explanation and more like a preemptive legal posture.

Blaming the worker for entering a robot's operational zone sidesteps the question that actually matters: whether a factory worker should be able to enter that zone at all without the machine halting. Industrial robots routinely work alongside humans placing materials, adjusting components, and clearing obstructions. When that workflow is built into normal operations, the responsibility for preventing a fatal convergence does not sit entirely with the person who got close. It sits with whoever designed the work cell, configured the arm, and signed off on the procedures around it.

What is missing from the public record here is not just a safety investigation but a baseline of verifiable facts: what sensors were active, what safeguards were in place, whether the arm had ever been tested against its own emergency-stop behavior, and whether any of that was logged before the incident or only discussed afterward. Vandapac declined to share system details and directed liability toward the worker. That posture may protect the company in the short term, but it ensures nothing changes. A provable record of what a system did, and what checks were in place before a worker entered its reach, is the only thing that turns accountability into something more than a clause in an employment contract.

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.