FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL90FA056 · Cessna 150F

30 Jan 1990 · Weaver, AL, United States

Cessna 150F · Accident: undershoot on approach

Report a problem

Event

NTSB case
ATL90FA056
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 150F

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
N6871F
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
Approach · VFR pattern base
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
Undershoot
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
Tree(s)
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 › Altitude, misjudged
  • Pilot in command › Clearance, not maintained
  • Pilot in command › Distance, misjudged

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

NTSB narrative

AFTER RTRNG FROM A LOCAL FLT, THE PLT BEGAN PRACTICING LANDINGS AT DUSK. HE ELECTED TO MAKE A SIMULATED ENG-OUT LNDG ON RWY 26, WHICH HAD A DISPLACED THRESHOLD & 2320 FT OF USABLE RWY FOR LNDG. HE BEGAN THE APCH WHILE AT 700 FT AGL ON A LEFT DOWNWIND, ABEAM THE DISPLACED THRESHOLD. AS THE ACFT WAS TURNING ONTO FINAL APCH, IT BRUSHED THE TOP OF A TREE. THE PLT LOWERED THE NOSE TO GAIN AIRSPEED, THEN THE ACFT ENTERED AN AREA OF TREES & CRASHED. THE PLT HAD BEEN FLYING A CESSNA 182, BUT THIS WAS THE 1ST FLT IN A CESSNA 150 IN NEARLY A YEAR.

Probable cause

THE PILOT MISJUDGED DISTANCE AND ALTITUDE TO THE RUNWAY DURING A SIMULATED ENGINE-OUT APPROACH, AND FAILED TO MAINTAIN CLEARANCE FROM TREES. FACTORS RELATED TO THE ACCIDENT WERE: DUSK LIGHT CONDITIONS, AND THE PILOT'S LACK OF RECENT EXPERIENCE IN THE MAKE AND MODEL OF AIRCRAFT.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL90FA056
Event ID
20001212X22362
Case number
ATL90FA056
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: b38b4093249fca75344f105a1ee25063c9a6f2f4f15ed9ba266baaa83f55f4dc; retrieved 2026-09-21T15:45:21.650Z.