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

Kansas City, KS —

OSHA Injury Report: GM Fairfax Assembly

Injury · Other recordable case

At a glance

On , an injury at GM Fairfax Assembly in 3201 Fairfax Trfy, Kansas City, KS 66115 resulted in other recordable case. Employee was assembly Operator MFG in assembly plants, passenger car, on chassis of own manufacture.

Where did this happen?

Establishment
GM Fairfax Assembly
Parent company
General Motors LLC
Street
3201 Fairfax Trfy
City
Kansas City
State
KS
ZIP
66115
On-site location
Dept 25 Column T42 Was not on a job when injury occurred

What was the outcome?

Outcome
Other recordable case (code 4)
Type
Injury (code 1)

Before the incident

Walking back from break to the job

What happened

Employee States I was walking down the middle underneath the car and I ducked down but hit my head on the lower controller of the rear end of the car

Injury or illness

Contusion of unspecified part of head

Object or substance involved

lower controller on rear end of car

Summary line

Contusion of unspecified part of headlower controller on rear end of car

Employee and industry

Job description
Assembly Operator MFG
SOC code
51-2099 — Assemblers and Fabricators, All Other
NAICS code
336111 — Assembly plants, passenger car, on chassis of own manufacture
NAICS vintage
2017
Avg employees
2250
Total hours worked
3609738
EIN
270383222
Establishment ID
1108189
Employer case #
2023 15429

When (timing detail)

Date of incident
Shift started
6:30:00.000
Time of incident
9:00:00.000
Filing year
2023
Submitted
08FEB24:10:45:00

More injuries at GM Fairfax Assembly

View GM Fairfax Assembly's full OSHA safety record →

More injuries in this industry (NAICS 336111)

More injuries in KS

LAWRENCE, KS—

WM 5219

PRATT, KS—

WM 419

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.