# Accident 20190127000409A: Piper PA-32RT-300T, Pflugerville, TX, January 27, 2019

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: January 27, 2019, 15:12 local time
- Place: Pflugerville, TX
- Damage: Substantial damage
- Phase of flight: Takeoff: Climb Out
- Operating rules: General operating rules (Part 91)
- Location: 30.4242° N, 97.5686° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=30.4242&lon=-97.5686&mi=10
- Aircraft: N39650, registered now (https://openairdocs.org/aircraft/N39650) (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 PA-32RT-300T
- Reported engine: LYCOMING TI0-540 SER
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 1
- Pilot certificates: Private pilot
- Pilot flight hours: 1,741 total, 120 in this make and model, 70 in the last 90 days
- NTSB investigation: [NTSB CEN19LA076](https://openairdocs.org/ntsb/CEN19LA076) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20190127000409A

## Narrative

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

ON JANUARY 27, 2019 AT 1521 CDT, A PIPER PA32 BEARING REGISTRATION NUMBER N39650, REGISTERED TO STEWART DUNLAP LLC IMPACTED A PARKED VEHICLE DURING AN EMERGENCY LANDING AFTER LOSING POWER DURING INITIAL CLIMB OUT. THE ACCIDENT OCCURRED APPROXIMATELY 1.75 MILES NORTH OF AUSTIN EXECUTIVE AIRPORT (KEDC). THE AIRCRAFT WAS BEING OPERATED ON A PERSONAL FLIGHT. VISUAL METEOROLOGICAL CONDITIONS PREVAILED AT THE TIME AND NO FLIGHT PLAN WAS FILED. THE AIRCRAFT WAS SUBSTANTIALLY DAMAGED AND THE SOLE OCCUPANT-PRIVATE PILOT SUFFERED MINOR INJURIES.

## 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 CEN19LA076](https://openairdocs.org/ntsb/CEN19LA076), Jan 27, 2019: Piper PA32RT (N39650), Pflugerville, TX, substantial damage. Probable cause: The pilot's fuel mismanagement and his improper use and placement of the fuel selector, contrary to operating procedures, which resulted in a partial loss of engine power due to fuel starvation.

## Other reports on N39650 (5)

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

- [Incident 20071027829329I](https://openairdocs.org/incident/20071027829329I), Oct 27, 2007: Piper PA32RT300T (N39650), Millington, TN, Minor damage. (-23) On October 27, 2007, at approximately 1030 hours CST, the pilot [privacy data omitted] was flying in the pattern at Millington regional airport (nqa)…
- [Incident 20070415006519I](https://openairdocs.org/incident/20070415006519I), Apr 15, 2007: Piper PA32RT300T (N39650), Carbondale, IL. (-23) The pilot-in-command of N39650 and his wife, were flying on a VFR flight from chicago's midway airport to millington, Tennessee at 12,500 feet when the…
- [Incident 20051218032469I](https://openairdocs.org/incident/20051218032469I), Dec 18, 2005: Piper PA32RT300T (N39650), Steamboat Spgs, CO, Minor damage. (-23) Aircraft landed with the left main wheel off the left side of runway 32 at sbs and continued to exit the left side of runway 32 coming to rest in packed…
- [Incident 19970809028079I](https://openairdocs.org/incident/19970809028079I), Aug 9, 1997: Piper PA32RT300T (N39650), Heber Springs, AR, Minor damage. Lost electrical power IFR en route. Landed airport. Nose gear folded. Defective alterator. Manual extend incomplete
- [Incident 19960131004619I](https://openairdocs.org/incident/19960131004619I), Jan 31, 1996: Piper PA32RT300 (N39650), Memphis, TN. Narrative: at about 0802 on January 31, 1996, N39650 was cleared to land on runway 36C. About 1 minute later, he called tower and asked if he was lined up on…

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.