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

Richmond, VA —

OSHA Injury Report: Richmond Terminal

Injury · Days away from work

At a glance

On , an injury at Richmond Terminal in 2841 Charles City Rd, Richmond, VA 23231 resulted in days away from work. Employee was sHOP in general freight trucking, long-distance, less-than-truckload (LTL).

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

Where did this happen?

Establishment
Richmond Terminal
Parent company
Swift Transportation Co of Arizona LLC
Street
2841 Charles City Rd
City
Richmond
State
VA
ZIP
23231
On-site location
Richmond VA

What was the outcome?

Outcome
Days away from work (code 2)
Type
Injury (code 1)
Days away from work
3

Before the incident

TRAILER DOOR HANDLE HIT FACE

What happened

Struck or Injured NOC

Injury or illness

NOSE LACERATION

Object or substance involved

TRAILER DOORS

Summary line

Laceration Nose

Employee and industry

Job description
SHOP
SOC code
49-3031 — Bus and Truck Mechanics and Diesel Engine Specialists
NAICS code
484122 — General freight trucking, long-distance, less-than-truckload (LTL)
NAICS vintage
2022
Avg employees
333
Total hours worked
831168
EIN
860265030
Establishment ID
751951
Employer case #
2.31122E+1

When (timing detail)

Date of incident
Shift started
5:25:00.000
Time of incident
5:25:00.000
Filing year
2023
Submitted
27FEB24:22:04:00

More injuries at Richmond Terminal

View Richmond Terminal's full OSHA safety record →

More injuries in this industry (NAICS 484122)

MANCHESTER, NH—

XNH

More injuries in VA

DANVILLE, VA—

WM 4996

COVINGTON, VA—

WM 2662

MADISON HEIGHTS, VA—

WM 2565

FREDERICKSBURG, VA—

WM 1833

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.