WPR13FA312 · Mooney M20F
Mooney M20F · Accident: controlled flight into terrain/object (CFIT) en route
From Santa Ynez Airport (IZA) to Mammoth Lakes, CA
Event
- NTSB case
- WPR13FA312
- 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
- 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
- N9524M
- Operator
- Wilson Nicol S
- Onboard fatalities
- Unknown
- Route
- From Santa Ynez Airport (IZA), Santa Ynez, CATo Mammoth Lakes, CA
- 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
- 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
- Controlled flight into terrain/object (CFIT)
- 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
- Personnel issues › Psychological
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 departed on a visual flight rules cross-county flight. Review of radar data showed the airplane departing and then proceeding on a northeasterly heading toward the intended destination. For the first 35 minutes of flight, the airplane remained below 10,000 ft mean sea level (msl). The airplane then ascended to a maximum altitude of 17,000 ft msl, initiated a descent, and turned north. As the airplane continued to descend through 14,300 ft msl, it turned west. (The airplane operated above 10,000 ft msl for 1 hour 8 minutes.) The data then showed the airplane perform a series of 360-degree descending turns. During the series of turns, the airplane descended to 6,200 ft msl and then ascended while turning east. The last recorded radar target was located about 12 miles west of the accident site at an altitude of 9,800 ft msl. Examination of the accident site revealed that the airplane impacted mountainous terrain just below the top of a ridgeline at an altitude of about 10,679 ft msl.
Airmen's meteorological information for instrument meteorological conditions (IMC), mountain obscuration, and moderate turbulence conditions below 18,000 ft were in effect throughout the area about the time of the accident. Satellite imagery depicted a layer of low clouds over the area with a thick, overcast layer of clouds over the accident site. Weather radar imagery depicted scattered echoes within the immediate vicinity of the accident site, which indicates that precipitation was falling over the area. However, due to the possibility of beam blockage from the higher terrain, the full extent and intensity of the precipitation over the accident site could not be determined. It could not be determined if the pilot obtained a weather briefing before the flight.
A postaccident examination of the airframe and engine revealed no evidence of preimpact mechanical malfunctions or failures that would have precluded normal operation. Wreckage impact signatures and radar data were consistent with continued flight toward the intended destination before the accident. It is likely that the pilot was attempting to maneuver around the IMC but did not maintain situational awareness and sufficient altitude above the mountainous terrain and entered IMC at the time of the accident.
As noted, the airplane operated 1 hour 8 minutes over 10,000 ft msl; this included 42 minutes over 14,000 ft msl. The Federal Aviation Administration requires pilots to use supplemental oxygen when flying over 14,000 ft msl; however, no evidence was found that supplemental oxygen was available to or used by the pilot. The duration of flight at these altitudes without supplemental oxygen could have resulted in the pilot experiencing hypoxia, which can cause various symptoms, including headache, decreased reaction time, impaired judgment, euphoria, visual impairment, and drowsiness. The pilot's decision-making was likely significantly impaired during this period, and the radar track showed that the airplane turned away from and flew northwest beyond the intended destination. However, the data then showed the airplane descend and remain below 10,000 ft msl for the last 17 minutes of recorded data as the flight track changed direction back toward the original destination. During this period, it is likely that the symptoms of hypoxia would have largely abated.
Probable cause
The pilot’s decision to continue flight into instrument meteorological conditions, which resulted in his failure to maintain situational awareness and sufficient altitude to clear mountainous terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR13FA312
- Event ID
- 20130107X20121
- Case number
- WPR13FA312
- 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. 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: ada5dd9cc4b0f99e71d9e619431e0ff2b452d7bee0e161e464479c00d304ee2a; retrieved 2026-09-14T15:51:42.891Z.