Duncan, SC —
OSHA Injury Report: Duncan
Injury · Other recordable case
At a glance
On , an injury at Duncan in Duncan, SC 29334 resulted in other recordable case. Employee was utility Worker in general Warehousing and Storage.
Where did this happen?
- Establishment
- Duncan
- Parent company
- The Timken Company Duncan DC
- Street
- 120 Hidden Lake Circle
- City
- Duncan
- State
- SC
- ZIP
- 29334
- On-site location
- Rail area
What was the outcome?
- Outcome
- Other recordable case (code 4)
- Type
- Injury (code 1)
Before the incident
The employee was using his personal pocket knife to cut a banding strap The banding was hard to cut and when the knife went through the banding strap it slipped off and struck his left forearm causing a laceration app 1 1 2 inches
What happened
The employee was using his personal pocket knife to cut a banding strap The banding was hard to cut and when the knife went through the banding strap it slipped off and struck his left forearm causing a laceration app 1 1 2 inches
Injury or illness
Laceration Cut Open Wound Arm Left Forearm
Object or substance involved
The mechanism of injury was his personal pocket knife
Summary line
The employee was using his personal pocket knife to cut a banding strap The banding was hard to cut and when the knife went through the banding strap it slipped off and struck his left forearm causing a laceration app 1 1 2 inches
Employee and industry
- Job description
- Utility Worker
- SOC code
- 53-7062 — Laborers and Freight, Stock, and Material Movers, Hand
- NAICS code
- 493110 — General Warehousing and Storage
- NAICS vintage
- 2022
- Avg employees
- 238
- Total hours worked
- 409414
- EIN
- 341878497
- Establishment ID
- 345103
- Employer case #
- 38
When (timing detail)
- Date of incident
- Shift started
- 7:00:00.000
- Time of incident
- 7:35:00.000
- Submitted
- 29FEB24:21:16:00
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.