LAX93LA175 · Cessna 150K
Proflite Cessna 150K · Accident: loss of control in flight during landing
From L15 · Las Vegas, NV to L15
Event
- NTSB case
- LAX93LA175
- 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 150K
- 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
- N5836G
- Operator
- Proflite
- Onboard fatalities
- Unknown
- Route
- From L15 · Las Vegas, NVTo L15
- 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
- Landing · flare/touchdown
- 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
- Loss of control in flight
- 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
- Substantial
Cause areas
- Pilot in command(cfi) › Airspeed, inadequate
- Pilot in command(cfi) › Recovery from bounced landing, inadequate
- Pilot in command(cfi) › Stall/mush, inadvertent
- Pilot in command(cfi) › Supervision, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE INSTRUCTOR SAID THE STUDENT WAS MAKING A PLANNED FULL STOP LANDING ON RUNWAY 33 AND THE AIRCRAFT BOUNCED BADLY. THE INSTRUCTOR SAID HE TOOK CONTROL OF THE AIRCRAFT, ADDED POWER, RETRACTED THE FLAPS AND ATTEMPTED TO INITIATE A GO AROUND. GROUND WITNESSES OBSERVED THE AIRCRAFT TRAVEL ABOUT 3,000 FEET DOWN THE RUNWAY IN GROUND EFFECT WHILE DRIFTING TO THE LEFT WITH THE WINGS ROCKING BACK AND FORTH. THE AIRCRAFT THEN DESCENDED AND HIT THE GROUND ON THE RIGHT WIND AND NOSE.
Probable cause
THE INSTRUCTOR'S INADEQUATE BOUNCED LANDING RECOVERY AND AIRSPEED MANAGEMENT DURING THE ATTEMPTED GO AROUND, WHICH LED TO AN INADVERTENT STALL AND THE INSTRUCTOR'S INADEQUATE SUPERVISION OF THE FLIGHT. A FACTOR IN THE ACCIDENT WAS THE INSTRUCTOR'S LOW TOTAL TIME AS A FLIGHT INSTRUCTOR.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX93LA175
- Event ID
- 20001211X12170
- Case number
- LAX93LA175
- 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: 620b4865767a63e7b593acc55b82e4fc2c852e01c780ea6471609cf53fc8a656; retrieved 2026-09-23T02:11:22.922Z.