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

San Jose, CA —

OSHA Injury Report: TransPak - DIV 110 San Jose

Injury · Other recordable case

At a glance

On , an injury at TransPak - DIV 110 San Jose in 520 N. Marburg Way, San Jose, CA 95133 resulted in other recordable case. Employee was assembler I Wood in packing crates, wood, manufacturing.

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

Where did this happen?

Establishment
TransPak - DIV 110 San Jose
Parent company
TransPak
Street
520 N. Marburg Way
City
San Jose
State
CA
ZIP
95133
On-site location
Production Floor

What was the outcome?

Outcome
Other recordable case (code 4)
Type
Injury (code 1)

Before the incident

Employee was working on assembling a panel

What happened

The employee was founding using a hammer and had his hand too close to the red zone and hammered his left thumb

Injury or illness

contusion of left thumb

Object or substance involved

hammer

Summary line

crushing injury to left thumb using a hammer while assembling a panel

Employee and industry

Job description
Assembler I Wood
SOC code
51-2099 — Assemblers and Fabricators, All Other
NAICS code
321920 — Packing crates, wood, manufacturing
NAICS vintage
2012
Avg employees
249
Total hours worked
549998
EIN
941711977
Establishment ID
1008642
Employer case #
110-08182

When (timing detail)

Date of incident
Time of incident
17:50
Filing year
2025
Submitted
28FEB26:05:38:00

More injuries at TransPak - DIV 110 San Jose

View TransPak - DIV 110 San Jose's full OSHA safety record →

More injuries in this industry (NAICS 321920)

More injuries in CA

Rancho Cucamonga, CA—

087-RCDC

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.