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

Lynden, WA —

OSHA Injury Report: Maberry Packing LLC

Injury · Days away from work

At a glance

On , an injury at Maberry Packing LLC in 816 Loomis Trail Rd, Lynden, WA 98264 resulted in days away from work. Employee was raspberry Pruning Seasonal Processing Main Crew in berry (except strawberry) farming.

Where did this happen?

Establishment
Maberry Packing LLC
Parent company
Maberry Packing LLC
Street
816 Loomis Trail Rd
City
Lynden
State
WA
ZIP
98264
On-site location
Outside the lunchroom at 816 Loomis Trail Rd.

What was the outcome?

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

Before the incident

He was sitting on the bench eating his food during a break.

What happened

A car driven by another employee pinned his leg between the car and bench accidentally.

Injury or illness

Broken lower left leg.

Object or substance involved

The car. The employee had moved from a forklift to his car and I think the gas pedals are different he was tired and it was an accident.

Summary line

Broken lower left leg.

Employee and industry

Job description
Raspberry Pruning Seasonal Processing Main Crew
SOC code
45-2092 — Farmworkers and Laborers, Crop, Nursery, and Greenhouse
NAICS code
111334 — Berry (except strawberry) farming
NAICS vintage
2012
Avg employees
300
Total hours worked
628535
EIN
262387050
Establishment ID
962199
Employer case #
jRJYdvUpg

When (timing detail)

Date of incident
Shift started
16:00
Time of incident
3:45
Filing year
2025
Submitted
07JAN26:17:07:00

More injuries at Maberry Packing LLC

View Maberry Packing LLC's full OSHA safety record →

More injuries in this industry (NAICS 111334)

More injuries in WA

VANCOUVER, WA—

WM 5461

MARYSVILLE, WA—

WM 2595

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.