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

HENDERSON, NV —

OSHA Injury Report: FedEx ZLAS G LAS VEGAS 891

Injury · Job transfer or restriction

At a glance

On , an injury at FedEx ZLAS G LAS VEGAS 891 in 470 E. BRUNER AVE, HENDERSON, NV 89044 resulted in job transfer or restriction. Employee was package Handler in courier and Express Delivery Services.

Where did this happen?

Establishment
FedEx ZLAS G LAS VEGAS 891
Parent company
FEDERAL EXPRESS CORPORATION
Street
470 E. BRUNER AVE
City
HENDERSON
State
NV
ZIP
89044
On-site location
WAREHOUSE

What was the outcome?

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

Before the incident

LOADING ON VAN [REDACTED]

What happened

Employee was loading on van line 2 when picking up an NC off the belt the employee twisted her back and heard a noise originating from her lower back

Injury or illness

Strained Low back Lifting Package

Object or substance involved

Package

Summary line

Employee was loading on van line 2 when picking up an NC off the belt the employee twisted her back and heard a noise originating from her lower back

Employee and industry

Job description
Package Handler
SOC code
53-7062 — Laborers and Freight, Stock, and Material Movers, Hand
NAICS code
492110 — Courier and Express Delivery Services
NAICS vintage
2022
Avg employees
572
Total hours worked
437541
EIN
710427007
Establishment ID
1367454
Employer case #
265755

When (timing detail)

Date of incident
Shift started
1:30
Time of incident
5:00
Filing year
2024
Submitted
28FEB2025:01:23:00

More injuries at FedEx ZLAS G LAS VEGAS 891

View FedEx ZLAS G LAS VEGAS 891's full OSHA safety record →

More injuries in this industry (NAICS 492110)

ERLANGER, KY—

CVG RO

More injuries in NV

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.