MIA02LA027 · Mooney M-20-20
Mooney M-20-20 · Accident: loss of control in flight en route
From Wilson Industrial Air Center Airport (W03) to St. Petersburg Clearwater International Airport (PIE)
Event
- NTSB case
- MIA02LA027
- 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
- Visual Meteorological Cond
Mooney M-20-20
- Aircraft type
- Mooney M-20
- 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
- N5217B
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Wilson Industrial Air Center Airport (W03), Wilson, NCTo St. Petersburg Clearwater International Airport (PIE), St. Petersburg, 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
- 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
- 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
- Visual flight rules (VFR) flight into instrument meteorological conditions (IMC)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Aircraft control, 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
According to information obtained from the FAA, a visual flight rules flight plan had been filed, and the pilot had requested and was receiving VFR flight following. The FAA transcript of communications showed that on November 22, 2001, at 1025, shortly after departing from Wilson Industrial Air Center, Wilson, North Carolina, the pilot had initiated radio communications with Seymour Johnson Air Force Base (AFB) Approach Control. As the flight progressed, communications control had been passed from Seymour Johnson Approach Control, to Fayetteville Approach Control, to Myrtle Beach Approach Control, to Charleston Approach Control. At 1223, the pilot was handed off from Charleston Approach Control to Beaufort Approach Control, and at 1224, the pilot had checked in with Beaufort approach controller, saying that he was at 8,800 feet, and climbing. He then requested to climb to 10,500 feet, to remain clear of clouds, and was given clearance to do so. At 1238, the pilot stated that he had been trying to get above the clouds nice Charleston, and that he was presently at 10,500 feet, and asked if there were any reports on the cloud coverage. He also said that at that time the clouds appeared to be at 10,300 feet. At 1248, the pilot was instructed to contact Jacksonville Center on 126.75 mHZ, and he acknowledged the frequency change. At 1249, the pilot made initial contact with the Jacksonville Center Brunswick radar sector controller, reporting that he was at 10,300 feet. The controller responded with the Brunswick altimeter setting, and informed the pilot to remain VFR at all times. The pilot did not respond. Radar data showed that at 1248, the airplane was at an altitude of 10,700 feet, and at 1250, when the airplane was last seen on radar, it had descended to an altitude of 7000 feet, and was in geographic position 32 degrees 06 minutes 58 seconds north latitude, 080 degrees 23 minutes 13 seconds west longitude There were no subsequent radar contacts or voice communications with the flight. According to information obtained from the U.S. Coast Guard, at 1347, the U.S. Coast Guard received initial notification of the downed airplane and diverted a search and rescue asset to initiate a search. On November 23, 2001, about 0758, a U.S. Coast Guard search and rescue asset observed and recovered airplane related debris floating in the Atlantic Ocean, in position 32 degrees, 01.5 minutes north latitude, 080 degrees, 29.4 minutes west longitude. Airplane related debris was also retrieved in the vicinity of Sea Pines, Hilton Head, South Carolina, and the retrieved debris was examined by an FAA licensed aviation mechanic. The examination revealed that the wreckage was consistent with portions of a Mooney M20. According to the mechanic, fragmented sections of the right wing rear spar at the aileron bellcrank exhibited 60 percent damage due to rot, and the left wing's rear spar at the aileron bell crank exhibited 75 percent damage due to rot. The NTSB conducted a meteorological study of weather in the vicinity of the accident site, and the study revealed the presence of clouds with bases of about 3,500 feet, and an overcast layer with tops of about 11,000 to 13,000 feet, The study also revealed the possibility of light to moderate turbulence and light precipitation within clouds. According to information obtained from the FAA, as well as the pilot's insurance company, the pilot held a private pilot certificate with an airplane single engine land rating, and had accumulated about 170 total flight hours. The pilot did not hold an instrument rating.
Probable cause
The pilot's continued visual flight rules flight into instrument meteorological conditions, which resulted in a loss of control, an uncontrolled descent, and an impact with the water.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA02LA027
- Event ID
- 20011130X02324
- Case number
- MIA02LA027
- 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: b2e631d450a21e218710a2a5c7072f493aaecc0486897e4668e1fa628dd4c0bf; retrieved 2026-09-20T20:17:00.303Z.