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

GILROY, CA —

OSHA Injury Report: Trevis Berry Transportation

Injury · Other recordable case

At a glance

On , an injury at Trevis Berry Transportation in 655 E. Luchessa Ave., GILROY, CA 95020 resulted in other recordable case. Employee was driver in trucking, general freight, local.

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

Where did this happen?

Establishment
Trevis Berry Transportation
Parent company
Trevis Berry Transportation
Street
655 E. Luchessa Ave.
City
GILROY
State
CA
ZIP
95020
On-site location
Road

What was the outcome?

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

Before the incident

delivering load to customer

What happened

Driver was leaving customers facility stopped at driveway when confronted and assaulted by inpatient driver

Injury or illness

swollen right side check left elbow & buttocks

Object or substance involved

close fist punch by another person

Summary line

swollen right side check left elbow & buttocks

Employee and industry

Job description
Driver
SOC code
53-3032 — Heavy and Tractor-Trailer Truck Drivers
NAICS code
484110 — Trucking, general freight, local
NAICS vintage
2022
Avg employees
52
Total hours worked
126066
EIN
942236774
Establishment ID
1049990
Employer case #
2

When (timing detail)

Date of incident
Shift started
6:00:00.000
Time of incident
14:30:00.000
Filing year
2023
Submitted
01FEB24:18:13:00

More injuries at Trevis Berry Transportation

View Trevis Berry Transportation's full OSHA safety record →

More injuries in this industry (NAICS 484110)

More injuries in CA

Rancho Cucamonga, CA—

087-RCDC

Source

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.