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: LAXCIRAMP LAX - CARGO RAMP

Injury · Job transfer or restriction

At a glance

On , an injury at LAXCIRAMP LAX - CARGO RAMP in 5758 CENTURY BLVD, LOS ANGELES, CA 90045 resulted in job transfer or restriction. Employee was cargo ramp agen in other Airport Operations.

Where did this happen?

Establishment
LAXCIRAMP LAX - CARGO RAMP
Parent company
Worldwide Flight Services LAX - CARGO RAMP
Street
5758 CENTURY BLVD
City
LOS ANGELES
State
CA
ZIP
90045
On-site location
PLANE

What was the outcome?

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

Before the incident

MOVING PALLETS

What happened

EE was on plane moving pallets he did not see the secondpallet and it caught his heel between the pallet and the floor He reports no visual changes to the left heel however he is unable to put full weight on right foot is walking with a limp and

Injury or illness

Strained Right Ankle Caught in under or between Pallet

Object or substance involved

Pallet

Summary line

EE was on plane moving pallets he did not see the secondpallet and it caught his heel between the

Employee and industry

Job description
cargo ramp agen
SOC code
9999 — Uncoded
NAICS code
488119 — Other Airport Operations
NAICS vintage
2022
Avg employees
70
Total hours worked
179900
EIN
751932711
Establishment ID
1181780
Employer case #
7202

When (timing detail)

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

More injuries at LAXCIRAMP LAX - CARGO RAMP

View LAXCIRAMP LAX - CARGO RAMP'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.