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

LOS ANGELES, CA —

OSHA Injury Report: LAX-INFLIGHT

Injury · Days away from work

At a glance

On , an injury at LAX-INFLIGHT in 100 WORLD WAY MEZZANINE LEVEL, LOS ANGELES, CA 90045 resulted in days away from work. Employee was flight Attendan in scheduled Passenger Air Transportation.

Where did this happen?

Establishment
LAX-INFLIGHT
Parent company
Southwest Airlines
Street
100 WORLD WAY MEZZANINE LEVEL
City
LOS ANGELES
State
CA
ZIP
90045
On-site location
ON AIRCRAFT AFT FA JUMPSEAT

What was the outcome?

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

Before the incident

SITTING IN JUMPSEAT

What happened

Pilot made an announcement that they would be using air brakes for short landing the AC planted straight down The hard landing caused FA D pain and discomfort in lower back and waist area FA [REDACTED] was sitting in his jumpseat when landing occurred

Injury or illness

Sprained Low back Struck by Galley equipment F A jumpseat

Object or substance involved

Galley equipment F A jumpseat

Summary line

Pilot made an announcement that they would be using air brakes for short landing the AC planted str

Employee and industry

Job description
Flight Attendan
SOC code
53-2031 — Flight Attendants
NAICS code
481111 — Scheduled Passenger Air Transportation
NAICS vintage
2012
Avg employees
1081
Total hours worked
887952
EIN
741563240
Establishment ID
959448
Employer case #
143982

When (timing detail)

Date of incident
Shift started
7:10
Time of incident
9:30
Filing year
2024
Submitted
17FEB2025:20:19:00

More injuries at LAX-INFLIGHT

View LAX-INFLIGHT'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 2024. ITA Case Detail records are establishment-reported submissions, not OSHA inspections — no per-record IMIS deep link exists.