LAX86LA241 · Boeing A75N1
Boeing A75N1 · Accident: in flight collision with object on approach
From OQ3 · Sonoma, CA to an unrecorded destination
Event
- NTSB case
- LAX86LA241
- 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
Boeing A75N1
- Aircraft type
- Boeing A75
- 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
- N62763
- Operator
- Gustaf Friesen
- Onboard fatalities
- Unknown
- Route
- From OQ3 · Sonoma, 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
- Approach · VFR pattern final
- 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
- Utility pole
- 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 › Altitude, inadequate
- Pilot in command › Clearance, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE ACFT COLLIDED WITH A POLE AND CRASHED IN A FLOODED FIELD WHILE ON FINAL APPROACH. THE PILOT INDICATED THAT HE FLEW A 20 MINUTE LOCAL VFR FLIGHT PRIOR TO THE ACCIDENT. HE STATED HE HAD SUFFERED HEAD INJURIES AND WAS UNABLE TO RECALL ANY DETAILS OF THE ACCIDENT AFTER THE ACFT STRUCK THE POLE. EXAMINATION OF THE ENGINE REVEALED MINOR IMPACT DAMAGE AND MUD AND RUST DEPOSITS. THE RIGHT MAGNETO WAS RUSTED SHUT. EXAMINATION OF THE PROPELLER REVEALED ONE BLADE BENT FORWARD AND THE OTHER DAMAGED DUE TO A STRIKE. THE ENGINE WAS RUN ON A TEST STAND WITHOUT ANY PROBLEMS AFTER THE ENGINE OIL WAS CHANGED AND THE RIGHT MAGNETO REPLACED.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record LAX86LA241
- Event ID
- 20001213X33906
- Case number
- LAX86LA241
- 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: 53e4a1d874386429706f9f03792193681c284342f02191c7ac72c92146264346; retrieved 2026-09-21T16:57:34.784Z.