FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA06CA079 · Mooney M20R

5 Apr 2006 · Destin, FL, United States

Mooney M20R · Accident: loss of control in flight on approach

From Hattiesburg Bobby L Chain Municipal Airport (HBG) to Destin Executive Airport (DTS)

Report a problem

Event

NTSB case
MIA06CA079
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
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 M20R

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
N4654M
Operator
Unknown
Onboard fatalities
Unknown
Route
From Hattiesburg Bobby L Chain Municipal Airport (HBG), Hattiesburg, MSTo Destin Executive Airport (DTS), Destin, FL
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 go-around
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/mush
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 › Airspeed, not maintained

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot stated that he made a smooth touchdown on the runway centerline, and after a "couple hundred feet", a strong gust of wind blew him to the left toward the runway edge lights. He said he made the decision to go around, applied full throttle, and "pulled up sharply" to avoid hitting the runway lights. He further stated that the stall warning then activated, so he lowered the nose of the airplane but "apparently did not have sufficient airspeed to maintain altitude. He said he tried to turn back to the runway, but felt a sudden "spin" to the left about 30 degrees, as the airplane impacted the ground. Prior to the accident there were no mechanical failures or malfunctions to the airplane or any of its systems.

Probable cause

The pilot's failure to maintain airspeed while attempting a go-around at a low altitude which resulted in an inadvertent stall/mush, an uncontrolled descent and an impact with terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA06CA079
Event ID
20060525X00619
Case number
MIA06CA079
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: e3f06908b64064c8826170328a857e92ef7aa55ca75f32d644a3a68c3e0a4229; retrieved 2026-09-22T05:01:46.181Z.