# Incident 20060701016699I: Piper PA32RT300T, Winston Salem, NC, July 1, 2006

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: July 1, 2006, 11:00 local time
- Place: Winston Salem, NC
- Airport: Smith Reynolds
- Damage: Minor damage
- Phase of flight: Fcd/Prec Ldg From Cruise
- Operating rules: General operating rules (Part 91)
- Location: 36.1337° N, 80.2220° W: Placed by OpenAirDocs at SMITH REYNOLDS (INT), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=36.1337&lon=-80.2220&mi=10
- Aircraft: N36733, registered now (https://openairdocs.org/aircraft/N36733) (OpenAirDocs)
- Registry model: Piper PA-32RT-300T (registry code 7103216, https://openairdocs.org/model/piper-pa-32rt-300t) (OpenAirDocs)
- Registry engine: Lycoming TI0-540 series (registry code 41533, https://openairdocs.org/engine/lycoming-ti0-540-series) (OpenAirDocs)
- Reported make and model: PIPER PA32RT300T
- Reported engine: LYC TIO540*
- People aboard: 5
- Fatal injuries: 0
- Pilot flight hours: 300 total, 50 in this make and model, 35 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20060701016699I

## Narrative

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

(-23) AT THE CONCLUSION OF 2.5 HOUR CROSS COUNTRY FLIGHT FROM HOPKINSVILLE, KY, PILOT STATED THAT HE EXPERIENCED IN-FLIGHT ELECTRICAL FAILURE DUE TO UNKNOWN ORIGIN SOON AFTER CONTACTING GREENSBORO APPROACH. WHEN HE LOST ALL COMMUNICATIONS ABILITY HE REVERSED COURSE AND PROCEEDED TO INT FOR A LANDING. WHILE ENROUTE TO INT HE NOTICED AN ABNORMALLY HIGH EGT AND SUSPECTED AN ENGINE FIRE OR OTHER CRITICAL ENGINE PROBLEM. HE STATED THAT HE CONCLUDED HE WAS IN AN EMERGENCY SITUATION AND PROCEEDED TO LAND AT INT WITHOUT ATTEMPTING TO ALERT THE TOWER. HE FURTHER STATED THAT HE ATTEMPTED TO EXTEND THE GEAR PRIOR TO LANDING. THE LANDED GEAR WAS NOT FULLY EXTENDED OR HAD NEVER BEEN EXTENDED.

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.