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

Olney, TX —

OSHA Injury Report: Tower Extrusions, Fab.

Injury · Days away from work

At a glance

On , an injury at Tower Extrusions, Fab. in 100 Anderson Pl., Olney, TX 76374 resulted in days away from work. Employee was cNC OPERATOR in fabricated structural metal manufacturing.

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

Where did this happen?

Establishment
Tower Extrusions, Fab.
Parent company
Tower Extrusions, Fab.
Street
100 Anderson Pl.
City
Olney
State
TX
ZIP
76374
On-site location
FAB SHOP

What was the outcome?

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

Before the incident

MOVING PARTS FROM CNC MACHINE

What happened

TM BENT TO MOVE A PART BY HIMSELF AND STRAINED HIS BACK

Injury or illness

STRAIN TO LOWER BACK

Object or substance involved

ALIMINUM PART

Summary line

INFLAMATION FROM OVEREXERTION

Employee and industry

Job description
CNC OPERATOR
SOC code
51-9161 — Computer Numerically Controlled Tool Operators
NAICS code
332312 — Fabricated structural metal manufacturing
NAICS vintage
2022
Avg employees
150
Total hours worked
336987
Establishment ID
1095575
Employer case #
OLN-82

When (timing detail)

Date of incident
Shift started
5:00
Time of incident
15:00
Filing year
2025
Submitted
07JAN26:20:29:00

More injuries at Tower Extrusions, Fab.

View Tower Extrusions, Fab.'s full OSHA safety record →

More injuries in this industry (NAICS 332312)

Lindon, UT—

Lindon

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 2025. ITA Case Detail records are establishment-reported submissions, not OSHA inspections — no per-record IMIS deep link exists.