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

San Jose, CA —

OSHA Injury Report: Amazon.com Services LLC - DXC8

Injury · Other recordable case

At a glance

On , an injury at Amazon.com Services LLC - DXC8 in 1710 Little Orchard Rd, San Jose, CA 95125 resulted in other recordable case. Employee was sortation Associate in couriers and Express Delivery Services.

Watch Amazon.com Services LLC - DXC8 — free Get an email when a new federal OSHA severe-injury report for Amazon.com Services LLC - DXC8 is published. One employer, no account, unsubscribe in one click.

Where did this happen?

Establishment
Amazon.com Services LLC - DXC8
Parent company
Amazon.com Services LLC
Street
1710 Little Orchard Rd
City
San Jose
State
CA
ZIP
95125
On-site location
B cluster aisle 19

What was the outcome?

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

Before the incident

stowing non-cons

What happened

While unloading a u-boat AA was struck on the bicep of their right arm by a falling package.

Injury or illness

strain

Object or substance involved

Box package;Non-con box

Summary line

strain

Employee and industry

Job description
Sortation Associate
SOC code
53-7062 — Laborers and Freight, Stock, and Material Movers, Hand
NAICS code
492110 — Couriers and Express Delivery Services
NAICS vintage
2012
Avg employees
186
Total hours worked
270236
EIN
820544687
Establishment ID
884843
Employer case #
8

When (timing detail)

Date of incident
Shift started
3:20
Time of incident
7:19
Filing year
2024
Submitted
25FEB2025:17:43:00

More injuries at Amazon.com Services LLC - DXC8

View Amazon.com Services LLC - DXC8's full OSHA safety record →

More injuries in this industry (NAICS 492110)

ERLANGER, KY—

CVG RO

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.