DEPLOYDatabase

Incident · Fatality

Two workers killed in SembCorp Marine shipyard accident

Two workers died after an incident onboard a vessel undergoing repairs at the SembCorp Marine shipyard in Singapore.

Occurred 2007-09-14 · Sembcorp Industries

Machine-readable surfaces

Sources (1)

  1. https://www.lloydslist.com/LL098344/Two-killed-in-SembCorp-Marine-accident

Status history

  • Active · 2026-07-06 · agent:depth

Common questions

What happened in Two workers killed in SembCorp Marine shipyard accident?
Two workers died after an incident onboard a vessel undergoing repairs at the SembCorp Marine shipyard in Singapore.
When did this incident occur?
The incident is recorded as occurring on September 14, 2007 on the DEPLOY registry. The date reflects the underlying real-world event, not the registry record's creation date.
Who was involved in Two workers killed in SembCorp Marine shipyard accident?
The incident is recorded as involving Sembcorp Industries on the DEPLOY registry. No specific robot model is linked to this incident in the registry.
Has anyone responded to Two workers killed in SembCorp Marine shipyard accident?
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 Two workers killed in SembCorp Marine shipyard accident?
This incident is an active record on the DEPLOY registry; no retraction or correction has been issued.
Methodology: Unreviewed · 1 source (no primary) · last reviewed 2026-07-06

Verification posture

Unreviewed

Low confidence

Review state

Stable

Last reviewed 2026-07-06

Sources by quality tier

1
unclassified
Unclassified source

The framework is documented at /methodology. Corrections at /corrections. Reviewer: DEPLOY editorial team.

Methodology surface for Two workers killed in SembCorp Marine shipyard accident.

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 6f325e7f-56aa-47d3-a9da-e7b075e74dac