FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA12FA566 · Mooney M20M

17 Sept 2012 · Crane Hill, AL, United States

Mooney M20M · Accident: loss of control in flight en route

From DTN · Destin, FL to M33 · Gallatin, TN

Report a problem

Event

NTSB case
ERA12FA566
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
2 · 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
Instrument 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
N1085A
Operator
Unknown
Onboard fatalities
Unknown
Route
From DTN · Destin, FLTo M33 · Gallatin, TN
Aircraft age
About 23 years (built 1989)
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
Defining eventThe 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
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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Action/decision

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

NTSB narrative

The pilot initially delayed the cross-country flight for convective weather, but later took off, encountered weather in a climb, and advised an air traffic controller that he was looking at "ADS-B" (Automatic Dependent Surveillance-Broadcast). As the flight progressed, the airplane climbed to 13,000 feet, and the pilot asked the next controller if there were any reports of icing ahead about 15,000 feet. The controller noted no reports of icing, "but quite a bit of deviation, quite a bit of clouds and precipitation in front of you." The pilot requested 15,000 feet "to see if I can see things better," which was approved by the controller. Upon switching to the next controller, the pilot was advised of moderate to extreme precipitation for the next 90 miles.

The pilot then stated that in looking at the ADS-B, he needed to deviate. Deviation was approved, and, 2 minutes later, the pilot advised the controller that he was making another deviation, which the controller acknowledged. Eighteen minutes after that, the controller told the pilot to change radio frequency, and the pilot responded, "unable, we're battling some pretty bad...". The airplane subsequently made numerous turns and altitude excursions, turning 90 degrees to the right and descending to 14,600 feet, then turning another 90 degrees right and descending to 14,100 feet. After making a sharp left turn, the airplane climbed to 15,500 feet, then made another sharp left turn, and, as it began a final rapid descent to the ground, the pilot issued several mayday calls.

An examination of the wreckage revealed no mechanical anomalies that would have precluded normal operation.

The expected ADS-B cockpit depiction compared to real-time, ground-based radar indicated significant differences in the depiction of hazardous reflectivity (rain). In the ADS-B product, the airplane was depicted as being clear of moderate or heavy rain as it made its final various turns. However, rea-time radar imagery indicated that the airplane would have been in or near moderate-to-heavy rain.

The pilot indicated to the controller that he was using ADS-B in a tactical manner; however, ADS-B is intended to be used in a strategic manner . It is unknown why the pilot lost control of the airplane in moderate-to-heavy rain; he may have become confused and lost situational awareness when turning into what he thought were clearer conditions per the ADS-B depiction but was actually worse weather. ADS-B does not show what the weather is; it shows what the weather was up to 15 to 20 minutes earlier.

Probable cause

The pilot’s loss of control in moderate-to-heavy rain. Contributing to the accident was the pilot’s reliance on ADS-B for tactical weather avoidance.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA12FA566
Event ID
20120917X63831
Case number
ERA12FA566
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 63767d143c55ecf2a9fecfb090b0c6424d58532867cdf6294d1242bfe46c0dba; retrieved 2026-09-14T15:44:50.683Z.