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

St. Paul, MN —

OSHA Injury Report: Pier Foundry & Pattern Shop, Inc.

Injury · Other recordable case

At a glance

On , an injury at Pier Foundry & Pattern Shop, Inc. in 51 State Street, St. Paul, MN 55107 resulted in other recordable case. Employee was maintenance Technician in foundries, iron (i.e., ductile, gray, malleable, semisteel).

Where did this happen?

Establishment
Pier Foundry & Pattern Shop, Inc.
Parent company
Pier Foundry & Pattern Shop, Inc.
Street
51 State Street
City
St. Paul
State
MN
ZIP
55107
On-site location
Vulcan Line push-off

What was the outcome?

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

Before the incident

Employee was attempting to repair stuck pusher plate on [REDACTED]

What happened

Upon tightening a carriage wheel stored pressure caused the pusher to retract pinching employee 's head between pusher and machine framework.

Injury or illness

Left ear laceration

Object or substance involved

Vulcan line pusher

Summary line

Laceration on left ear from pusher plate retracting

Employee and industry

Job description
Maintenance Technician
SOC code
49-9041 — Industrial Machinery Mechanics
NAICS code
331511 — Foundries, iron (i.e., ductile, gray, malleable, semisteel)
NAICS vintage
2022
Avg employees
57
Total hours worked
118684
EIN
410912672
Establishment ID
307045
Employer case #
16

When (timing detail)

Date of incident
Shift started
6:00:00.000
Time of incident
6:34:00.000
Filing year
2023
Submitted
22FEB24:13:07:00

More injuries at Pier Foundry & Pattern Shop, Inc.

View Pier Foundry & Pattern Shop, Inc.'s full OSHA safety record →

More injuries in this industry (NAICS 331511)

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