FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW90DPA08 · Morris AVID FLYER

9 Sept 1990 · Kerens, TX, United States

Morris AVID FLYER · Accident: loss of control in flight during landing

Report a problem

Event

NTSB case
FTW90DPA08
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

Morris AVID FLYER

Aircraft type
Morris AVID FLYER
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
N7128D
Operator
Morris, Joe M. · private individual
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
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
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Pilot in command › Compensation for wind conditions, improper
  • Pilot in command › Stall, inadvertent

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

NTSB narrative

AT ABOUT 100 FEET AGL ON FINAL APPROACH, THE PILOT HAD THE FLAPERONS FULLY EXTENDED AND ENCOUNTERED A GUST. CONTROL WAS LOST AND THE PILOT ATTEMPTED TO LAND IN AN ADJACENT FIELD. THE AIRPLANE STALLED AND IMPACTED RIGHT LANDING GEAR FIRST AND NOSED OVER. THE PILOT/BUILDER REPORTED THAT THE AIRPLANE FLIGHT MANUAL RECOMMENDED FULL FLAPERONS BE USED AT 20 FEET AGL OR LESS. HE FURTHER RELATED THAT HE WAS NOT ACCUSTOMED TO THE SLOWER ROLL RATE WITH FULL FLAPERONS EXTENDED.

Probable cause

THE PILOT'S IMPROPER COMPENSATION FOR THE WIND CONDITIONS AND THE RESULTANT INADVERTENT STALL. FACTORS RELATED TO THE ACCIDENT WERE: THE GUSTY CROSSWIND CONDITION AND THE PILOT'S EXTENSION OF FULL FLAPERONS BEFORE DESCENDING TO THE PROPER ALTITUDE.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW90DPA08
Event ID
20001212X24254
Case number
FTW90DPA08
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: 5071285f3029459c1ebe9638c49054fbb148ee4f4bdab5c442b6f9e2b676f9cd; retrieved 2026-09-21T23:44:35.257Z.