ATL83FKQ02 · Cessna 140
Cessna 140 · Accident: loss of control in flight during landing
From New Albany Union County Airport (M72) to New Albany Union County Airport (M72)
Event
- NTSB case
- ATL83FKQ02
- 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 140
- Aircraft type
- Cessna 140
- 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
- N76379
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From New Albany Union County Airport (M72), New Albany, MSTo New Albany Union County Airport (M72), New Albany, MS
- 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
- 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 › Directional control, not maintained
- Pilot in command › Flare, improper
- Pilot in command › Recovery from bounced landing, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE STUDENT PLT WAS INSTRUCTED TO MAKE 1 OR 2 LANDINGS AFTER RETURNING FROM A SOLO CROSS-COUNTRY FLT. HE WAS UNABLE TO RECALL DETAILS OF THE ACCIDENT, BUT HIS WIFE WAS AT THE AIRPORT & WAS A WITNESS. ACCORDING TO HER, THE PLT MADE A GO-AROUND ON HIS FIRST APPROACH. ON THE SECOND APPROACH, THE ACFT TOUCHED DOWN, BOUNCED ONCE OR TWICE, POWER WAS ADDED & THE ACFT LIFTED OFF. HOWEVER, DURING THE SEQUENCE, THE ACFT ANGLED TO THE LEFT OF THE RWY & SUBSEQUENTLY COLLIDED WITH A ROW OF TREES APRX 360 FT FROM THE RWY CENTERLINE. THE ACFT WAS EXAMINED & AN ENGINE RUN-UP WAS MADE, BUT NO PREIMPACT MECHANICAL MALFUNCTION OF FAILURE WAS FOUND.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ATL83FKQ02
- Event ID
- 20001214X42869
- Case number
- ATL83FKQ02
- 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 1983-05-10.
- API snapshot SHA-256: 31be52150dabc0e63df703c63b198177e0859ef3b65f8106dea9392a72434dc3; retrieved 2026-09-21T17:57:28.779Z.