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

Lancaster, TX —

OSHA Injury Report: Oak Creek Homes, Lancaster

Injury · Days away from work

At a glance

On , an injury at Oak Creek Homes, Lancaster in 800 N. I-35 E, Lancaster, TX 75146 resulted in days away from work. Employee was forklift Driver in buildings, mobile, commercial use, manufacturing.

Where did this happen?

Establishment
Oak Creek Homes, Lancaster
Street
800 N. I-35 E
City
Lancaster
State
TX
ZIP
75146
On-site location
Behind plant in parking area

What was the outcome?

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

Before the incident

Driving forklift

What happened

Got stuck in mud and tipping over. Caused small cut to top of head.

Injury or illness

Small cut to top of head

Object or substance involved

Forklift cage

Summary line

Behind plant in parking area Driving forklift and got stuck in mud and tipping over in shallow ditch. Caused small cut to top of head.

Employee and industry

Job description
Forklift Driver
SOC code
53-7051 — Industrial Truck and Tractor Operators
NAICS code
321991 — Buildings, mobile, commercial use, manufacturing
NAICS vintage
2022
Avg employees
305
Total hours worked
724375
Establishment ID
1206731
Employer case #
5

When (timing detail)

Date of incident
Shift started
6:00:00.000
Time of incident
14:00:00.000
Submitted
02MAR24:15:54:00

More injuries at Oak Creek Homes, Lancaster

View Oak Creek Homes, Lancaster's full OSHA safety record →

More injuries in this industry (NAICS 321991)

Indianapolis, IN—

Volumod

Moultrie, GA—

DESTINY

More injuries in TX

AMARILLO, TX—

WM 4464

VICTORIA, TX—

WM 4194

FORT WORTH, TX—

WM 3005

ARLINGTON, TX—

WM 2977

SAN ANTONIO, TX—

WM 1803

Source

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