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

Apopka, FL —

OSHA Injury Report: Goya Foods of Orlando

Injury · Other recordable case

At a glance

On , an injury at Goya Foods of Orlando in 3001 Shelby Industrial Drive, Apopka, FL 32703 resulted in other recordable case. Employee was territory Manager in general-line groceries merchant wholesalers.

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

Where did this happen?

Establishment
Goya Foods of Orlando
Parent company
Goya Foods of Florida
Street
3001 Shelby Industrial Drive
City
Apopka
State
FL
ZIP
32703
On-site location
Customer

What was the outcome?

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

Before the incident

setting up display

What happened

metal part from display slipped causing a laceration to left thumb

Injury or illness

laceration blood vessel to left thumb

Object or substance involved

metal piece of display

Summary line

lacertion to left thumb

Employee and industry

Job description
Territory Manager
SOC code
44866 — Sales Managers
NAICS code
424410 — General-line groceries merchant wholesalers
NAICS vintage
2012
Avg employees
255
Total hours worked
534903
EIN
111983666
Establishment ID
235805
Employer case #
66420

When (timing detail)

Date of incident
Shift started
8:00
Time of incident
14:00
Filing year
2025
Submitted
03MAR26:18:55:00

More injuries at Goya Foods of Orlando

View Goya Foods of Orlando's full OSHA safety record →

More injuries in this industry (NAICS 424410)

More injuries in FL

BROOKSVILLE, FL—

WM 4818

WEST PALM BEACH, FL—

WM 4446

PENSACOLA, FL—

WM 3785

MELBOURNE, FL—

WM 3538

POMPANO BEACH, FL—

WM 2962

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.