LAX96FA275 · Piper PA-24-260
Piper PA-24-260 · Accident: in flight encounter with weather en route
From Reid-Hillview Airport of Santa Clara County (RHV) to Sisters Eagle Air Airport (6K5)
Event
- NTSB case
- LAX96FA275
- 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
- 0
- 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
Piper PA-24-260
- Aircraft type
- Piper PA-24
- 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
- N9324P
- Operator
- Leroy M. Leale · private individual
- Onboard fatalities
- Unknown
- Route
- From Reid-Hillview Airport of Santa Clara County (RHV), REID HILLVIEW, CATo Sisters Eagle Air Airport (6K5), SISTER, OR
- 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
- 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 › Flight into known adverse weather, continued
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot departed San Jose, California, on a cross-country flight to Sisters, Oregon. He obtained a standard preflight weather briefing. Visual flight was not recommended. Cumulus buildups were reported to the pilot. The pilot indicated that he may be overflying the cloud tops. He did not file a flight plan. The pilot's wife was driving to the same location and they talked by cell phone while en route. When the pilot failed to arrive at the destination a search was started. According to radar data, the aircraft was at 15,400 feet when it started a rapid descent. Radar was lost at 11,800 feet. Witnesses reported seeing the aircraft descending near vertically out of broken clouds with the engine at full power. When the aircraft was found, the right outboard wing panel from about station 110 outboard was missing. About a month later the outer wing panel was found. Analysis of the failed structure indicated a positive overload of the wing and the horizontal stabilators.
Probable cause
the pilot's continued flight into known adverse weather conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX96FA275
- Event ID
- 20001208X06269
- Case number
- LAX96FA275
- 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. 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: 915dad47a6703236ef4378f2e7b58196b34d81ea9d80aee49b0ee2b3844cf37d; retrieved 2026-09-20T23:16:27.331Z.