# Incident 19880227010849I: Cessna 172M, Columbus, NE, February 27, 1988

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: February 27, 1988, 14:40 local time
- Place: Columbus, NE
- Airport: Columbus Municipal
- Damage: Minor damage
- Phase of flight: Roll-Out (Fixed Wing)
- Operating rules: General operating rules (Part 91)
- Location: 41.4487° N, 97.3409° W: Placed by OpenAirDocs at COLUMBUS MUNI (OLU), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=41.4487&lon=-97.3409&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: 1
- Fatal injuries: 0
- Pilot flight hours: 30 total, 30 in this make and model, 30 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19880227010849I

## Narrative

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

LOST DIRECTIONAL CONTROL ON ROLLOUT. VEERED OFF RUNWAY INTO SOFT GROUND.

## 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.
- [Accident 19891019043909A](https://openairdocs.org/incident/19891019043909A), Oct 19, 1989: Cessna 172M (N5336R), Omaha, NE, Substantial damage. Throttle cable failed on approach to airport. Engine went to idle. Landing short in soy bean field, struck a fence.

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.