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

MIAMI, FL —

OSHA Injury Report: SHASTA BEVERAGES, INC.

Injury · Days away from work

At a glance

On , an injury at SHASTA BEVERAGES, INC. in 3550 NW 110TH STREET, MIAMI, FL 33167 resulted in days away from work. Employee was mAINTENANCE MECHANIC in carbonated soft drinks manufacturing.

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

Where did this happen?

Establishment
SHASTA BEVERAGES, INC.
Parent company
NATIONAL BEVERAGE CORP
Street
3550 NW 110TH STREET
City
MIAMI
State
FL
ZIP
33167
On-site location
MACHINE CONVEYOR BELT

What was the outcome?

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

Before the incident

CHANGE OVER ON THE CONVEYOR

What happened

HAND SLIPPED AND SHARP EDGE CUT HIS FINGER

Injury or illness

LACERATION OF THE FINGER

Object or substance involved

DIVIDER

Summary line

RIGHT THUMB LACERATION

Employee and industry

Job description
MAINTENANCE MECHANIC
SOC code
49-9041 — Industrial Machinery Mechanics
NAICS code
312111 — Carbonated soft drinks manufacturing
NAICS vintage
2022
Avg employees
60
Total hours worked
181440
EIN
942977421
Establishment ID
107418
Employer case #
003-23

When (timing detail)

Date of incident
Shift started
5:30:00.000
Time of incident
8:50:00.000
Filing year
2023
Submitted
15FEB24:20:56:00

More injuries at SHASTA BEVERAGES, INC.

View SHASTA BEVERAGES, INC.'s full OSHA safety record →

More injuries in this industry (NAICS 312111)

More injuries in FL

BROOKSVILLE, FL—

WM 4818

WEST PALM BEACH, FL—

WM 4446

PENSACOLA, FL—

WM 3785

MELBOURNE, FL—

WM 3538

POMPANO BEACH, FL—

WM 2962

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.