LAX06FA054 · Piper PA-32RT-300
Piper PA-32RT-300 · Accident: in flight encounter with weather en route
From Reid-Hillview Airport of Santa Clara County (RHV) to Visalia Municipal Airport (VIS)
Event
- NTSB case
- LAX06FA054
- 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
- 2 · 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
Piper PA-32RT-300
- Aircraft type
- Piper PA-32
- 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
- N3039B
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Reid-Hillview Airport of Santa Clara County (RHV), San Jose, CATo Visalia Municipal Airport (VIS), Visalia, 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 · descent
- 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
- Visual flight rules (VFR) flight into instrument meteorological conditions (IMC); Tree(s)
- 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
- Pilot in command › Clearance, not maintained
- Pilot in command › VFR flight into imc, 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 impacted trees and terrain while descending in instrument meteorological conditions. The airplane was reported overdue about 5 hours after its departure. No flight plan had been filed. Due to thick ground fog in the area, the search was restricted until daylight the following day when the wreckage was located. Family members reported that the pilot and his wife contacted them via telephone about 1000 and said they were running a little late. Records at the departure airport show the airplane departed at 1026. The pilot and his wife were scheduled to be at the destination airport around 1100 for an appointment. Review of recorded radar data noted a secondary 1200 (VFR) beacon code at a mode C reported altitude of 1,600 feet mean sea level (msl) 12 nautical miles(nm) northwest of the destination airport. The target continued climbing while proceeding on a southeasterly course, which appeared to track towards the airport. About 3.8 nm northwest of the airport at a mode C reported altitude of 2,100 feet msl, the target began a gradual descending right turn. The target tracked back towards the northwest until radar contact was lost at 11:31:10, at a mode C reported altitude of 300 feet. The last recorded radar target was 1.5 nm south of the accident site. The distance from the initial impact point near the top of a 100-foot-tall tree to the main wreckage was approximately 370 feet. Aviation routine weather reports for the destination airport and the airports within 20 miles showed widespread low stratus and fog conditions with visibilities 1/4-mile or less under a 100-foot overcast, with the tops of the cloud layer reported at 800 feet.
Probable cause
The pilot's in-flight decision to continue VFR flight into instrument meteorological conditions during descent, which resulted in an in-flight collision with trees and terrain. Fog, low ceiling, and obscuration were factors.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX06FA054
- Event ID
- 20051223X02006
- Case number
- LAX06FA054
- 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: 47ddf599404a3f375ca28da98073e02ee0655dfc054e92f1d9de663f8a527a0f; retrieved 2026-09-20T17:43:20.904Z.