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

Plover, WI —

OSHA Injury Report: Biery Cheese Company Plover, WI

Hearing loss · Other recordable case

At a glance

On , a hearing loss at Biery Cheese Company Plover, WI in 4930 Hayes Ave, Plover, WI 54447 resulted in other recordable case. Employee was pT in cheese (except cottage cheese) manufacturing.

Watch Biery Cheese Company Plover, WI — free Get an email when a new federal OSHA severe-injury report for Biery Cheese Company Plover, WI is published. One employer, no account, unsubscribe in one click.

Where did this happen?

Establishment
Biery Cheese Company Plover, WI
Parent company
Biery Cheese Company Plover WI
Street
4930 Hayes Ave
City
Plover
State
WI
ZIP
54447
On-site location
Unknown

What was the outcome?

Outcome
Other recordable case (code 4)
Type
Hearing loss (code 5)

Before the incident

Unknown

What happened

Unknown

Injury or illness

Annual hearing test revealed a mild loss of hearing in the left ear and a severe loss of hearing in the right ear.

Object or substance involved

Unknown

Summary line

Annual hearing test revealed a mild loss of hearing in the left ear and a severe loss of hearing in the right ear.

Employee and industry

Job description
PT
SOC code
9999 — Uncoded
NAICS code
311513 — Cheese (except cottage cheese) manufacturing
NAICS vintage
2022
Avg employees
97
Total hours worked
50248
Establishment ID
1090096
Employer case #
123

When (timing detail)

Date of incident
Shift started
6:30:00.000
Filing year
2023
Submitted
29JAN24:18:01:00

More injuries at Biery Cheese Company Plover, WI

View Biery Cheese Company Plover, WI's full OSHA safety record →

More injuries in this industry (NAICS 311513)

More injuries in WI

CHIPPEWA FALLS, WI—

WM 5373

PLYMOUTH, WI—

WM 3497

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.