2,098,129Injury reports 132,232Establishments Most recent incident 2025-12-31
Safety Incidents OSHA Severe Injury Reports · 2015–2025

RICHLAND, MS —

OSHA Injury Report: LJS

Injury · Days away from work

At a glance

On , an injury at LJS in 100 CON WAY PL, RICHLAND, MS 39218 resulted in days away from work. Employee was driver Sales Rep in freight Transportation.

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

Where did this happen?

Establishment
LJS
Parent company
XPO Logistics Freight Inc.
Street
100 CON WAY PL
City
RICHLAND
State
MS
ZIP
39218
On-site location
On route

What was the outcome?

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

Before the incident

driving

What happened

Employee was driving when he was hit on the left side by another truck. Sustained injury to left hand hip.

Injury or illness

OTHER SPECIFIC INJURIES

Object or substance involved

V2

Summary line

Employee was driving when he was hit on the left side by another truck. Sustained injury to left hand hip.

Employee and industry

Job description
Driver Sales Rep
SOC code
41-3091 — Sales Representatives of Services, Except Advertising, Insurance, Financial Services, and Travel
NAICS code
484122 — Freight Transportation
NAICS vintage
2012
Avg employees
174
Total hours worked
377692
EIN
942904084
Establishment ID
108366
Employer case #
9.43618E+1

When (timing detail)

Date of incident
Shift started
17:01
Time of incident
22:01
Filing year
2024
Submitted
28FEB2025:20:38:00

More injuries at LJS

RICHLAND, MS—

LJS

RICHLAND, MS—

LJS

RICHLAND, MS—

LJS

RICHLAND, MS—

LJS

RICHLAND, MS—

LJS

View LJS's full OSHA safety record →

More injuries in this industry (NAICS 484122)

MANCHESTER, NH—

XNH

More injuries in MS

TUPELO, MS—

WM 391

Source

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