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

Beaumont, CA —

OSHA Injury Report: BEAUMONT JUICE, INC.

Skin disorder · Job transfer or restriction

At a glance

On , a skin disorder at BEAUMONT JUICE, INC. in 550 B Street, Beaumont, CA 92223 resulted in job transfer or restriction. Employee was oil Operator in beverages, fruit and vegetable juice, manufacturing.

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

Where did this happen?

Establishment
BEAUMONT JUICE, INC.
Parent company
Perricone Juice
Street
550 B Street
City
Beaumont
State
CA
ZIP
92223
On-site location
Inside extraction room. Frit tank

What was the outcome?

Outcome
Job transfer or restriction (code 3)
Type
Skin disorder (code 2)
Days restricted or transferred
52

Before the incident

Cleaning out frit trank

What happened

Employee submerged both arms inside frit tank without wearing proper PPE

Injury or illness

Both arms suffered 2nd degree burns

Object or substance involved

Frit tank chemical

Summary line

Second degree chemical burn on both forearms while cleaning frit tank

Employee and industry

Job description
Oil Operator
SOC code
9999 — Uncoded
NAICS code
311421 — Beverages, fruit and vegetable juice, manufacturing
NAICS vintage
2022
Avg employees
254
Total hours worked
489083
Establishment ID
850721
Employer case #
4

When (timing detail)

Date of incident
Shift started
15:00:00.000
Time of incident
19:00:00.000
Filing year
2023
Submitted
02MAR24:05:01:00

More injuries at BEAUMONT JUICE, INC.

View BEAUMONT JUICE, INC.'s full OSHA safety record →

More injuries in this industry (NAICS 311421)

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.