LAX07LA039 · Cessna 172RG
Golden Wing Flying Club Cessna 172RG · Accident: airframe, component or system failure en route
From Montgomery-Gibbs Executive Airport (MYF) to an unrecorded destination
Event
- NTSB case
- LAX07LA039
- 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
- N28RJ
- Operator
- Golden Wing Flying Club
- Onboard fatalities
- Unknown
- Route
- From Montgomery-Gibbs Executive Airport (MYF)To not recorded
- 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
- En route · cruise
- 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
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
According to a report obtained from the airport manager, the airplane experienced a complete electrical failure during the flight. The pilot elected to return and land at the departure airport. After receiving a clearance to land from the tower (via light gun signal), the pilot prepared for landing and moved the landing gear handle to the down position. The landing gear dropped from their bays, but did not extend and lock into place. The pilot did not pump the emergency landing gear extension handle to lock the landing gear in the down position. As the aircraft touched down on the runway, the main landing gear legs folded back into their retracted position. The left wing and horizontal stabilizer contacted the runway as the aircraft came to a stop in an upright position. The airplane sustained substantial damage to its left horizontal stabilizer. The reason for the electrical failure was not determined.
Probable cause
An undetermined total electrical failure. The pilot's failure to extend the landing gear to the down and locked position was a factor.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX07LA039
- Event ID
- 20061124X01712
- Case number
- LAX07LA039
- 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 2006-11-20.
- API snapshot SHA-256: 7b6f47f2fa935874caf0747d1fedecbd7ddf2177435f3e8f6595f66a2a28f84a; retrieved 2026-09-22T04:13:27.434Z.