ATL06LA014 · Mooney M20M
Mooney M20M · Accident: wheels up landing
From Pike County Airport (EOP) to Summerville Airport (DYB)
Event
- NTSB case
- ATL06LA014
- 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
- 1 · all aircraft and ground
- Ground fatalities
- Unknown
- 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
Mooney M20M
- Aircraft type
- Mooney M20
- 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
- N43CW
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Pike County Airport (EOP), Waverly, OHTo Summerville Airport (DYB), Summerville, SC
- 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
- Wheels up landing
- 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 › Checklist, not followed
- Pilot in command › Planning/decision, inadequate
- Propeller system/accessories, blade › Blade strike
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
During landing, the pilot failed to extend the landing gear. He stated that he ran through the normal landing check list including putting the landing gear down. At touchdown, the wind picked up and the airplane was going "a little to fast." The airplane bounced and he elected to do a go-around and try again. Witnesses observed the gear up landing, saw the propeller strike the ground, and then the pilot attempted a go-around. He climbed to 500 feet and circled runway 24 twice, and attempted a second landing. After the accident, the pilot stated that during the approach a loss of engine power occurred and he was unable to reach the runway. The airplane collided with trees and subsequently the ground. Examination of the runway found scrape marks and propeller slashes. There were no mechanical problems discovered during the post-accident examination of the airplane.
Probable cause
The pilot's failure to follow the pre-landing checklist which resulted in a gear up landing and subsequent propeller strike. The pilots improper decision to attempt a go-around after the propeller strike, resulted in a loss of engine power and subsequent forced landing, and collision with trees.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL06LA014
- Event ID
- 20051116X01846
- Case number
- ATL06LA014
- 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, coordinates. 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: 7bc91df5372478c279cdad3dce33cd8dd684a9bc716fa4c4a1bf8be014342e1f; retrieved 2026-09-20T17:45:39.392Z.