San Francisco, CA —
OSHA Injury Report: San Francisco Base Alaska
Injury · Days away from work
At a glance
On , an injury at San Francisco Base Alaska in San Francisco, CA 94128 resulted in days away from work. Employee was customer Service Agent in scheduled air passenger transportation.
Where did this happen?
- Establishment
- San Francisco Base Alaska
- Parent company
- Alaska Airlines
- Street
- Alaska Airlines Terminal 2 D.1.444
- City
- San Francisco
- State
- CA
- ZIP
- 94128
- On-site location
- Security Checkpoint
What was the outcome?
- Outcome
- Days away from work (code 2)
- Type
- Injury (code 1)
- Days away from work
- 9
- Days restricted or transferred
- 10
Before the incident
Agent was heading to Gate assignment from the Ticket Counter
What happened
After going through the turnstile opened up the door that lead to gates. Second step slipped felt ankle twist felt straight on knees and put pressure on her palms. Slowly got up and felt pain in ankle and immediately called [REDACTED]. Had intention to continue gate assignment but walked over to take a seat since it was hurting as she was sitting felt knee soreness ankle started to swell and thought she should not be walking around the gates. [REDACTED] suggested wheelchair agent denied. Assignment got changed to ticket counter messaged [REDACTED].
Injury or illness
Sprain
Object or substance involved
N A
Summary line
Sprained right ankle
Employee and industry
- Job description
- Customer Service Agent
- SOC code
- 43-4051 — Customer Service Representatives
- NAICS code
- 481111 — Scheduled air passenger transportation
- NAICS vintage
- 2012
- Avg employees
- 1560
- Total hours worked
- 1440903
- Establishment ID
- 1011093
- Employer case #
- 969
When (timing detail)
- Date of incident
- Shift started
- 13:30
- Time of incident
- 18:30
- Filing year
- 2025
- Submitted
- 24FEB26:19:02:00
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.