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

YOSEMITE VALLEY, CA —

OSHA Injury Report: 000009004 YOSEMITE CURRY VILLAGE

Other illness · Days away from work

At a glance

On , an other illness at 000009004 YOSEMITE CURRY VILLAGE in 9013 VILLAGE DRIVE, YOSEMITE VALLEY, CA 95389 resulted in days away from work. Employee was hospitality Wor in hospitality and Leisure.

Where did this happen?

Establishment
000009004 YOSEMITE CURRY VILLAGE
Parent company
Aramark
Street
9013 VILLAGE DRIVE
City
YOSEMITE VALLEY
State
CA
ZIP
95389
On-site location
GROUNDS

What was the outcome?

Outcome
Days away from work (code 2)
Type
Other illness (code 6)
Days away from work
4

Before the incident

SWEEPING FOR TRASH RIDING BIKE

What happened

Employee was working outside during closing down rafts felt really bad half way through day due to heat after finishing sweeping the river for trash road bike back to guest rec office after employee clocked out went to the bathroom threw up once

Injury or illness

Heat stroke Internal organs Hot or cold temps Heat

Object or substance involved

Heat

Summary line

Employee was working outside during closing down rafts felt really bad half way through day due to

Employee and industry

Job description
Hospitality Wor
SOC code
9999 — Uncoded
NAICS code
721110 — Hospitality and Leisure
NAICS vintage
2022
Avg employees
532
Total hours worked
13297
EIN
233102688
Establishment ID
1388664
Employer case #
75474

When (timing detail)

Date of incident
Shift started
7:00
Time of incident
16:40
Filing year
2024
Submitted
02MAR2025:19:51:00

More injuries at 000009004 YOSEMITE CURRY VILLAGE

View 000009004 YOSEMITE CURRY VILLAGE's full OSHA safety record →

More injuries in this industry (NAICS 721110)

More injuries in CA

Rancho Cucamonga, CA—

087-RCDC

Source

Data from OSHA ITA Form 300/301 electronic submissions, filing year 2024. ITA Case Detail records are establishment-reported submissions, not OSHA inspections — no per-record IMIS deep link exists.