Lewiston, ME —
OSHA Injury Report: Lepage Bakeries Park Street LLC
Injury · Job transfer or restriction
At a glance
On , an injury at Lepage Bakeries Park Street LLC in Lewiston, ME 4240 resulted in job transfer or restriction. Employee was production Helper in commercial bakeries.
Where did this happen?
- Establishment
- Lepage Bakeries Park Street LLC
- Parent company
- Lepage Bakeries Park Street LLC
- Street
- 354 Lisbon Street
- City
- Lewiston
- State
- ME
- ZIP
- 4240
- On-site location
- KRD #1 Roll Department
What was the outcome?
- Outcome
- Job transfer or restriction (code 3)
- Type
- Injury (code 1)
- Days restricted or transferred
- 15
Before the incident
Please see answer to Question 15 below for details.
What happened
Employee stated that they were trying to clean under the moulder belt and didnt realize where their hand was. They said that it got caught between the belt and the scraper. The video footage shows that they placed their hand on the belt idler roller while leaning on the equipment. Their finger was between the idler roller and the framework a zerk fitting on the side of the roller came up around and caught their index finger causing a laceration.
Injury or illness
Laceration Cut Open Wound Finger Right Index Finger
Object or substance involved
Zerk fitting from a belt idler roller
Summary line
Laceration Cut Open Wound Finger Right Index Finger Zerk fitting from a belt idler roller Caught in under on between
Employee and industry
- Job description
- Production Helper
- SOC code
- 9999 — Uncoded
- NAICS code
- 311812 — Commercial bakeries
- NAICS vintage
- 2012
- Avg employees
- 185
- Total hours worked
- 403793
- EIN
- 461358637
- Establishment ID
- 705437
- Employer case #
- 183
When (timing detail)
- Date of incident
- Shift started
- 5:55
- Time of incident
- 6:14
- Filing year
- 2024
- Submitted
- 03FEB2025:20:28: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.