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

Seattle, WA —

OSHA Injury Report: 3286 - Seattle University Way

Injury · Job transfer or restriction

At a glance

On , an injury at 3286 - Seattle University Way in 4535 University Way NE, Seattle, WA 981E6 resulted in job transfer or restriction. Employee was target Security Specialist.

Watch 3286 - Seattle University Way — free Get an email when a new federal OSHA severe-injury report for 3286 - Seattle University Way is published. One employer, no account, unsubscribe in one click.

Where did this happen?

Establishment
3286 - Seattle University Way
Parent company
Target
Street
4535 University Way NE
City
Seattle
State
WA
ZIP
981E6
On-site location
TM EntranceLobby

What was the outcome?

Outcome
Job transfer or restriction (code 3)
Type
Injury (code 1)
Days restricted or transferred
180

Before the incident

AP Activities

What happened

Other Medical Issue - Back - Lower

Injury or illness

Strain or Tear

Object or substance involved

Numbness-Tingling

Summary line

TM Working in TM Entrance-Lobby and Other Medical Issue involving Numbness-Tingling while doing Other AP Activities injuring Back - Lower

Employee and industry

Job description
Target Security Specialist
SOC code
33-9032 — Security Guards
NAICS code
452112
NAICS vintage
2012
Avg employees
44
Total hours worked
49296
EIN
410215170
Establishment ID
637744
Employer case #
WA23755217

When (timing detail)

Date of incident
Shift started
5:00:00.000
Time of incident
8:00:00.000
Filing year
2023
Submitted
29FEB24:20:23:00

More injuries at 3286 - Seattle University Way

View 3286 - Seattle University Way's full OSHA safety record →

More injuries in this industry (NAICS 452112)

More injuries in WA

VANCOUVER, WA—

WM 5461

MARYSVILLE, WA—

WM 2595

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.