Safety Incidents OSHA Severe Injury Reports · 2015–2025
2,098,129Injury reports 132,232Establishments Most recent incident 2025-12-31

Los Angeles, CA —

OSHA Injury Report: Los Angeles Base Alaska

Injury · Other recordable case

At a glance

On , an injury at Los Angeles Base Alaska in 600 World Way, Los Angeles, CA 90045 resulted in other recordable case. Employee was flight Attendant in scheduled air passenger transportation.

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

Where did this happen?

Establishment
Los Angeles Base Alaska
Parent company
Alaska Airlines
Street
600 World Way
City
Los Angeles
State
CA
ZIP
90045
On-site location
Aircraft: Galley

What was the outcome?

Outcome
Other recordable case (code 4)
Type
Injury (code 1)

Before the incident

Preparing food and transporting hot trays from AFT Galley to FWD Galley due to INOP ovens in FWD Galley.

What happened

EE stated that the FC oven was INOP and he had to wheel all the food to the AFT ovens. While transporting the food the trays made contact with his skin which caused the burn.

Injury or illness

Burn

Object or substance involved

Food

Summary line

burned right hand arm

Employee and industry

Job description
Flight Attendant
SOC code
53-2031 — Flight Attendants
NAICS code
481111 — Scheduled air passenger transportation
NAICS vintage
2012
Avg employees
1564
Total hours worked
1683818
Establishment ID
1010978
Employer case #
2444

When (timing detail)

Date of incident
Shift started
10:07
Filing year
2025
Submitted
24FEB26:21:31:00

More injuries at Los Angeles Base Alaska

View Los Angeles Base Alaska's full OSHA safety record →

More injuries in this industry (NAICS 481111)

More injuries in CA

Rancho Cucamonga, CA—

087-RCDC

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.