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

Greer, SC —

OSHA Injury Report: tkSCS Greenville Transportation

Injury · Job transfer or restriction

At a glance

On , an injury at tkSCS Greenville Transportation in 320 Business Parkway Suite F, Greer, SC 29651 resulted in job transfer or restriction. Employee was driver in motor freight carrier, general, local.

Watch tkSCS Greenville Transportation — free Get an email when a new federal OSHA severe-injury report for tkSCS Greenville Transportation is published. One employer, no account, unsubscribe in one click.

Where did this happen?

Establishment
tkSCS Greenville Transportation
Parent company
ThyssenKrupp Materials NA, Inc.
Street
320 Business Parkway Suite F
City
Greer
State
SC
ZIP
29651
On-site location
Off site

What was the outcome?

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

Before the incident

Driving hostler-stepped down

What happened

Stepped down-right ankle popped

Injury or illness

Right ankle sprain

Object or substance involved

Stepping off hostler

Summary line

Stepped off hostler-right ankle popped - sprain

Employee and industry

Job description
Driver
SOC code
53-3032 — Heavy and Tractor-Trailer Truck Drivers
NAICS code
484110 — Motor freight carrier, general, local
NAICS vintage
2022
Avg employees
157
Total hours worked
321087
EIN
320132592
Establishment ID
656287
Employer case #
23-1

When (timing detail)

Date of incident
Shift started
7:00:00.000
Time of incident
8:45:00.000
Filing year
2023
Submitted
26JAN24:16:19:00

More injuries at tkSCS Greenville Transportation

View tkSCS Greenville Transportation's full OSHA safety record →

More injuries in this industry (NAICS 484110)

More injuries in SC

GAFFNEY, SC—

WM 638

Source

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