FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX89LA043 · Cessna 150L

9 Nov 1988 · Sacramento, CA, United States

Sacramento Aero Service Cessna 150L · Accident: loss of control in flight during landing

From Q96 to an unrecorded destination

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's aircraft involved. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
LAX89LA043
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 150L Possible conflict

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
N17293
Onboard fatalities
Unknown
Route
From Q96To 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 · aborted
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
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 › Aborted landing, improper
  • Pilot in command › Directional control, not maintained

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

THE STUDENT PLT WAS PRACTICING TOUCH-&-GO LANDINGS ON HIS 3RD INSTRUCTIONAL SOLO FLT. DRG AN APCH TO LAND, THE ACFT WAS SLIGHTLY TO THE RIGHT OF THE RWY. THE STUDENT TRIED TO CORRECT THE SITUATION, THEN DECIDED THE ACFT WAS TOO CLOSE TO THE GROUND. HE ADDED FULL PWR TO GO AROUND. HOWEVER, THE ACFT BEGAN TO DRIFT TO THE LEFT & WAS NOT GAINING ALTITUDE. SUBSEQUENTLY, IT DRIFTED OFF THE RWY & COLLIDED WITH AN UNOCCUPIED AIRPLANE. AFTER THE ACDNT, THE PILOT NOTED THE THROTTLE WAS IN THE FULL FWD PSN & THE FLAPS WERE FULLY EXTENDED. THERE WAS NO RPRTD MECHANICAL FAILURE OR MALFUNCTION PRIOR TO THE ACDNT.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record LAX89LA043
Event ID
20001213X27277
Case number
LAX89LA043
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. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 1988-11-10.
  • API snapshot SHA-256: c3d8904870b7318105f0a7e911596f085991e9d2f39a8c7bd70ac7b83e9350f9; retrieved 2026-09-23T08:26:30.129Z.