WPR11FA230 · Cameron LANCAIR LEGACY
Tumbleweed Cameron LANCAIR LEGACY · Accident: VFR encounter with IMC en route
From Minden, NV to Tracy, CA
Event
- NTSB case
- WPR11FA230
- 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
Cameron LANCAIR LEGACY
- Aircraft type
- Cameron LANCAIR LEGACY
- 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
- N121J
- Operator
- Tumbleweed
- Onboard fatalities
- Unknown
- Route
- From Minden, NVTo Tracy, 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
- VFR encounter with IMC
- 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
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
During the personal flight, the airplane impacted mountainous terrain. The witness marks and debris field were consistent with an in-flight collision with trees and terrain. Weather information available for the time of the accident showed suspended precipitation and/or instrument meteorological conditions (IMC) near the accident site and the potential for icing in the accident area. The airplane's altitude could not be identified on radar; therefore, it could not be determined whether the airplane was flying in frozen, liquid, or a mixed-phase of precipitation at the time of the accident. Postaccident examination of the airframe and engine revealed no mechanical malfunctions or failures that would have precluded normal operation. The airplane likely impacted terrain due to the pilot's decision to continue flight into IMC at an insufficient altitude to clear terrain.
Probable cause
The pilot’s continued flight into instrument meteorological conditions at an insufficient altitude to clear terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR11FA230
- Event ID
- 20110520X11457
- Case number
- WPR11FA230
- 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. 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: 661ecbdbd12bdc4b44b85ec74c6c2465ed3f16a4afcf21fa49e4953b33c75584; retrieved 2026-09-13T21:25:14.997Z.