James Williams Piper 28-151 accident
Piper 28-151 · Accident: in flight encounter with weather en route
From Monterey, CA to Oakland, CA
Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- LAX82FVM09
- 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
- 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
- Charter & commuter
- 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 28-151
- Aircraft type
- Piper 28
- 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
- N32678
- Operator
- James Williams
- Onboard fatalities
- Unknown
- Route
- From Monterey, CATo Oakland, 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 135: Air Taxi & Commuter
- 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
- Visual flight rules (VFR) flight into instrument meteorological conditions (IMC)
- 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 › VFR flight into imc, continued
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT PREPARED TO DEPART ON A SCHEDULED COURIER RUN IN A PIPER PA-32, BUT WAS UNABLE TO START THE ENGINE. AFTER CONSULTING WITH COMPANY PERSONNEL, HE RENTED A PIPER PA-28-151, TRANSFERRED THE CARGO AND DEPARTED MONTEREY, CA ON A FLIGHT TO OAKLAND, CA. AFTER DEPARTING THE MONTEREY TRSA, HE CONTINUED WITH NO FAA FLIGHT PLAN. ABOUT 30 MINUTES AFTER TAKEOFF, THE AIRCRAFT CRASHED IN MOUNTAINOUS TERRAIN LOCATED WITHIN THE TOWN OF LOS GATOS, CA. RESIDENTS IN THE AREA REPORTED THAT THE VISIBILITY WAS FROM 20 TO 50 FT AND THAT THE BRANCHES OF THE TALL TREES COULD NOT BE SEEN WITH THE AID OF A FLASHLIGHT. AN EXAMINATION OF THE WRECKAGE REVEALED NO PREIMPACT ENGINE OR AIRFRAME FAILURES. THE CRASH SITE WAS WITHIN ONE MILE FROM A COURSE LINE BETWEEN THE MONTEREY AND OAKLAND AIRPORTS. THE OPERATOR HAD NOT RECEIVED APPROVAL TO USE THIS MAKE AND MODEL OF AIRCRAFT IN ITS SCHEDULED AIR TAXI OERATION.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record LAX82FVM09
- Event ID
- 20020917X02325
- Case number
- LAX82FVM09
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1982-01-29.
- API snapshot SHA-256: 89daca4b350d7185a9ade76564dfc2be5fd17fe0f6f75c1fcdddd1ac64b4979f; retrieved 2026-09-18T14:33:21.234Z.