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

Las Vegas, NV —

OSHA Injury Report: 300 Food and Beverage

Injury · Job transfer or restriction

At a glance

On , an injury at 300 Food and Beverage in 3300 Las Vegas Boulevard South, Las Vegas, NV 89109 resulted in job transfer or restriction. Employee was asst Chef Pastry in casino Hotels.

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

Where did this happen?

Establishment
300 Food and Beverage
Parent company
Treasure Island, LLC.
Street
3300 Las Vegas Boulevard South
City
Las Vegas
State
NV
ZIP
89109
On-site location
Bakery

What was the outcome?

Outcome
Job transfer or restriction (code 3)
Type
Injury (code 1)
Days restricted or transferred
217

Before the incident

Employee was working inside the bakery carrying a 50-pound bag of sugar.

What happened

The employee injured his right shoulder while carrying a 50-pound bag of sugar.

Injury or illness

Right shoulder strain carrying a heavy bag of sugar.

Object or substance involved

50-pound bag of sugar

Summary line

The employee injured his right shoulder while carrying a 50-pound bag of sugar.

Employee and industry

Job description
Asst Chef Pastry
SOC code
35-1011 — Chefs and Head Cooks
NAICS code
721120 — Casino Hotels
NAICS vintage
2012
Avg employees
540
Total hours worked
853523
EIN
880279092
Establishment ID
276411
Employer case #
9

When (timing detail)

Date of incident
Shift started
7:00
Time of incident
9:45
Filing year
2025
Submitted
19JAN26:19:10:00

More injuries at 300 Food and Beverage

View 300 Food and Beverage's full OSHA safety record →

More injuries in this industry (NAICS 721120)

More injuries in NV

Source

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