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

Redding, CA —

OSHA Injury Report: Win-River Resort and Casino

Injury · Days away from work

At a glance

On , an injury at Win-River Resort and Casino in 2100 Redding Rancheria Rd, Redding, CA 96003 resulted in days away from work. Employee was food and Beverage Supervisor in casino hotels.

Watch Win-River Resort and Casino — free Get an email when a new federal OSHA severe-injury report for Win-River Resort and Casino is published. One employer, no account, unsubscribe in one click.

Where did this happen?

Establishment
Win-River Resort and Casino
Parent company
Redding Rancheria dba Win-River Casino Bingo
Street
2100 Redding Rancheria Rd
City
Redding
State
CA
ZIP
96003
On-site location
Overtime Beer Cooler

What was the outcome?

Outcome
Days away from work (code 2)
Type
Injury (code 1)
Days away from work
109
Days restricted or transferred
35

Before the incident

Changing Keg tap

What happened

Backed up while changing keg and knocked over stack of kegs

Injury or illness

Right knee injury

Object or substance involved

Beer Keg

Summary line

Right Knee injury

Employee and industry

Job description
Food and Beverage Supervisor
SOC code
35-1012 — First-Line Supervisors of Food Preparation and Serving Workers
NAICS code
721120 — Casino hotels
NAICS vintage
2022
Avg employees
402
Total hours worked
698944
EIN
680371082
Establishment ID
682504
Employer case #
12773

When (timing detail)

Date of incident
Shift started
10:00:00.000
Time of incident
17:45:00.000
Filing year
2023
Submitted
28FEB24:17:16:00

More injuries at Win-River Resort and Casino

View Win-River Resort and Casino's full OSHA safety record →

More injuries in this industry (NAICS 721120)

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.