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

Lewiston, ME —

OSHA Injury Report: Lewiston Manufacturing

Other illness · Other recordable case

At a glance

On , an other illness at Lewiston Manufacturing in 75 Westminster Street, Lewiston, ME 04210 resulted in other recordable case. Employee was stitcher II in leather footwear manufacturing.

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

Where did this happen?

Establishment
Lewiston Manufacturing
Parent company
L.L. Bean, Inc.
Street
75 Westminster Street
City
Lewiston
State
ME
ZIP
04210
On-site location
Lewiston MFG Boat and Tote

What was the outcome?

Outcome
Other recordable case (code 4)
Type
Other illness (code 6)

Before the incident

he was moved to a new position as a stitcher in Boat and Tote closing.

What happened

over time employee developed bilat shoulder and L wrist discomfort

Injury or illness

Bilat shoulder myofascial pain syndrome

Object or substance involved

Repetitive use

Summary line

Bilat shoulder myofascial pain syndrome Repetitive use

Employee and industry

Job description
Stitcher II
SOC code
51-6042 — Shoe Machine Operators and Tenders
NAICS code
316210 — Leather footwear manufacturing
NAICS vintage
2022
Avg employees
149
Total hours worked
243902
EIN
10026590
Establishment ID
1087723
Employer case #
2023-17593

When (timing detail)

Date of incident
Shift started
15:00:00.000
Filing year
2023
Submitted
30JAN24:15:47:00

More injuries at Lewiston Manufacturing

View Lewiston Manufacturing's full OSHA safety record →

More injuries in this industry (NAICS 316210)

MILWAUKEE, WI—

ANODYNE

More injuries in ME

SCARBOROUGH, ME—

WM 1788

Source

Data from OSHA ITA Form 300/301 electronic submissions, filing year 2023. ITA Case Detail records are establishment-reported submissions, not OSHA inspections — no per-record IMIS deep link exists.