LAX85FA193 · Cessna 150M
Aviation Facilities Cessna 150M · Accident: hard landing
Event
- NTSB case
- LAX85FA193
- 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 150M
- 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
- N8190U
- Operator
- Aviation Facilities
- 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
- 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
- Hard landing
- 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 › Carburetor heat, improper use of
- Pilot in command › Go-around, delayed
- Pilot in command › Raising of flaps, premature
Approximate · Estimated position: the centre of Fullerton, CA, the place the record names. Not the accident site.
NTSB narrative
GND WITNESS & THE STUDENT PLT RPTD UPON TOUCHDOWN THE ACFT BEGAN TO BOUNCE. AFTER SEVERAL BOUNCES THE PLT BEGAN TO GO-AROUND UPON REACHING MIDFIELD. AFTER LIFT OFF THE ACFT BEGAN TO SINK AND COLLIDED WITH THE ARPT BOUNDARY FENCE. WHEN EXECUTING THE GO-AROUND THE PLT APPLIED FULL THROTTLE WITHOUT CLOSING THE CARB HEAT & IMMEDIATELY RAISED THE FLAPS. FULL THROTTLE WITH CARB HEAT ON WOULD SIGNIFICANTLY REDUCE THE ENGINE POWER & RAISING THE FLAPS WOULD CAUSE THE ACFT TO DVLP A HIGH SINK RATE UNDER THESE CONDITIONS. THE PLT RPTD SHE HAD EXPERIENCED BOUNCED LNDGS & HAD PERFORMED GO-AROUNDS DURING HER TRAINING, BUT THAT DURING THOSE TIMES SHE WAS DIRECTED BY THE INSTRUCTOR IN THE RECOVERY PROCESS AND SHE HAD NEVER RECEIVED FORMAL INSTRUCTION IN THE RECOVERY PROCESS. THE PLT'S FLIGHT RECORD DISCLOSED NO EVIDENCE THAT THE PLT RECEIVED ANY INSTRUCTION IN THESE AREAS. THE PLT'S LOGBOOK DISCLOSED 3 ENTRIES WHERE THE PLT RECEIVED TRAINING IN GO-AROUND MANEUVERS.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record LAX85FA193
- Event ID
- 20001214X36204
- Case number
- LAX85FA193
- 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: e6a7b50a06c5f1c7a3e2e3c40a06915ec9099c7a67842d1decb28f054dfd56e5; retrieved 2026-09-22T01:54:48.318Z.