# Accident 19950723026439A: Cessna 172P, Springfield, MO, July 23, 1995

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: July 23, 1995, 19:10 local time
- Place: Springfield, MO
- Airport: Springfield Regional
- Damage: Substantial damage
- Phase of flight: Final Approach
- Operating rules: General operating rules (Part 91)
- Location: 37.2808° N, 93.2900° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=37.2808&lon=-93.2900&mi=10
- Aircraft: N55212, a cancelled registration (https://openairdocs.org/deregistered/N55212-2012-07-31) (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
- Reported engine: LYC O320D2J
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 179 total, 121 in this make and model, 90 in the last 90 days
- NTSB investigation: [NTSB CHI95LA235](https://openairdocs.org/ntsb/CHI95LA235) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19950723026439A

## Narrative

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

LOST CONTROL IN WINDSHIFT TRYING TO LAND IN APPROACHING THUNDERSTORM. DOWNDRAFTS. IMPACTED SHORT. FAILED GO AROUND.

## 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 CHI95LA235](https://openairdocs.org/ntsb/CHI95LA235), Jul 24, 1995: Cessna 172 (N55212), Springfield, MO, substantial damage. Probable cause: improper in-flight planning/decision by the pilot, and his continued flight into adverse weather conditions, which resulted in an uncontrolled altitude deviation and collision with terrain. Factors…

## Other reports on N55212 (3)

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

- [Accident 20110130000729A](https://openairdocs.org/incident/20110130000729A), Jan 30, 2011: Cessna 172P (N55212), South Point, OH, Substantial damage. Pilot stated, after departure from runway 8, the aircraft engine suddenly began to run rough during the climb. Pilot stated he executed a steep left turn with…
- [Incident 19880527024839I](https://openairdocs.org/incident/19880527024839I), May 27, 1988: Cessna 172P (N55212), Lubbock, TX. Pilot disoriented. Using pilotage navigation,misidentified airport and misinterpreted fuel state. Landed afb safely.
- [Incident 19821001058269I](https://openairdocs.org/incident/19821001058269I), Oct 1, 1982: Cessna 172P (N55212), Scottsdale, AZ. Lost control temporarily on landing roll, recovered, went around and landed safely.

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.