FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR22FA210 · Mooney Aircraft CORP. M20K

10 Jun 2022 · Camarillo, CA, United States

Mooney Aircraft CORP. M20K · Accident: loss of control in flight during takeoff

From Camarillo International Airport (CMA) to Phoenix Deer Valley Airport (DVT)

Report a problem

Event

NTSB case
WPR22FA210
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
Instrument Meteorological Cond

Mooney Aircraft CORP. M20K

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
N305L
Operator
Unknown
Onboard fatalities
Unknown
Route
From Camarillo International Airport (CMA), Camarillo, CATo Phoenix Deer Valley Airport (DVT), Phoenix, AZ
Aircraft age
About 41 years (built 1981)
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
Takeoff
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
Destroyed

Cause areas

  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Psychological
  • Personnel issues › Task performance

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

NTSB narrative

The instrument-rated pilot planned to fly to his home base. The departure airport was enveloped in marine layer conditions with low visibility, mist, and clouds tops between 400 and 1,600 ft. The pilot received this weather information during a briefing about 30 minutes before departure, during which he filed an instrument flight rules (IFR) flight plan with a visual flight rules (VFR)-on-top clearance.

The pilot was unfamiliar with the airport. After making a wrong turn, the pilot was given taxi instructions to the departure runway. The engine run-up and takeoff appeared uneventful, and the pilot’s communication with the control tower was routine.

Shortly after takeoff, the airplane likely entered the clouds, and the pilot was instructed to contact the departure controller. Although the pilot acknowledged the instruction, he did not contact the departure controller.

A short time later, a witness who was driving along a freeway parallel to the departure runway saw a low-flying airplane that was traveling perpendicular to the takeoff direction. The airplane did not appear to have any trailing smoke or vapors. The airplane then impacted the ground just past the freeway. A video from the witness’ dashboardmounted camera captured the flames from the impact and showed the fog and low clouds enveloping the area. The reported weather observations matched the weather conditions observed in both the security camera video and the dashboard camera video.

Engine and propeller evidence and the associated propeller ground scars indicated that the engine was producing high levels of power at impact. The airplane was equipped with conventional vacuum and electrically powered flight instruments. Although the autopilot and flight instruments were destroyed due to impact and thermal damage, the vacuum pump, which had recently been installed, was recovered and found to be operational. Also, evidence within the wreckage indicated that the airplane was configured appropriately for the initial takeoff climb, with the landing gear retracted and the trim set for takeoff. Thus, the loss of control did not occur due to a loss of engine power, a preimpact mechanical malfunction or failure, or pilot error in configuring the airplane for takeoff.

The pilot’s logbook showed only the flight time required to meet Federal Aviation Administration (FAA) currency requirements; and based on his entries, while he had undergone a flight review the year prior, it appeared that he was not instrument current at the time of the accident.

The airport area is provided with radar and automatic dependent surveillancebroadcast (ADS-B) coverage that starts between 250 and 500 ft above ground level (agl), but neither system tracked the airplane. Thus, the airplane likely did not reach an altitude that would allow the airplane to be tracked after it entered the clouds. The pilot was required to make a slight right turn after departure; however, the airplane’s rapid change in direction after takeoff along with its high impact speed (as shown by ground scar and video evidence) are consistent with the pilot encountering spatial disorientation in the clouds, resulting in a loss of airplane control. It is possible that that the pilot might have been distracted as he configured the airplane for the initial climb and reached over to switch to the departure controller’s frequency.

The pilot had cardiovascular disease, including moderate coronary artery disease, an implanted pacemaker/defibrillator, and mitral valve replacement. The pilot’s medical certificate had expired 6 years before the accident. In 2019 he began flying under the provisions of BasicMed, which is an alternate way for pilots to fly without holding an FAA medical certificate. The pilot’s history of mitral valve replacement would have required a special issuance medical certificate for BasicMed. No such issuance was obtained; therefore the pilot did not possess valid medical certification for the flight.

The pilot’s cardiovascular disease was associated with an increased risk of sudden impairment or incapacitating cardiovascular event such as ventricular arrhythmia, heart attack, or stroke. No forensic evidence indicated that such an event occurred. However, such events do not leave reliable autopsy evidence if the event occurs just before death, and no data were available from the pilot’s implanted pacemaker/defibrillator. Thus, the investigation was unable to determine if sudden incapacitation or impairment was a factor in this accident.

Probable cause

The pilot’s spatial disorientation and loss of airplane control after entering instrument meteorological conditions shortly after takeoff.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR22FA210
Event ID
20220610105237
Case number
WPR22FA210
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, coordinates, cause areas. 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: 61990bf1b6a56d8570a7d19bde2e01a79ec083d1f2720c58405c43567ec3fda8; retrieved 2026-09-15T07:46:02.391Z.