# Accident 19930724039349A: Cessna 210A, Salinas, CA, July 24, 1993

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: July 24, 1993, 20:28 local time
- Place: Salinas, CA
- Airport: Salinas Municipal Airport
- Damage: Substantial damage
- Phase of flight: Forced Landing
- Operating rules: General operating rules (Part 91)
- Location: 36.6408° N, 121.6191° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=36.6408&lon=-121.6191&mi=10
- Aircraft: N9520X, a cancelled registration (https://openairdocs.org/deregistered/N9520X-2007-04-02) (OpenAirDocs)
- Registry model: Cessna 210A (registry code 2073408, https://openairdocs.org/model/cessna-210a) (OpenAirDocs)
- Registry engine: Continental I0-470 series (registry code 17027, https://openairdocs.org/engine/continental-i0-470-series) (OpenAirDocs)
- Reported make and model: CESSNA 210A
- Reported engine: CONT IO470E
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 1,342 total, 60 in this make and model, 36 in the last 90 days
- NTSB investigation: [NTSB LAX93LA363](https://openairdocs.org/ntsb/LAX93LA363) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19930724039349A

## Narrative

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

ENGINE QUIT ON APPROACH TO AIRPORT. LANDED OFF AIRPORT. NO ANOMALIES. WAS LOW ON FUEL. MAY HAVE CAUSE UNPORTING.

## 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 LAX93LA363](https://openairdocs.org/ntsb/LAX93LA363), Jul 25, 1993: Cessna 210A (N9520X), Salinas, CA, substantial damage. Probable cause: An undetermined loss of engine power during the final approach phase of landing resulting in a collision with terrain during the forced landing.

## Other reports on N9520X (3)

Matched to the same aircraft by N-number and date.

- [Accident 19890619016769A](https://openairdocs.org/incident/19890619016769A), Jun 19, 1989: Cessna 210A (N9520X), Ocean City, MD, Substantial damage. Landed and ran off end of runway into cluster of antennae. Minor damage to aircraft.
- [Incident 19850616072359I](https://openairdocs.org/incident/19850616072359I), Jun 16, 1985: Cessna 210A (N9520X), Kalamazoo, MI. Encountered IFR weather en route. Filed and accepted an IFR clearance. Not IFR rated.
- [Incident 19840327022029I](https://openairdocs.org/incident/19840327022029I), Mar 27, 1984: Cessna 210A (N9520X), Sussex, NJ, Minor damage. Unable to obtain 3 green lights for landing. The nose gear collapsed on touchdown. Downlock pin was broken.

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.