2,042,423Injury reports 130,778Establishments Most recent incident 2025-12-31
Safety Incidents OSHA Severe Injury Reports · 2015–2025

Mt. Pleasant, SC —

OSHA Injury Report: Wando Welch Terminal

Injury · Job transfer or restriction

At a glance

On , an injury at Wando Welch Terminal in 400 Long Point Rd, Mt. Pleasant, SC 29464 resulted in job transfer or restriction. Employee was container Handler Operator in port facility operation.

Where did this happen?

Establishment
Wando Welch Terminal
Parent company
South Carolina State Ports Authority
Street
400 Long Point Rd
City
Mt. Pleasant
State
SC
ZIP
29464
On-site location
WWT BD Row

What was the outcome?

Outcome
Job transfer or restriction (code 3)
Type
Injury (code 1)
Days restricted or transferred
180

Before the incident

Moving down BD row in RTG [REDACTED]

What happened

[REDACTED] was moving down BD row in RTG 19. the machine got a fault for the locking pin on the boogie. The [REDACTED] then went to a sudden stop. from this sudden stop he injured his back.

Injury or illness

Lower Back AreaMultiple Trunk

Object or substance involved

Tools Instruments and Equipment - Tools instruments and equipment unspecified

Summary line

While operating RTG equipment the employee injured his back when the equipment came to a sudden stop.

Employee and industry

Job description
Container Handler Operator
SOC code
53-7062 — Laborers and Freight, Stock, and Material Movers, Hand
NAICS code
488310 — Port facility operation
NAICS vintage
2022
Avg employees
560
Total hours worked
1173178
EIN
576000923
Establishment ID
504057
Employer case #
FY24-00040

When (timing detail)

Date of incident
Submitted
01FEB24:20:03:00

More injuries at Wando Welch Terminal

View Wando Welch Terminal's full OSHA safety record →

More injuries in this industry (NAICS 488310)

More injuries in SC

GAFFNEY, SC—

WM 638

Source

Data from OSHA ITA Form 300/301 electronic submissions, filing year unspecified. ITA Case Detail records are establishment-reported submissions, not OSHA inspections — no per-record IMIS deep link exists.