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

Perrysburg, OH —

OSHA Injury Report: IMCO Carbide Tool Inc.

Injury · Days away from work

At a glance

On , an injury at IMCO Carbide Tool Inc. in 28170 Cedar Park Blvd., Perrysburg, OH 43551 resulted in days away from work. Employee was wheel Technician in inserts, cutting tool, manufacturing.

Where did this happen?

Establishment
IMCO Carbide Tool Inc.
Parent company
IMCO Carbide Tool Inc.
Street
28170 Cedar Park Blvd.
City
Perrysburg
State
OH
ZIP
43551
On-site location
Production Floor - Wheel Grinder

What was the outcome?

Outcome
Days away from work (code 2)
Type
Injury (code 1)
Days away from work
180
Days restricted or transferred
180

Before the incident

Employee was dressing wheels

What happened

Employee was dressing wheels lost focused and reached for knobs but reached into dressing wheel stone.

Injury or illness

Laceration of left ring finger. Partial amputation with reattachment.

Object or substance involved

grinding wheel stone* This machine has since been guarded and fines abated.

Summary line

Employee was dressing wheels lost focused and reached for knobs but reached into dressing wheel stone.

Employee and industry

Job description
Wheel Technician
SOC code
9999 — Uncoded
NAICS code
333515 — Inserts, cutting tool, manufacturing
NAICS vintage
2022
Avg employees
115
Total hours worked
180750
EIN
341237442
Establishment ID
714402
Employer case #
2

When (timing detail)

Date of incident
Shift started
6:59:00.000
Time of incident
10:30:00.000
Submitted
01MAR24:21:04:00

More injuries at IMCO Carbide Tool Inc.

View IMCO Carbide Tool Inc.'s full OSHA safety record →

More injuries in this industry (NAICS 333515)

More injuries in OH

LEWIS CENTER, OH—

WM 2725

EASTLAKE, OH—

WM 1863

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.