# Accident 20141016020069A: Piper PA32-301FT, Winona, MS, October 16, 2014

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: October 16, 2014, 12:26 local time
- Place: Winona, MS
- Airport: Winona-Montgomery County
- Damage: Substantial damage
- Phase of flight: Takeoff: Departure Roll
- Operating rules: General operating rules (Part 91)
- Location: 33.4650° N, 89.7303° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=33.4650&lon=-89.7303&mi=10
- Aircraft: N106C, a cancelled registration (https://openairdocs.org/deregistered/N106C-2023-01-14) (OpenAirDocs)
- Registry model: Piper PA32-301FT (registry code 7103300, https://openairdocs.org/model/piper-pa32-301ft) (OpenAirDocs)
- Registry engine: Lycoming IO-540-K1G5D (registry code 41598, https://openairdocs.org/engine/lycoming-io-540-k1g5d) (OpenAirDocs)
- Reported make and model: PIPER PA32-301FT
- Reported engine: LYCOMING IO-540-K1G5D
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Private pilot
- Pilot flight hours: 190 total, 120 in this make and model, 40 in the last 90 days
- NTSB investigation: [NTSB ERA15LA019](https://openairdocs.org/ntsb/ERA15LA019) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20141016020069A

## Narrative

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

DURING TAKEOFF PILOT ABORTED AFTER MFD DISPLAYED RED X. PILOT RUN OFF LEFT SIDE OF RUNWAY STRIKING FENCE.

## 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 ERA15LA019](https://openairdocs.org/ntsb/ERA15LA019), Oct 16, 2014: Piper PA32 301FT (N106C), Winona, MS, substantial damage. Probable cause: A loss of directional control during takeoff for reasons that could not be determined because postaccident examination of the airplane revealed no anomalies.

## Other reports on N106C (1)

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

- [Accident 20100706039659A](https://openairdocs.org/incident/20100706039659A), Jul 6, 2010: Piper PA32-301FT (N106C), Albuquerque, NM, Substantial damage. On July 6, 2010 at 0800 MDT, N106C, a Piper PA-32-301FT, sustained substantial damage when it departed the left side of runway 8 at Albuquerque international…

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.