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: Ready 2 Go Logistics

Injury · Days away from work

At a glance

On , an injury at Ready 2 Go Logistics in 2150 N. 1st St. Suite 457, San Jose, CA 95131 resulted in days away from work. Employee was driver in express delivery services (except establishments operating under a universal service obligation).

Where did this happen?

Establishment
Ready 2 Go Logistics
Parent company
Ready 2 Go Logistics
Street
2150 N. 1st St. Suite 457
City
San Jose
State
CA
ZIP
95131
On-site location
Customers House

What was the outcome?

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

Before the incident

Getting a package inside of the company van to deliver to a customer.

What happened

Slipped out of the van after stepping on the stair with their right foot.

Injury or illness

Right ankle sprain init left scapula init low back pain unspecified lumbar muscle strain init.

Object or substance involved

Employee stepping down onto step and falling slipping.

Summary line

Right Ankle side of body

Employee and industry

Job description
Driver
SOC code
43-5021 — Couriers and Messengers
NAICS code
492110 — Express delivery services (except establishments operating under a universal service obligation)
NAICS vintage
2022
Avg employees
57
Total hours worked
104475
EIN
834204661
Establishment ID
727060
Employer case #
1

When (timing detail)

Date of incident
Shift started
9:45:00.000
Time of incident
13:13:00.000
Filing year
2023
Submitted
29FEB24:17:50:00

More injuries at Ready 2 Go Logistics

View Ready 2 Go Logistics'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.