FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

BFO91LA002 · Cessna 150

8 Oct 1990 · Indian Head, MD, United States

Cessna 150 · Accident: loss of control in flight during landing

Report a problem

Event

NTSB case
BFO91LA002
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
N6439G
Operator
Unknown
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
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 › Aircraft control, not maintained

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

NTSB narrative

THE STUDENT PILOT STATED THAT DURING HIS LANDING FLARE THE RIGHT WING TIP 'SUDDENLY' LIFTED, AND THE AIRCRAFT DRIFTED OFF THE LEFT SIDE OF THE RUNWAY. HE REPORTED THAT HE ADDED RIGHT RUDDER AND AILERON, AND FULL POWER TO ATTEMPT A GO-AROUND. HE STATED THAT WHEN HE RAISED THE FLAPS, HE INADVERTENTLY RAISED THEM ALL AT ONCE. THE AIRCRAFT STALLED AND FELL TO THE GROUND RIGHT WING AND NOSE WHEEL FIRST, AND THEN FLIPPED OVER, INVERTED. THE STUDENT PILOT REPORTED 60 HOURS OF TOTAL FLIGHT EXPERIENCE, INCLUDING 51 HOURS IN THE ACCIDENT MAKE AND MODEL AIRCRAFT.

Probable cause

THE STUDENT PILOT'S FAILURE TO MAINTAIN ADEQUATE AIRCRAFT CONTROL DURING THE LANDING FLARE/TOUCHDOWN. CONTRIBUTING FACTORS ARE HIS LACK OF TOTAL FLIGHT EXPERIENCE AND HIS IMPROPER TECHNIQUE WHEN RAISING FLAPS DURING AN ATTEMPTED GO-AROUND.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record BFO91LA002
Event ID
20001212X24414
Case number
BFO91LA002
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: 0b99c9d66424a1828f7749208dd13aaa2367606bf6dbb558e8c365e1c2159b26; retrieved 2026-09-23T05:14:40.159Z.