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

Farmington, CT —

OSHA Injury Report: Allegion Stanley Access Technologies

Injury · Other recordable case

At a glance

On , an injury at Allegion Stanley Access Technologies in 65 Scott Swamp Rd, Farmington, CT 06032, Farmington, CT 6032 resulted in other recordable case. Employee was material Handler in doors, metal, manufacturing.

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

Where did this happen?

Establishment
Allegion Stanley Access Technologies
Parent company
Allegion Stanley Access Technologies
Street
65 Scott Swamp Rd, Farmington, CT 06032
City
Farmington
State
CT
ZIP
6032
On-site location
Header Extrusion Storage

What was the outcome?

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

Before the incident

Material handling

What happened

Extrusion fell over from stored upending striking employee 's head

Injury or illness

Laceration

Object or substance involved

Header

Summary line

Laceration to head caused by header extrusion

Employee and industry

Job description
Material Handler
SOC code
53-7062 — Laborers and Freight, Stock, and Material Movers, Hand
NAICS code
332321 — Doors, metal, manufacturing
NAICS vintage
2022
Avg employees
219
Total hours worked
435969
Establishment ID
1336946
Employer case #
IN-2024100

When (timing detail)

Date of incident
Shift started
15:00
Time of incident
23:45
Filing year
2024
Submitted
25FEB2025:21:59:00

More injuries at Allegion Stanley Access Technologies

View Allegion Stanley Access Technologies's full OSHA safety record →

More injuries in this industry (NAICS 332321)

More injuries in CT

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.