Hillsboro, OR —
OSHA Injury Report: Lam Research Corp Hillsboro Office
Injury · Job transfer or restriction
At a glance
On , an injury at Lam Research Corp Hillsboro Office in Hillsboro, OR 97006 resulted in job transfer or restriction. Employee was fSE in semiconductor making machinery manufacturing.
Where did this happen?
- Establishment
- Lam Research Corp Hillsboro Office
- Parent company
- Lam Research Corp
- Street
- 2345 NW Overlook Dr. Ste. 125 & 150
- City
- Hillsboro
- State
- OR
- ZIP
- 97006
- On-site location
- in customer fab (RA-ATTD)
What was the outcome?
- Outcome
- Job transfer or restriction (code 3)
- Type
- Injury (code 1)
- Days restricted or transferred
- 21
Before the incident
Performing equipment maintenance
What happened
Employee was kneeling on a raised metal floor while attempting to locate the interlock for the [REDACTED] LF [REDACTED] ([REDACTED]). No knee pads or kneeling protection were used. The employee completed the task without noting any immediate issues but later experienced knee discomfort which progressed to swelling by the [REDACTED].
Injury or illness
Swelling and pain to right knee
Object or substance involved
Raised metal floor surface
Summary line
FSE reported swollen knee after working at floor level on raised metal floor with no knee pads or kneeling protection. FSE found swelling the next day after waking up and went to seek out assessment treatment
Employee and industry
- Job description
- FSE
- SOC code
- 00-9900 — Insufficient Information - NIOSH
- NAICS code
- 333242 — Semiconductor making machinery manufacturing
- NAICS vintage
- 2012
- Avg employees
- 443
- Total hours worked
- 886000
- EIN
- 942634797
- Establishment ID
- 165175
- Employer case #
- 26435
When (timing detail)
- Date of incident
- Shift started
- 8:00
- Time of incident
- 16:00
- Filing year
- 2025
- Submitted
- 20FEB26:02:14: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.