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 Mgmt/CS Alaska

Injury · Days away from work

At a glance

On , an injury at Seattle Mgmt/CS Alaska in 17801 International Blvd, Seattle, WA 98158 resulted in days away from work. Employee was lounge Hospitality Host SEA in scheduled air passenger transportation.

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

Where did this happen?

Establishment
Seattle Mgmt/CS Alaska
Parent company
Alaska Airlines
Street
17801 International Blvd
City
Seattle
State
WA
ZIP
98158
On-site location
Non-Aircraft: Other

What was the outcome?

Outcome
Days away from work (code 2)
Type
Injury (code 1)
Days away from work
52

Before the incident

Employee was working normal rotations

What happened

Sounds as though she was working the dishes during her rotation and the frequency of dishes movement strained her arm.

Injury or illness

Strain

Object or substance involved

Dishes

Summary line

Strained left arm

Employee and industry

Job description
Lounge Hospitality Host SEA
SOC code
35-9031 — Hosts and Hostesses, Restaurant, Lounge, and Coffee Shop
NAICS code
481111 — Scheduled air passenger transportation
NAICS vintage
2012
Avg employees
3940
Total hours worked
6038628
Establishment ID
1011201
Employer case #
2637

When (timing detail)

Date of incident
Shift started
4:30
Time of incident
12:00
Filing year
2025
Submitted
26FEB26:19:46:00

More injuries at Seattle Mgmt/CS Alaska

View Seattle Mgmt/CS 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.