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

Rochester, MN —

OSHA Injury Report: Gillette Pepsi Companies - Rochester

Injury · Job transfer or restriction

At a glance

On , an injury at Gillette Pepsi Companies - Rochester in 3393 Commercial Drive SW, Rochester, MN 55902 resulted in job transfer or restriction. Employee was bulk Driver in soft drinks merchant wholesalers.

Where did this happen?

Establishment
Gillette Pepsi Companies - Rochester
Parent company
Gillette Pepsi Companies
Street
3393 Commercial Drive SW
City
Rochester
State
MN
ZIP
55902
On-site location
Customer Account - Kwik Trip

What was the outcome?

Outcome
Job transfer or restriction (code 3)
Type
Injury (code 1)
Days restricted or transferred
180

Before the incident

Delivering product and merchandising product at a customer account.

What happened

The employee was loading up empty shells at a customer account when they felt a sharp pain up and down their spine. They also felt a heat sensation that extended down into their right leg.

Injury or illness

Sharp pain in lower back area.

Object or substance involved

N A

Summary line

Sharp spine pain when lifting empty shells.

Employee and industry

Job description
Bulk Driver
SOC code
9999 — Uncoded
NAICS code
424490 — Soft drinks merchant wholesalers
NAICS vintage
2022
Avg employees
113
Total hours worked
184473
Establishment ID
1071635
Employer case #
4

When (timing detail)

Date of incident
Shift started
4:25
Time of incident
10:00
Filing year
2024
Submitted
15JAN2025:21:31:00

More injuries at Gillette Pepsi Companies - Rochester

View Gillette Pepsi Companies - Rochester's full OSHA safety record →

More injuries in this industry (NAICS 424490)

More injuries in MN

BROOKLYN PARK, MN—

WM 1864

OAK PARK HEIGHTS, MN—

WM 1861

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.