# Accident 19901120051529A: Cessna 210M, Fallbrook, CA, November 20, 1990

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: November 20, 1990, 12:00 local time
- Place: Fallbrook, CA
- Airport: Fallbrook Community Airpark
- Damage: Destroyed
- Phase of flight: Forced/Precautionary Landing
- Operating rules: General operating rules (Part 91)
- Location: 33.3892° N, 117.2105° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=33.3892&lon=-117.2105&mi=10
- Aircraft: N9139M, a cancelled registration (https://openairdocs.org/deregistered/N9139M-2009-09-15) (OpenAirDocs)
- Registry model: Cessna 210M (registry code 2073450, https://openairdocs.org/model/cessna-210m) (OpenAirDocs)
- Registry engine: Continental IO-520 series (registry code 17032, https://openairdocs.org/engine/continental-io-520-series) (OpenAirDocs)
- Reported make and model: CESSNA 210M
- Reported engine: CONT IO520L
- Fatal injuries: 0
- Pilot flight hours: 500 total
- NTSB investigation: [NTSB LAX91LA035](https://openairdocs.org/ntsb/LAX91LA035) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19901120051529A

## Narrative

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

LOST POWER HIT POLE CITY STREET. BROKE CONNECTING ROD. HYDRAULIC CYLINDER LOCK DUE START PROCEDURE. EXCESSIVE FUEL.

## 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 LAX91LA035](https://openairdocs.org/ntsb/LAX91LA035), Nov 20, 1990: Cessna 210M (N9139M), Fallbrook, CA, destroyed. Probable cause: THE FAILURE OF THE NUMBER 5 CYLINDER PISTON CONNECTING ROD DUE TO BENDING AND SUBSEQUENT FATIGUE FRACTURE. CONTRIBUTING TO THE ACCIDENT WAS THE IMPROPER STARTING PROCEDURE ACCOMPLISHED BY AN…

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.