# Accident 19850912047319A: Cessna 152, Olathe, KS, September 12, 1985

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: September 12, 1985, 18:31 local time
- Place: Olathe, KS
- Airport: Johnson Co Executive
- Damage: Substantial damage
- Phase of flight: Roll-Out (Fixed Wing)
- Operating rules: General operating rules (Part 91)
- Location: 38.8799° N, 94.8103° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=38.8799&lon=-94.8103&mi=10
- Aircraft: N5269Q, a cancelled registration (https://openairdocs.org/deregistered/N5269Q-2009-03-25) (OpenAirDocs)
- Registry model: Cessna 152 (registry code 2071835, https://openairdocs.org/model/cessna-152) (OpenAirDocs)
- Reported make and model: CESSNA 152
- Reported engine: LYC O235L2C
- Fatal injuries: 0
- Pilot flight hours: 56 total, 33 in this make and model, 31 in the last 90 days
- NTSB investigation: [NTSB MKC85LA214](https://openairdocs.org/ntsb/MKC85LA214) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19850912047319A

## Narrative

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

LOST DIRECTIONAL CONTROL DURING CROSSWIND LANDING. DEPARTED SIDE OF RUNWAY, NOSE GEAR COLLAPSED. FLIPPED OVER.

## 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 MKC85LA214](https://openairdocs.org/ntsb/MKC85LA214), Sep 12, 1985: Cessna 152 (N5269Q), Olathe, KS, substantial damage

## Other reports on N5269Q (1)

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

- [Accident 19870709032679A](https://openairdocs.org/incident/19870709032679A), Jul 9, 1987: Cessna 152 (N5269Q), Parker, CO, Substantial damage. Aircraft apparently entered micro burst downdraft. Pilot unable to stop descent. Crashed on landing in a sod field.

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.
