# Incident 19900510024619I: Cessna 172P, Festus, MO, May 10, 1990

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: May 10, 1990, 16:15 local time
- Place: Festus, MO
- Airport: Festus Memorial Aprt
- Damage: Minor damage
- Phase of flight: Roll-Out (Fixed Wing)
- Operating rules: General operating rules (Part 91)
- Location: 38.2192° N, 90.4098° W: Placed by OpenAirDocs: center of Festus, MO, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=38.2192&lon=-90.4098&mi=10
- Aircraft: N6174K, a cancelled registration (https://openairdocs.org/deregistered/N6174K-2007-10-01) (OpenAirDocs)
- Registry model: Cessna 172P (registry code 2072436, https://openairdocs.org/model/cessna-172p) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172P
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 131 total, 15 in this make and model, 15 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19900510024619I

## Narrative

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

LOST DIRECTIONAL CONTROL ON LANDING ROLLOUT. VEERED OFF RUNWAY AND HIT A FENCE. HAD GUSTY WINDS.

## Other reports on N6174K (2)

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

- [Accident 19980419013289A](https://openairdocs.org/incident/19980419013289A), Apr 19, 1998: Cessna 172P (N6174K), Longmont, CO, Substantial damage. Drifted in crosswind landing. Made contact with groun. CFI targeted for dual xwind landings. P factor. Go arounds. (.4)while on final approach to land at Vance…
- [Incident 19850628040819I](https://openairdocs.org/incident/19850628040819I), Jun 28, 1985: Cessna 172P (N6174K), Washington Cour, OH, Minor damage. Engine failed and landing made in corn field. Found exhaust valve had stuck and push rod and housing were 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.