# Accident 19961213039349A: Piper PA32R300, Garnett, KS, December 13, 1996

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: December 13, 1996, 05:30 local time
- Place: Garnett, KS
- Airport: Garnett Municipal Airport
- Damage: Substantial damage
- Phase of flight: Fcd/Prec Ldg From Cruise
- Operating rules: Air taxi and commuter (Part 135)
- Operator: DD5A
- Location: 38.2791° N, 95.2309° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=38.2791&lon=-95.2309&mi=10
- Aircraft: N31SW, a cancelled registration (https://openairdocs.org/deregistered/N31SW-1999-07-29) (OpenAirDocs)
- Registry model: Piper PA-32R-300 (registry code 7103213, https://openairdocs.org/model/piper-pa-32r-300) (OpenAirDocs)
- Reported make and model: PIPER PA32R300
- Reported engine: LYC O540G1A5
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 1,850 total, 35 in this make and model, 66 in the last 90 days
- NTSB investigation: [NTSB CHI97LA042](https://openairdocs.org/ntsb/CHI97LA042) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19961213039349A

## Narrative

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

MISSED THREE APPROACHES, DUE DENSE FOG. DIVERTED, EXHAUSTED FUEL SHORT RUNWAY AFTER CIRCLING THE AIRPORT.

## 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 CHI97LA042](https://openairdocs.org/ntsb/CHI97LA042), Dec 13, 1996: Piper PA-32R-300 (N31SW), Garnett, KS, substantial damage. Probable cause: the pilot's improper in-flight planning/decision, including a delay in proceeding to an alternate airport after encountering fog during a night approach, which resulted in loss of engine power due to…

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.