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: Seattle Maintenance Alaska

Injury · Job transfer or restriction

At a glance

On , an injury at Seattle Maintenance Alaska in Alaska Service Road Sea Tac Int'l Airport, Seattle, WA 98158 resulted in job transfer or restriction. Employee was machinist in scheduled air passenger transportation.

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

Where did this happen?

Establishment
Seattle Maintenance Alaska
Parent company
Alaska Airlines
Street
Alaska Service Road Sea Tac Int'l Airport
City
Seattle
State
WA
ZIP
98158
On-site location
Aircraft: Other

What was the outcome?

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

Before the incident

Working on 560AS on the horizontal stab jack screw.

What happened

A few trips in and out of the access door with twisting and awkward angles led to the injury.

Injury or illness

Strain

Object or substance involved

Door

Summary line

[REDACTED] left back

Employee and industry

Job description
Machinist
SOC code
51-4041 — Machinists
NAICS code
481111 — Scheduled air passenger transportation
NAICS vintage
2012
Avg employees
640
Total hours worked
977979
Establishment ID
1011165
Employer case #
2446

When (timing detail)

Date of incident
Shift started
1:00
Time of incident
6:29
Filing year
2025
Submitted
23FEB26:23:03:00

More injuries at Seattle Maintenance Alaska

View Seattle Maintenance Alaska's full OSHA safety record →

More injuries in this industry (NAICS 481111)

More injuries in WA

VANCOUVER, WA—

WM 5461

MARYSVILLE, WA—

WM 2595

Source

Data from OSHA ITA Form 300/301 electronic submissions, filing year 2025. ITA Case Detail records are establishment-reported submissions, not OSHA inspections — no per-record IMIS deep link exists.