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

OSHA Injury Report: Llano Logistics

Injury · Job transfer or restriction

On , an injury at Llano Logistics in 5801 Martin Luther King Jr. Blvd, Lubbock, TX 79404 resulted in job transfer or restriction. Employee was material Handler in warehousing and storage, general merchandise.

Watch Llano Logistics — free Get an email when a new federal OSHA severe-injury report for Llano Logistics is published. One employer, no account, unsubscribe in one click.
Establishment
Llano Logistics
Parent company
Llano Logistics, Inc.
Street
5801 Martin Luther King Jr. Blvd
City
Lubbock
State
TX
ZIP
79404
On-site location
Salvage Dock
Outcome
Job transfer or restriction (code 3)
Type
Injury (code 1)
Days restricted or transferred
19

Team Member was unloading trailers in the salvage building.

Team Member was coming out of a trailer on his pallet jack and did not stop or look for oncoming traffic. This caused another team member traveling on a fork lift down the dock to come in contact with the other team members foot.

Contusions Crush Bruise Left Foot;

Fork-Lift

Fracture of third metatarsal bone of left foot driving into a fork operator - Contusions Crush Bruise on Left Side of Foot; source: Fork-Lift

Job description
Material Handler
SOC code
53-7062 — Laborers and Freight, Stock, and Material Movers, Hand
NAICS code
493110 — Warehousing and storage, general merchandise
NAICS vintage
2022
Avg employees
526
Total hours worked
1057514
EIN
742908772
Establishment ID
144065
Employer case #
806302924
Date of incident
Shift started
13:00:00.000
Time of incident
16:46:00.000
Filing year
2023
Submitted
01MAR24:23:17:00

View Llano Logistics's full OSHA safety record →

087-RCDC

WM 6504

WM 6043

WM 4464

WM 4194

WM 3005

WM 2977

WM 1803

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.