LAX05LA027 · Cessna 172RG
Sheble Aviation Cessna 172RG · Accident: airframe, component or system failure on approach
From HND · Henderson, AZ to Kingman Airport (IGM)
Event
- NTSB case
- LAX05LA027
- 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
- Accident
- 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
- Unknown
- 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
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Cessna 172RG
- Aircraft type
- Cessna 172
- 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
- N6140R
- Operator
- Sheble Aviation
- Onboard fatalities
- Unknown
- Route
- From HND · Henderson, AZTo Kingman Airport (IGM), Kingman, AZ
- 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 91: General Aviation
- 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
- Approach · VFR pattern final
- First occurrenceThe 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
- Airframe, component or system failure
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Landing gear, gear locking mechanism › Inoperative
- Landing gear, normal retraction/extension assembly › Failure
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane landed gear up following a component failure in the airplane's landing gear extension system. As the flight was approaching the airport, the gear was extended, but it failed to lock in the down position. Several attempts using both the normal and emergency extension systems failed to rectify the problem and the instructor decided to land with the gear retracted. Post accident examination revealed that the roller piston and bearing (part numbers 1281019-1 and S1997C7-8) had fallen out of their assembly, thereby allowing the actuator piston assembly to reindex itself on the main gear pivot assembly. This prevented the left main gear from achieving a locked position in the down direction.
Probable cause
Landing gear extension system component failure resulting in a gear up landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX05LA027
- Event ID
- 20041116X01822
- Case number
- LAX05LA027
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2004-11-01.
- API snapshot SHA-256: 114578a32461ee902292be7d43507b3b8c7224b6995b09087393c27d94c6c9a1; retrieved 2026-09-22T06:33:17.561Z.