LAX91LA319 · Piper J3C-65
Piper J3C-65 · Accident: in flight collision with object while maneuvering
From Westley Airport (CA67) to an unrecorded destination
Event
- NTSB case
- LAX91LA319
- 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
- 0 · 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 J3C-65
- Aircraft type
- Piper J3
- 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
- N23142
- Operator
- Michael Mahaffey
- Onboard fatalities
- Unknown
- Route
- From Westley Airport (CA67), Westley, CATo not recorded
- 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
- Maneuvering
- 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 collision with object
- 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
- Wire, transmission
- 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 › Visual lookout, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT AND HIS PASSENGER WERE FLYING IN THE VICINITY OF A RIVER AND A POND TRYING TO LOCATE STRAY CATTLE. THEY WERE FLYING AT ABOUT 400 FEET ABOVE THE GROUND WHEN THE PASSENGER THOUGHT HE SPOTTED SOMETHING AT THE NORTH END OF A POND. NOT BEING ABLE TO IDENTIFY THE OBJECT, THEY BEGAN A DESCENT TO TRY TO IDENTIFY THE OBJECT. DURING DESCENT THE AIRCRAFT COLLIDED WITH ELECTRICAL TRANSMISSION WIRES. THE AIRCRAFT ENTERED AN UNCONTROLLED DESCENT AND IMPACTED THE WATER IN THE POND. THEY SAID THAT THEY DID NOT SEE THE WIRES OR SUPPORTING POLES. AN FAA SAFETY INSPECTOR REPORTED THAT 3 WIRES HAD BEEN BROKEN. THE POLES ARE ON LAND AND THEY ARE APPROXIMATELY 1,140 FEET APART.
Probable cause
THE PILOT-IN-COMMAND'S IMPROPER VISUAL LOOKOUT IN A DESCENT AT LOW ALTITUDE, RESULTING IN AN IN FLIGHT COLLISION WITH WIRES AND SUBSEQUENT IN FLIGHT COLLISION WITH TERRAIN.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX91LA319
- Event ID
- 20001212X17608
- Case number
- LAX91LA319
- 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 1991-07-19.
- API snapshot SHA-256: 25fd130abf51265fe89da6c99f5d1c46fa62f17d37cf0d0d37542e1454fe639c; retrieved 2026-09-21T15:23:49.764Z.