# Accident 19920201028699A: Piper PA22150, Columbus, MS, February 1, 1992

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: February 1, 1992, 14:29 local time
- Place: Columbus, MS
- Airport: Columbus-Lowndes County Airport
- Damage: Substantial damage
- Phase of flight: Fcd/Prec Ldg From Cruise
- Operating rules: General operating rules (Part 91)
- Location: 33.5009° N, 88.4008° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=33.5009&lon=-88.4008&mi=10
- Aircraft: N3500Z, registered now (https://openairdocs.org/aircraft/N3500Z) (OpenAirDocs)
- Registry model: Piper PA-22-150 (registry code 7102210, https://openairdocs.org/model/piper-pa-22-150) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: PIPER PA22150
- Reported engine: LYC TIO540*
- Fatal injuries: 0
- Pilot flight hours: 13,000 total
- NTSB investigation: [NTSB MIA92LA076](https://openairdocs.org/ntsb/MIA92LA076) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19920201028699A

## Narrative

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

ENGINE QUIT ON DESCENT TO LAND. HIT TREES LANDING. CRANKSHAFT FAILED DUE HIGH CYCLE FATIGUE. 174HRS SINCE NEW.

## 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 MIA92LA076](https://openairdocs.org/ntsb/MIA92LA076), Feb 1, 1992: Aero Mercantil Gavilan 358 EL-1 (N3500Z), Columbus, MS, substantial damage. Probable cause: FATIGUE FAILURE OF THE CRANKSHAFT DUE TO IMPROPER ENGINE ASSEMBLY BY THE MANUFACTURER.

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.