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

Minneapolis, MN —

OSHA Injury Report: General Security Services Corporation

Injury · Days away from work

At a glance

On , an injury at General Security Services Corporation in 9110 Meadowview Road, Minneapolis, MN 55245 resulted in days away from work. Employee was technician in patrol services, security.

Where did this happen?

Establishment
General Security Services Corporation
Parent company
General Security Services Corporation
Street
9110 Meadowview Road
City
Minneapolis
State
MN
ZIP
55245
On-site location
Client site

What was the outcome?

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

Before the incident

There was a latch that the employee needed to open to use a tow-able boom lift.

What happened

The latch was spring loaded and when he released the latch the tension on it flipped over and slammed onto his middle finger on his left hand.

Injury or illness

Cut and fracture of left hand middle finger

Object or substance involved

Latch on tow-able boom lift

Summary line

Cut and fracture of left hand middle finger

Employee and industry

Job description
Technician
SOC code
49-2098 — Security and Fire Alarm Systems Installers
NAICS code
561612 — Patrol services, security
NAICS vintage
2012
Avg employees
274
Total hours worked
493056
Establishment ID
736357
Employer case #
3

When (timing detail)

Date of incident
Time of incident
12:00
Filing year
2024
Submitted
16FEB2025:16:25:00

More injuries at General Security Services Corporation

View General Security Services Corporation's full OSHA safety record →

More injuries in this industry (NAICS 561612)

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