# Accident 19961101034669A: Yaklev YAK52, Fullerton, CA, November 1, 1996

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: November 1, 1996, 12:00 local time
- Place: Fullerton, CA
- Airport: Fullerton Municipal
- Damage: Substantial damage
- Phase of flight: Forced/Precautionary Landing
- Operating rules: General operating rules (Part 91)
- Location: 33.8720° N, 117.9798° W: Placed by OpenAirDocs at FULLERTON MUNI (FUL), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=33.8720&lon=-117.9798&mi=10
- Aircraft: N207YK, registered now (https://openairdocs.org/aircraft/N207YK) (OpenAirDocs)
- Registry model: S C Aerostar S A YAK-52 (registry code 1140000, https://openairdocs.org/model/s-c-aerostar-s-a-yak-52) (OpenAirDocs)
- Registry engine: Vedeneyev M14P (registry code 63601, https://openairdocs.org/engine/vedeneyev-m14p) (OpenAirDocs)
- Reported make and model: YAKLEV YAK52
- Fatal injuries: 0
- Pilot flight hours: 3,550 total, 40 in this make and model, 25 in the last 90 days
- NTSB investigation: [NTSB LAX97LA035](https://openairdocs.org/ntsb/LAX97LA035) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19961101034669A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

LOST POWER ON LIFTOFF. STRUCK BUILDING, AIRPORT FENCE LANDING. DEFECTIVE CARBURETOR INSTALLATION BY ASSEMBLY MECHS.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB LAX97LA035](https://openairdocs.org/ntsb/LAX97LA035), Nov 1, 1996: Aerostar YAK 52 (N207YK), Fullerton, CA, substantial damage. Probable cause: loss of engine power due to an undetermined internal carburetor malfunction. A factor relating to the accident was: the directions that were use for reassembly of the aircraft were written only in…

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.