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

Vancouver, WA —

OSHA Injury Report: Firestone Pacific Foods LLC

Injury · Job transfer or restriction

At a glance

On , an injury at Firestone Pacific Foods LLC in 4211 nw fruit valley road, Vancouver, WA 98660 resulted in job transfer or restriction. Employee was production Lead in fruits, frozen, manufacturing.

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

Where did this happen?

Establishment
Firestone Pacific Foods LLC
Parent company
Firestone Pacific Foods
Street
4211 nw fruit valley road
City
Vancouver
State
WA
ZIP
98660
On-site location
Production Floor

What was the outcome?

Outcome
Job transfer or restriction (code 3)
Type
Injury (code 1)
Days restricted or transferred
61

Before the incident

walking

What happened

foot trip on a pallet of lugs causing a left knee and ankle pain

Injury or illness

injury

Object or substance involved

pallet

Summary line

foot trip on a pallet of lugs causing a left knee and ankle pain

Employee and industry

Job description
Production Lead
SOC code
51-1011 — First-Line Supervisors of Production and Operating Workers
NAICS code
311411 — Fruits, frozen, manufacturing
NAICS vintage
2022
Avg employees
200
Total hours worked
441788
EIN
911634529
Establishment ID
1191483
Employer case #
3

When (timing detail)

Date of incident
Shift started
15:00:00.000
Filing year
2023
Submitted
29FEB24:20:05:00

More injuries at Firestone Pacific Foods LLC

View Firestone Pacific Foods LLC's full OSHA safety record →

More injuries in this industry (NAICS 311411)

More injuries in WA

VANCOUVER, WA—

WM 5461

MARYSVILLE, WA—

WM 2595

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.