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

WASHINGTON, DC —

OSHA Injury Report: EXPRESS ONE LOGISTICS, INC.-DC

Injury · Other recordable case

At a glance

On , an injury at EXPRESS ONE LOGISTICS, INC.-DC in 3130 V ST NE, WASHINGTON, DC 002E8 resulted in other recordable case. Employee was dRIVER in mESSENGER OR COURIER SERVICE (NJ, NY).

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

Where did this happen?

Establishment
EXPRESS ONE LOGISTICS, INC.-DC
Parent company
EXPRESS ONE LOGISTICS, INC.
Street
3130 V ST NE
City
WASHINGTON
State
DC
ZIP
002E8
On-site location
Roadway

What was the outcome?

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

Before the incident

Approaching an intersection red Toyota made a right turn at a high rate of speed and hit me head on. Minor Back neck

What happened

Hit head on by vehicle make turn at high rate of speed. Minor neck back

Injury or illness

52-Strain or Tear

Object or substance involved

MVA

Summary line

MVA52-Strain or TearMultiple

Employee and industry

Job description
DRIVER
SOC code
43-5021 — Couriers and Messengers
NAICS code
492110 — MESSENGER OR COURIER SERVICE (NJ, NY)
NAICS vintage
2022
Avg employees
116
Total hours worked
454348
EIN
900440420
Establishment ID
1206265
Employer case #
190138908

When (timing detail)

Date of incident
Shift started
9:00:00.000
Time of incident
15:19:00.000
Filing year
2023
Submitted
02MAR24:03:20:00

More injuries at EXPRESS ONE LOGISTICS, INC.-DC

View EXPRESS ONE LOGISTICS, INC.-DC's full OSHA safety record →

More injuries in this industry (NAICS 492110)

ERLANGER, KY—

CVG RO

More injuries in DC

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.