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

SAN BERNARDINO, CA —

OSHA Injury Report: CASBE - SAN BERNARDINO

Injury · Other recordable case

At a glance

On , an injury at CASBE - SAN BERNARDINO in 1457 E. VICTORIA AVE, SAN BERNARDINO, CA 92408 resulted in other recordable case. Employee was package Driver in couriers and Express Delivery Services.

Where did this happen?

Establishment
CASBE - SAN BERNARDINO
Parent company
UPS
Street
1457 E. VICTORIA AVE
City
SAN BERNARDINO
State
CA
ZIP
92408
On-site location
Residential

What was the outcome?

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

Before the incident

Employee was attempting to deliver a signature required package

What happened

Driver delivering signature required package customer opened door Dog was inside loose Driver began to distance himself dog launched himself and bit driver in abdomen

Injury or illness

Skin Injury

Object or substance involved

Dog bit driver on the abdomen

Summary line

Driver delivering signature required package customer opened door Dog was inside loose Driver began to distance himself dog launched himself and bit driver in abdomen

Employee and industry

Job description
Package Driver
SOC code
43-5021 — Couriers and Messengers
NAICS code
492110 — Couriers and Express Delivery Services
NAICS vintage
2022
Avg employees
311
Total hours worked
407603
EIN
582480149
Establishment ID
1105612
Employer case #
WC648D760

When (timing detail)

Date of incident
Shift started
9:00
Time of incident
17:58
Filing year
2025
Submitted
27FEB26:20:14:00

More injuries at CASBE - SAN BERNARDINO

View CASBE - SAN BERNARDINO'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 2025. ITA Case Detail records are establishment-reported submissions, not OSHA inspections — no per-record IMIS deep link exists.