FTW98LA059 · Mooney M20F
Mooney M20F · Accident: airframe, component or system failure en route
From De Witt Municipal Airport Whitcomb Field (5M1) to Bill & Hillary Clinton National Airport/Adams Field (LIT)
Event
- NTSB case
- FTW98LA059
- 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
Mooney M20F
- 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
- N2954L
- Operator
- Calvin A. Bohannon · private individual
- Onboard fatalities
- Unknown
- Route
- From De Witt Municipal Airport Whitcomb Field (5M1), De Witt, ARTo Bill & Hillary Clinton National Airport/Adams Field (LIT), Little Rock, AR
- 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
- En route · cruise
- 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
- Airframe, component or system failure
- 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 › Procedures/directives, not followed
- Pilot in command › Wrong runway, selected
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that the cabin door popped open while in cruise flight approximately 10 minutes after takeoff. The pilot added that 'the airplane began to buffet and vibrate.' He further stated that 'the wind noise in the cabin made communications difficult' and the pilot's 12 year old son, who was seated in the right front seat, 'became excited and scared.' The pilot asked Little Rock Approach Control for a vector to the Stuttgart Municipal Airport to land and secure the cabin door. During arrival over the airport, the pilot circled the airport as he attempted to activate the pilot controlled runway lights by clicking on frequency 122.9; however, the pilot was unable to activate any of the runway lights. UNICOM frequency 122.8 MHz was listed as the published frequency to activate the runway lights. The pilot attempted to land on a runway that had been closed and abandoned for over 10 years; its surface was reported to have been partly torn off.
Probable cause
the pilot's failure to activate the runway lights, which led to his selection of a closed/abandoned runway for the landing. Factors relating to the accident were: the unlatched cabin door, and the lack of lighting conditions at dusk.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW98LA059
- Event ID
- 20001208X09184
- Case number
- FTW98LA059
- 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: 9d615bcebf1ff8f7741cefd09e320f2b16dadf6d36f02f6ef5366b53dc3fffbc; retrieved 2026-09-22T18:10:13.369Z.