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: Foodservice Ledyard - 0680

Injury · Days away from work

At a glance

On , an injury at Foodservice Ledyard - 0680 in 5480 Monterey Rd, Gilroy, CA 95020 resulted in days away from work. Employee was driver Hourly.

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

Where did this happen?

Establishment
Foodservice Ledyard - 0680
Street
5480 Monterey Rd
City
Gilroy
State
CA
ZIP
95020
On-site location
Whitings basement Rear of trailer

What was the outcome?

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

Before the incident

Strain Injury by Lifting

What happened

Lifting cases in the rear of trailer EE stated he felt a sharp pain in his lower back area

Injury or illness

Cause Strain or Injury By Body Part Low Back Area Body Part Position Detail Cause Strain Injury by Lifting

Object or substance involved

Product Freight 40 70 lbs

Summary line

Cause Strain or Injury By Body Part Low Back Area Body Part Position Detail Cause Strain Injury by Lifting

Employee and industry

Job description
Driver Hourly
SOC code
9999 — Uncoded
NAICS code
424410
NAICS vintage
2022
Avg employees
211
Total hours worked
457196
EIN
840629503
Establishment ID
206104
Employer case #
1201WC2403

When (timing detail)

Date of incident
Shift started
2:00:00.000
Time of incident
6:00:00.000
Filing year
2023
Submitted
06MAR24:17:55:00

More injuries at Foodservice Ledyard - 0680

View Foodservice Ledyard - 0680's full OSHA safety record →

More injuries in this industry (NAICS 424410)

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.