Cocoa Beach, FL —
OSHA Injury Report: Mako Delivery Service Inc
Injury · Job transfer or restriction
At a glance
On , an injury at Mako Delivery Service Inc in Cocoa Beach, FL 32931 resulted in job transfer or restriction. Employee was delivery Associate in courier services (i.e., intercity network) (except establishments operating under a universal service obligation).
Where did this happen?
- Establishment
- Mako Delivery Service Inc
- Parent company
- Mako Delivery Service Inc
- Street
- 321 Kent Dr.
- City
- Cocoa Beach
- State
- FL
- ZIP
- 32931
- On-site location
- Orange County
What was the outcome?
- Outcome
- Job transfer or restriction (code 3)
- Type
- Injury (code 1)
- Days restricted or transferred
- 31
Before the incident
Driver was rushing to finish her route when trip and fell with a house step Three packages fell to the ground and one of them stayed up right and she fell on it and hurt his body close to where her heart is
What happened
Driver was rushing to finish her route when trip and fell with a house step Three packages fell to the ground and one of them stayed up right and she fell on it and hurt his body close to where her heart is
Injury or illness
Concussion Chest Breast
Object or substance involved
Customers house step
Summary line
Concussion Chest Breast Customers house step Falls different level
Employee and industry
- Job description
- Delivery Associate
- 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
- 90
- Total hours worked
- 108640
- EIN
- 851278729
- Establishment ID
- 1088552
- Employer case #
- 6
When (timing detail)
- Date of incident
- Shift started
- 10:12
- Time of incident
- 20:21
- Filing year
- 2024
- Submitted
- 28FEB2025:17:45:00
Source
Data from OSHA ITA Form 300/301 electronic submissions, filing year 2024. ITA Case Detail records are establishment-reported submissions, not OSHA inspections — no per-record IMIS deep link exists.