FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Southwest Airlines Boeing 737 -76Q incident

1 Oct 2008 · Chicago, IL, United States

Boeing 737 -76Q · Incident: landing gear collapse while taxiing

From Kansas City International Airport (MCI) to Chicago Midway International Airport (MDW)

Report a problem

Event

NTSB case
ENG08IA042
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Incident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
0
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
Airline
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Not recorded

Boeing 737 -76Q

Aircraft type
Boeing 737
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N551WN
Onboard fatalities
Unknown
Route
From Kansas City International Airport (MCI), Kansas City, MOTo Chicago Midway International Airport (MDW), Chicago, IL
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 121: Air Carrier
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Taxi · from runway
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Landing gear collapse
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Minor

Cause areas

  • Aircraft › Aircraft systems

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The airplane experienced separation of the right nose landing gear (NLG)wheel assembly as it exited runway after landing. Metallurgical examination revealed that the NLG axle fractured in a transverse plane, and that the failure of the axle was due to intergranular cracking that acted as stress concentrators from which fatigue cracks emanated. The fracture of the right side inboard journal on the NLG inner cylinder assembly was most likely due to the failure of a prior tapered roller bearing. Eventually the size of the fatigue crack and the forces generated during landing were sufficient to drive the crack in overstress, leading to fracture of the inboard journal. The change in ownership of the plane and the monthly swapping of bearings and wheels make it difficult to determine when the bearing failure occurred or why.

Probable cause

The right nose landing gear axle's failure from intergranular and fatigue cracking due to an earlier bearing failure.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ENG08IA042
Event ID
20081219X65313
Case number
ENG08IA042
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 8d8c4e82fd87f923f7f5c3dc96965ef635b39ddc0870aa4e58aa66125926a66f; retrieved 2026-09-15T10:37:11.375Z.