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

Los Angeles, CA —

OSHA Injury Report: Riverlane Logistic

Injury · Other recordable case

At a glance

On , an injury at Riverlane Logistic in 4841 W San Fernando Rd, Los Angeles, CA 90039 resulted in other recordable case. Employee was delivery Driver in courier services (i.e., intercity network) (except establishments operating under a universal service obligation).

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

Where did this happen?

Establishment
Riverlane Logistic
Parent company
Riverlane Logistics LLC
Street
4841 W San Fernando Rd
City
Los Angeles
State
CA
ZIP
90039
On-site location
in apt building

What was the outcome?

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

Before the incident

walking to delivery to dor

What happened

Dog Bite right finger and elbow

Injury or illness

Dog Bite right finger and elbow

Object or substance involved

dog

Summary line

Dog Bite right finger and elbow

Employee and industry

Job description
Delivery Driver
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
96
Total hours worked
155963
EIN
871922769
Establishment ID
1026869
Employer case #
177406

When (timing detail)

Date of incident
Shift started
10:30:00.000
Filing year
2023
Submitted
03MAR24:05:44:00

More injuries at Riverlane Logistic

View Riverlane Logistic'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.