# Accident 19891019043909A: Cessna 172M, Omaha, NE, October 19, 1989

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: October 19, 1989, 09:30 local time
- Place: Omaha, NE
- Airport: Eagle Field Airport
- Damage: Substantial damage
- Phase of flight: Forced Landing
- Operating rules: General operating rules (Part 91)
- Location: 41.2586° N, 95.9378° W: Placed by OpenAirDocs: center of Omaha, NE, within about 7 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=41.2586&lon=-95.9378&mi=10
- Aircraft: N5336R, a cancelled registration (https://openairdocs.org/deregistered/N5336R-2023-07-25) (OpenAirDocs)
- Registry model: Cessna 172M (registry code 2072418, https://openairdocs.org/model/cessna-172m) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172M
- Reported engine: LYC O320E2D
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 2,800 total, 700 in this make and model, 226 in the last 90 days
- NTSB investigation: [NTSB MKC90LA010](https://openairdocs.org/ntsb/MKC90LA010) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19891019043909A

## Narrative

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

THROTTLE CABLE FAILED ON APPROACH TO AIRPORT. ENGINE WENT TO IDLE. LANDING SHORT IN SOY BEAN FIELD, STRUCK A FENCE.

## 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 MKC90LA010](https://openairdocs.org/ntsb/MKC90LA010), Oct 19, 1989: Cessna 172 (N5336R), Omaha, NE, substantial damage. Probable cause: FAILURE OF THE THROTTLE CABLE ASSEMBLY WHICH RESULTED IN A FORCED LANDING AND SUBSEQUENT COLLISION WITH A FENCE.

## Other reports on N5336R (2)

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

- [Accident 19990429043019A](https://openairdocs.org/incident/19990429043019A), Apr 29, 1999: Cessna 172M (N5336R), Blair, NE, No damage. (-23) Student pilot on solo training flight rounded out high, fell through, and experienced a hard landing causing substantial damage to firewall.
- [Incident 19880227010849I](https://openairdocs.org/incident/19880227010849I), Feb 27, 1988: Cessna 172M (N5336R), Columbus, NE, Minor damage. Lost directional control on rollout. Veered off runway into soft ground.

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.