# Accident 19960519010879A: Piper PA22160, Maryville, MO, May 19, 1996

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: May 19, 1996, 10:45 local time
- Place: Maryville, MO
- Airport: Rankin Airport
- Damage: Substantial damage
- Phase of flight: Ground Taxi, Other Airplane
- Operating rules: General operating rules (Part 91)
- Location: 40.3404° N, 94.8700° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=40.3404&lon=-94.8700&mi=10
- Aircraft: N8943D, a cancelled registration (https://openairdocs.org/deregistered/N8943D-2013-05-17) (OpenAirDocs)
- Registry model: Piper PA-22-160 (registry code 7102214, https://openairdocs.org/model/piper-pa-22-160) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: PIPER PA22160
- Reported engine: LYC O320B2A
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 1,368 total, 1,147 in this make and model, 24 in the last 90 days
- NTSB investigation: [NTSB CHI96LA161](https://openairdocs.org/ntsb/CHI96LA161) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19960519010879A

## Narrative

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

LOST DIRECTIONAL CONTROL ON LANDING DUE TO STRONG CROSSWIND, CAME TO REST INVERTED IN A FIELD NEAR RUNWAY.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      (.4)AFTER LANDING WITH A 40 DEGREE CROSSWIND, THE PILOT ALLOWED THE AIRPLANE TO DRIFT LEFT OFF THE RUNWAY, SO HE COULD TURN BACK INTO THE WIND AND BACK-TAXI ON THE RUNWAY. HE THEN SAW A RUNWAY LIGHT AHEAD AND MANEUVERED THE AIRPLANE FARTHER LEFT TO AVOID THE LIGHT. SHORTLY AFTER THAT, THE AIRPLANE ENTERED A DITCH. THE AIRPLANE'S NOSE WHEEL THEN SANK IN SOFT TERRAIN, AND THE AIRPLANE NOSED 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 CHI96LA161](https://openairdocs.org/ntsb/CHI96LA161), May 19, 1996: Piper PA-22 (N8943D), Maryville, MO, substantial damage. Probable cause: the pilot's selection of an unsuitable area to taxi off the narrow runway in order to turn around. The proximity of the ditch was a related factor.

## Other reports on N8943D (1)

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

- [Accident 20000407043199A](https://openairdocs.org/incident/20000407043199A), Apr 7, 2000: Piper PA22160 (N8943D), St Joseph, MO, Substantial damage. (-23) PIC stated that he landed on rwy 31 without difficulty. He cleared the runway, crossed another runway, and began taxiing eastbound toward his hangar.…

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.