ANC06LA030 · Mooney M-10
Mooney M-10 · Accident: in flight encounter with weather en route
From Watsonville Municipal Airport (KWVI) to General William J Fox Airfield (KWJF)
Event
- NTSB case
- ANC06LA030
- 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 M-10
- Aircraft type
- Mooney M-10
- 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
- N9533V
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Watsonville Municipal Airport (KWVI), Watsonville, CATo General William J Fox Airfield (KWJF), Lancaster, 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
- 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
- In flight encounter with weather
- 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
- 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
- Pilot in command › Airspeed(vs), not maintained
- Pilot in command › Flight into known adverse weather, continued
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane was being operated by the solo private pilot as a visual flight rules (VFR) personal cross-country flight under Title 14, CFR Part 91, when the accident occurred. Witnesses said the pilot arrived at the airport on Friday evening to pickup the accident airplane, which he had just purchased. They said the pilot refused a checkout in the new airplane, and planned to depart after dark, in deteriorating weather conditions, for his home, stating he needed to be home before Monday. Local pilots convinced him to delay his departure until the following morning. The pilot declined a second offer of a checkout in the airplane the following morning. A pilot-rated witness said he spoke with the pilot the morning he departed, while the pilot preflighted and fueled the accident airplane. The witness said he checked local weather via a computer for the pilot. He said weather to the east was not conducive to VFR flight, and he tried to convince the pilot to fly south to avoid the weather and rising terrain to the east. According to the witness, the last thing the pilot asked before leaving was the identifier for an airport to the southeast, which he input into a handheld global positioning system (GPS) unit. The witness said a direct route to that airport would not have taken the pilot far enough south to avoid the weather. The witness said when the airplane departed about 0900, the ceiling was about 1,600 feet above ground level, and the visibility was 5 miles in rain. The airplane wreckage was located east-southeast of the departure airport along an approximate direct route to the airport the pilot entered into the GPS. An FAA aviation safety inspector who visited the accident site, said the airplane impacted in hilly terrain, in a nose low, near vertical attitude. He said the airplane did not pass through brush and low trees located directly behind the wreckage. Photographs taken at the accident site, showed uniform, sharp aft and upward crushing of the entire leading edge of both wings. The empennage was crushed and folded downward, and twisted to the right, consistent with the airplane spinning at impact. The foreman of the ranch where the airplane crashed, reported that on the morning of the accident there was low cloud cover, and three-quarters of a mile visibility in rain.
Probable cause
The pilot's continued flight into known adverse weather, and his failure to maintain sufficient airspeed, which resulted in a loss of control and an inadvertent stall/spin during cruise flight. Factors associated with the accident are a low ceiling with reduced visibility, and an inadvertent stall/spin.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC06LA030
- Event ID
- 20060403X00382
- Case number
- ANC06LA030
- 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: 9e71ebe895847e038a6de0eb9cc53d225b52929013e2f7c67f61fa5100561d16; retrieved 2026-09-20T17:27:33.770Z.