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

Canton, MI —

OSHA Injury Report: Focusd Logixtics Corporation

Injury · Other recordable case

At a glance

On , an injury at Focusd Logixtics Corporation in 3039 Haverford Dr, Canton, MI 48188 resulted in other recordable case. Employee was delivery Associate in express delivery services (except establishments operating under a universal service obligation).

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

Where did this happen?

Establishment
Focusd Logixtics Corporation
Parent company
Focusd Logixtics Corporation
Street
3039 Haverford Dr
City
Canton
State
MI
ZIP
48188
On-site location
Customer 's house

What was the outcome?

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

Before the incident

delivering packages

What happened

slipped on mud slid into metal steps; hurt shine

Injury or illness

hurt shine

Object or substance involved

hurt shine

Summary line

slipped on mud slid into metal steps; hurt shine

Employee and industry

Job description
Delivery Associate
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
78
Total hours worked
110748
EIN
844121847
Establishment ID
1002931
Employer case #
4

When (timing detail)

Date of incident
Shift started
9:30:00.000
Filing year
2023
Submitted
27FEB24:02:51:00

More injuries at Focusd Logixtics Corporation

View Focusd Logixtics Corporation's full OSHA safety record →

More injuries in this industry (NAICS 492110)

ERLANGER, KY—

CVG RO

More injuries in MI

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.