LAX93LA161 · Cessna 150
Cessna 150 · Accident: airframe, component or system failure during takeoff
Event
- NTSB case
- LAX93LA161
- 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
- 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
- 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 150
- Aircraft type
- Cessna 150
- 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
- N50287
- Operator
- Shively, Harold Et Al · private individual
- Onboard fatalities
- Unknown
- Route
- From not recordedTo 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
- Takeoff · roll/run
- 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
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Stall/mush
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Flt control syst, wing flap control › Inoperative
- Unknown › Maintenance, installation, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT WAS PRACTICING TOUCH AND GO TAKEOFFS AND LANDINGS. THE FLAPS WERE FULLY EXTENDED DURING THE LANDING PHASE OF THE MANEUVER. DURING THE SECOND LANDING ROLL THE PILOT RAISED THE FLAP HANDLE AND BEGAN THE TAKEOFF ROLL. WHEN THE AIRPLANE LIFTED OFF THE PILOT OBSERVED THAT THE FLAPS REMAINED FULLY EXTENDED AND WOULD NOT RAISE. THE PILOT WAS ABLE TO TURN THE AIRPLANE, BUT COULD NOT GAIN ADDITIONAL ALTITUDE WITHOUT THE STALL WARNING HORN ACTIVATING. THE PILOT TURNED THE AIRPLANE TOWARD THE AIRPORT BUT OBSERVED A POWERLINE. THE PILOT WAS UNABLE TO CLIMB OVER THE POWERLINE AND BANKED THE AIRPLANE. THE AIRPLANE STALLED DURING THE BANKING TURN. THE POST ACCIDENT INVESTIGATION REVEALED THAT THE FUSE HAD BLOWN AND WAS THE WRONG TYPE OF FUSE. THE FLAP MOTOR TERMINALS WERE CORRODED AND THE FLAP MOTOR OPERATED INTERMITTENTLY UNDER ALL LOAD CONDITIONS.
Probable cause
THE FAILURE OF THE WING FLAP CONTROL DUE TO THE IMPROPER TYPE OF FUSE INSTALLED BY UNIDENTIFIED PERSONS. FACTORS RELATING TO THIS ACCIDENT WERE THE FLAP MOTOR PARTIAL FAILURE DUE TO CORROSION AND THE TOTAL FAILURE OF THE FUSE DUE TO THE WRONG TYPE AMPERAGE.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX93LA161
- Event ID
- 20001211X12160
- Case number
- LAX93LA161
- 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: 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: f582155f3d17ce6c36848a3b697b2731aea0af056115b915724950cdfcaabd4a; retrieved 2026-09-21T23:00:12.974Z.