Birmingham, AL —
OSHA Injury Report: Mayco Industries - Birmingham Main Facility
Injury · Job transfer or restriction
At a glance
On , an injury at Mayco Industries - Birmingham Main Facility in Birmingham, AL 35209 resulted in job transfer or restriction. Employee was operator in nonferrous metal shapes (except aluminum, copper) made by rolling, drawing, or extruding purchased nonferrous metal.
Where did this happen?
- Establishment
- Mayco Industries - Birmingham Main Facility
- Parent company
- Mayco Manufacturing LLC
- Street
- 18 West Oxmoor Road
- City
- Birmingham
- State
- AL
- ZIP
- 35209
- On-site location
- Packaging Department - Table Saw
What was the outcome?
- Outcome
- Job transfer or restriction (code 3)
- Type
- Injury (code 1)
- Days restricted or transferred
- 25
Before the incident
Employee was using table saw to cut wood to make crates for shipping.
What happened
While employee was working on table saw another employee came up and spoke to him. Employee operating the table saw looked up while cutting and ran left index finger into moving saw blade.
Injury or illness
Laceration to left index finger.
Object or substance involved
Moving table saw blade.
Summary line
Employee was using saw to cut when another employee distracted him and he pushed his left index finger into saw blade creating a laceration.
Employee and industry
- Job description
- Operator
- SOC code
- 51-4199 — Metal Workers and Plastic Workers, All Other
- NAICS code
- 331491 — Nonferrous metal shapes (except aluminum, copper) made by rolling, drawing, or extruding purchased nonferrous metal
- NAICS vintage
- 2022
- Avg employees
- 125
- Total hours worked
- 330218
- EIN
- 472367716
- Establishment ID
- 541483
- Employer case #
- 5
When (timing detail)
- Date of incident
- Shift started
- 4:00:00.000
- Time of incident
- 10:30:00.000
- Submitted
- 08MAR24:21:14:00
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.