# Incident 20140426006039I: Piper PA-32R-301, Decatur, AL, April 26, 2014

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: April 26, 2014, 12:10 local time
- Place: Decatur, AL
- Airport: Pryor Field Regional Airport
- Damage: Minor damage
- Phase of flight: Landing: Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 34.6541° N, 86.9454° W: Placed by OpenAirDocs at PRYOR FLD RGNL (DCU), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=34.6541&lon=-86.9454&mi=10
- Aircraft: N8186D, registered now (https://openairdocs.org/aircraft/N8186D) (OpenAirDocs)
- Registry model: Piper PA-32R-301 (registry code 7103218, https://openairdocs.org/model/piper-pa-32r-301) (OpenAirDocs)
- Registry engine: Lycoming IO-540 series (registry code 41530, https://openairdocs.org/engine/lycoming-io-540-series) (OpenAirDocs)
- Reported make and model: PIPER PA-32R-301
- Reported engine: LYCOMING IO-540 SER
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Private pilot
- Pilot flight hours: 223 total, 27 in this make and model, 6 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20140426006039I

## Narrative

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

ON APRIL 26, 2014 THE PILOT OF N8186D FLEW TO PULASKI, TN (KGZS) AND COMPLETED A VOR APPROACH. DURING THE FLIGHT TO DECATUR, AL (KDCU) THE AIRCRAFT EXPERIENCED A TOTAL ELECTRICAL FAILURE. ON APPROACH THE PILOT FOLLOWED EMERGENCY GEAR EXTENSION PROCEDURES BY REDUCING SPEED AND EXECUTING TURNS AND MANEUVERS TO HELP THE GEAR DEPLOY. UPON TOUCHDOWN AT (KDCU) THE MAIN GEAR HELD, HOWEVER SLOWING TO APPROPRIATE SPEED THE NOSE GEAR COLLASPED ON TOUCH DOWN.

ON MAY 8, 2014 A LANDING GEAR RETRACT WAS OBSERVED ON N8186D AND OPERATED NORMALLY THROUGHOUT ALL PARAMETERS OF THE RETRACT INCLUDING EMERGENCY EXTENSION.

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.