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: LAXCX00QF LAX - CARGO QF

Injury · Other recordable case

At a glance

On , an injury at LAXCX00QF LAX - CARGO QF in 6555 W. IMPERIAL HWY, LOS ANGELES, CA 90045 resulted in other recordable case. Employee was load Planner in other Airport Operations.

Where did this happen?

Establishment
LAXCX00QF LAX - CARGO QF
Parent company
Worldwide Flight Services LAX - CARGO QF
Street
6555 W. IMPERIAL HWY
City
LOS ANGELES
State
CA
ZIP
90045
On-site location
BY AIRPLANE

What was the outcome?

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

Before the incident

STADING NEXT TO CARGO LOADER

What happened

His foot was hit by a cargo loader There is redness and bruising larger than 2 inches to the top of the right foot He is unable to walk on the foot Resting 9 10 Walking It hurts a lot The pain is throbbing Urgent Care in lieu of ER Recommen

Injury or illness

Bruised Right Foot Struck by object handled Cargo loader

Object or substance involved

Cargo loader

Summary line

His foot was hit by a cargo loader There is redness and bruising larger than 2 inches to the top of

Employee and industry

Job description
Load Planner
SOC code
43-5061 — Production, Planning, and Expediting Clerks
NAICS code
488119 — Other Airport Operations
NAICS vintage
2022
Avg employees
90
Total hours worked
274365
EIN
751932711
Establishment ID
1181791
Employer case #
7735

When (timing detail)

Date of incident
Shift started
7:00
Time of incident
22:50
Filing year
2024
Submitted
27FEB2025:19:56:00

More injuries at LAXCX00QF LAX - CARGO QF

View LAXCX00QF LAX - CARGO QF's full OSHA safety record →

More injuries in this industry (NAICS 488119)

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.