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

San Jose, CA —

OSHA Injury Report: Eloka Logistics LLC

Injury · Days away from work

At a glance

On , an injury at Eloka Logistics LLC in 1710 Little Orchard Street, Eloka Logistics LLC, San Jose, CA 95125 resulted in days away from work. Employee was delivery Associate in courier services (i.e., intercity network) (except establishments operating under a universal service obligation).

Where did this happen?

Establishment
Eloka Logistics LLC
Parent company
Eloka Logistics LLC
Street
1710 Little Orchard Street, Eloka Logistics LLC
City
San Jose
State
CA
ZIP
95125
On-site location
Customers Front Yard

What was the outcome?

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

Before the incident

Employee was entering a customer’s front yard to complete a delivery.

What happened

Employee had to quickly turn and run from two dogs that chased after him after having previously been hidden.

Injury or illness

Strained back and sore heels

Object or substance involved

n a

Summary line

Strained back and sore heels escaping from dog

Employee and industry

Job description
Delivery Associate
SOC code
43-5021 — Couriers and Messengers
NAICS code
492110 — Courier services (i.e., intercity network) (except establishments operating under a universal service obligation)
NAICS vintage
2022
Avg employees
80
Total hours worked
68335
EIN
845161578
Establishment ID
1097851
Employer case #
5

When (timing detail)

Date of incident
Shift started
10:30:00.000
Filing year
2023
Submitted
31JAN24:22:51:00

More injuries at Eloka Logistics LLC

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