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 · Days away from work

At a glance

On , an injury at 300 Food and Beverage in 3300 Las Vegas Boulevard South, Las Vegas, NV 89109 resulted in days away from work. Employee was kitchen Worker 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
Coffee Shop kitchen

What was the outcome?

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

Before the incident

Employee was lifting plates for the hot line inside the Coffee [REDACTED]

What happened

Employee felt a hot pull and burning sensation in her left arm while lifting plates

Injury or illness

Left arm strain with hot pull and burning sensation lifting plates

Object or substance involved

Lifting plates

Summary line

Employee felt a hot pull and burning sensation in her left arm while lifting plates

Employee and industry

Job description
Kitchen Worker
SOC code
35-2021 — Food Preparation Workers
NAICS code
721120 — Casino Hotels
NAICS vintage
2012
Avg employees
540
Total hours worked
853523
EIN
880279092
Establishment ID
276411
Employer case #
11

When (timing detail)

Date of incident
Shift started
8:00
Time of incident
9:15
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.