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

HAZLEHURST, GA —

OSHA Injury Report: BEASLEY TIMBER COMPANY

Injury · Days away from work

At a glance

On , an injury at BEASLEY TIMBER COMPANY in 712 UVALDA HWY, HAZLEHURST, GA 31539 resulted in days away from work. Employee was tRUCK DRIVER in logging.

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

Where did this happen?

Establishment
BEASLEY TIMBER COMPANY
Parent company
BEASLEY TIMBER COMPANY INC
Street
712 UVALDA HWY
City
HAZLEHURST
State
GA
ZIP
31539
On-site location
JP NEWPORT TRACT LONG CO

What was the outcome?

Outcome
Days away from work (code 2)
Type
Injury (code 1)
Days away from work
104
Days restricted or transferred
140

Before the incident

RELEASING THE LANDING GEAR AND DISCONNECTING THE AIR LINES ON THE EMPTY TRAILER

What happened

TRIPPED ON GROUND DEBRIS ANDFELL ON LEFT SIDE OF TORSO

Injury or illness

STRAI SPRAIN

Object or substance involved

GROUND

Summary line

RELEASING THE LANDING GEAR AND DISCONNECTING THE AIR LINES TRIPPED ON DEBRIS ON THE GROUND AND STRAINED LEFT SHOULDER AND ARM

Employee and industry

Job description
TRUCK DRIVER
SOC code
45-4022 — Logging Equipment Operators
NAICS code
113310 — Logging
NAICS vintage
2022
Avg employees
252
Total hours worked
588345
EIN
582332843
Establishment ID
1212036
Employer case #
4

When (timing detail)

Date of incident
Shift started
19:30
Time of incident
2:00
Filing year
2024
Submitted
28FEB2025:21:56:00

More injuries at BEASLEY TIMBER COMPANY

View BEASLEY TIMBER COMPANY's full OSHA safety record →

More injuries in this industry (NAICS 113310)

More injuries in GA

EASTANOLLEE, GA—

WM 1122

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.