WPR11FA316 · Mooney M20F
Mooney M20F · Accident: aerodynamic stall/spin while maneuvering
From Watsonville Municipal Airport (WVI) to Groveland, CA
Event
- NTSB case
- WPR11FA316
- 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
- 4 · 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
- N7759M
- Operator
- David Edward Houghton
- Onboard fatalities
- Unknown
- Route
- From Watsonville Municipal Airport (WVI), Watsonville, CATo Groveland, 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
- Maneuvering
- 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
- Aerodynamic stall/spin
- 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
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot departed from his home airport situated about 3 miles east-northeast of the ocean with a low-lying stratus cloud layer. The takeoff was conducted while it was still daylight. Eyewitness and photographic evidence indicated that the stratus layer was nearby, to the southwest, south and southeast of the airport at the time of the takeoff. The airport was non-towered, and was equipped with two similar-length runways, designated as 2/20 and 8/26. Airplane performance, and terrain and obstacle clearance considerations did not preclude a takeoff from any of the four possible runway options. However, the takeoff was conducted from runway 20, directly towards the cloud layer.
Eyewitnesses and recovered GPS data indicated that the airplane began a sharp left turn prior to reaching the end of the runway, at an altitude of about 400 feet above ground level (agl). That turn was consistent with an effort to avoid the cloud layer, but contrary to published airport noise abatement guidance that prohibited departure turns prior to the airport boundary, or at altitudes below 900 feet agl. The airplane did not enter the cloud, but during the turn, the airplane stalled, entered a spin, and descended rapidly to the ground. The airplane struck a parking lot and building less than 700 feet from the departure runway. Post-accident examination of the airplane and engine did not reveal any anomalies or failures that would have precluded normal operation.
At least two headsets, one of which was a noise cancelling unit, were located in the wreckage. According to the airplane co-owner, the vane-activated, electrically-powered stall warning horn was inaudible to a pilot wearing a headset, and the owners' attempts to rectify that situation were unsuccessful. Post-accident testing of the vane switch and warning horn indicated that they were functional, but the horn volume was not measured or compared to any known standard.
During airplane manufacture, the final position of the stall warning vane and switch assembly on the wing is determined during the production flight test of each individual airplane, in order to ensure system activation at the proper angle of attack. No records of the as-delivered vane position were available, and the as-delivered position of the vane could not be discerned by examination of the wreckage. Examination of the vane assembly revealed that it had been modified, and was not installed in accordance with the manufacturer's design drawings. In addition, no information regarding the accuracy of the modified stall warning system was located. The investigation was unable to determine whether the system would have provided sufficient, or even any, notification of a stall, presuming the horn was audible to the pilot, which in this case it was not.
Despite three other runway alternatives, the pilot knowingly and intentionally decided to depart from the runway most closely aligned towards the stratus layer, with the apparent plan to turn to avoid it once airborne. While his runway choice may have been influenced by habit pattern, existing traffic, or a previous taxi event at that airport, the investigation was unable to determine why the pilot chose that runway, instead of using any of the other three alternatives which would have taken him away from the cloud layer. He then inadvertently stalled and spun the airplane during the avoidance turn, at an altitude which did not allow recovery.
Probable cause
The pilot's decision to take off toward a nearby low cloud layer and the subsequent turn, stall, and spin during the pilot’s attempt to avoid the cloud layer. Contributing to the accident was the pilot's failure to avoid the stall. His ability to avoid the stall was hindered by an inaudible stall warning system of questionable accuracy.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR11FA316
- Event ID
- 20110707X35545
- Case number
- WPR11FA316
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2011-07-08.
- API snapshot SHA-256: 4e299a53b611faff0902e4dc5cac3eeb250896b0647ade207fc09c83384be481; retrieved 2026-09-13T21:32:26.699Z.