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

Orlando, FL —

OSHA Injury Report: Baggage Handling System MCO Orlando Airport Main Terminal

Injury · Days away from work

At a glance

On , an injury at Baggage Handling System MCO Orlando Airport Main Terminal in 5774 S Semoran Blvd, Orlando, FL 32822 resulted in days away from work. Employee was baggage Handler in airport baggage handling services.

Where did this happen?

Establishment
Baggage Handling System MCO Orlando Airport Main Terminal
Parent company
Southeast Airport Services
Street
5774 S Semoran Blvd
City
Orlando
State
FL
ZIP
32822
On-site location
BHS area 5 6

What was the outcome?

Outcome
Days away from work (code 2)
Type
Injury (code 1)
Days away from work
56

Before the incident

Moving bags from conveyor belts

What happened

Sprained right arm and shoulder while moving bags in conveyor belt system

Injury or illness

Sprained right arm and shoulder

Object or substance involved

suitcases

Summary line

sprained right arm and shoulder

Employee and industry

Job description
Baggage Handler
SOC code
39-6011 — Baggage Porters and Bellhops
NAICS code
488119 — Airport baggage handling services
NAICS vintage
2022
Avg employees
140
Total hours worked
292180
EIN
462039334
Establishment ID
945319
Employer case #
1

When (timing detail)

Date of incident
Shift started
4:00:00.000
Time of incident
6:20:00.000
Submitted
08JAN24:05:35:00

More injuries at Baggage Handling System MCO Orlando Airport Main Terminal

View Baggage Handling System MCO Orlando Airport Main Terminal's full OSHA safety record →

More injuries in this industry (NAICS 488119)

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 unspecified. ITA Case Detail records are establishment-reported submissions, not OSHA inspections — no per-record IMIS deep link exists.