# Accident 20191020019319A: Piper PA-32-301, Raleigh, NC, October 20, 2019 - Type: FAA accident report (Accident/Incident Data System), as reported - Date: October 20, 2019, 19:32 local time - Place: Raleigh, NC - Damage: Destroyed - Phase of flight: Landing: Approach - Operating rules: General operating rules (Part 91) - Location: 35.8542° N, 78.7577° W: From the FAA - Nearby events: https://openairdocs.org/map.md?lat=35.8542&lon=-78.7577&mi=10 - Aircraft: N534Z, a cancelled registration (https://openairdocs.org/deregistered/N534Z-2020-08-02) (OpenAirDocs) - Registry model: Piper PA-32-301 (registry code 7103207, https://openairdocs.org/model/piper-pa-32-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-32-301 - Reported engine: LYCOMING IO-540 SER - People aboard: 2 - Fatal injuries: 2 - Other injuries: 0 - Pilot certificates: Private pilot - NTSB investigation: [NTSB ERA20FA014](https://openairdocs.org/ntsb/ERA20FA014) (OpenAirDocs) - FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/) - Page: https://openairdocs.org/incident/20191020019319A ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. RONALD GATEWOOD: AIRWORTHINESS SAFETY INSPECTOR ^PRIVACY DATA OMITTED^ AIRCRAFT ACCIDENT INSPECTOR REPORT DATE OF REPORT: 11/05/2019 ACCIDENT AIRCRAFT: PIPER PA-32-301, N534Z, S/N 3206054 SINGLE ENGINE LAND AIRPLANE LOCATION: RALEIGH, NCN534Z THE AIRCRAFT LOGBOOKS WERE REVIEWED AND THE AIRCRAFT WAS DETERMINED TO BE IN AIRWORTHY CONDITION. NO MAINTENANCE LOG BOOK ENTRIES WERE DOCUMENTED ON 11/5/2019. THE AIRCRAFT IMPACTED THE TOPS OF TREES IN A DESCENDING TO LAND, STABLE FLIGHT CONDITION. THE FUEL TANKS SHOWED SIGNS OF UNUSED FUEL. THE GRAPHIC ENGINE MONITOR WAS SENT OUT IN ORDER TO DOWNLOAD ENGINE DATA TO VALIDATE ENGINE OPERATION AT THE TIME OF IMPACT. THE PROPELLER WAS LOCATED APPROXIMATELY 100 YARDS FROM THE AIRCRAFT AND A GROUND IMPACT SCAR OF THE PROPELLER WAS LOCATED AT APPROXIMATELY 50 YARDS WITH FORWARD MOVEMENT INDICATIONS. THE BROKEN AND SEPARATED STARTER RING GEAR CIRCUMFERENCE WAS FOUND WITH THE PROPELLER. THE PROPELLER INDICATED SIGNS OF ROTATIONAL FORCE AT THE TIME OF IMPACT WITH THE TREE LIMBS. THE ENGINE SEPARATED FROM THE ENGINE MOUNT AND WAS FOUND NEAR THE AIRFRAME. THE PROPELLER ATTACHMENT BOLTS WERE SECURE IN THE CRANKSHAFT. ATTACHMENT OF THE THROTTLE, MIXTURE AND PROPELLER LINKAGE WERE CONFIRMED SECURE AT EACH END OF THE CABLES. AIRFRAME CONTROLS CHECKED FOR CONTINUITY AND ALL COMPONENTS ACCOUNTED FOR DURING THE SALVAGE PROCESS. THE AIRCRAFT WAS EQUIPPED WITH SUFFICIENT AVIONICS AND BACKUP SYSTEMS FOR THE INTENDED FLIGHT. ^PRIVACY DATA OMITTED^ ON OCTOBER 20, 2019 THE SUBJECT AIRCRAFT CRASH LANDED INTO WILLIAM B. UMSTEAD STATE PARK SOUTH OF THE RDU AIRPORT ON APPROACH TO RUNWAY 32. THERE WERE TWO OCCUPANTS OF THE AIRCRAFT, PILOT HARVEY L. PARTRIDGE, JR. AND HIS WIFE PATRICIA PARTRIDGE. BOTH WERE FATALLY INJURED. AT THE TIME OF THE ACCIDENT, THE WIND CONDITIONS REPORTED BY RDU ATC WERE APPROXIMATELY 340 DEGREES AT 7 KNOTS, AND MOST OTHER AIRCRAFT REPORTED THE BASES OF THE CLOUDS AT 1600-1800? MSL, WHICH WOULD BE APPROXIMATELY 1200-1400? AGL IN THE AREA OF RDU AIRPORT. THE ACCIDENT OCCURRED AT APPROXIMATELY 7:30PM LOCAL TIME, WHICH ON OCTOBER 20TH, 2019 WAS NIGHT TIME (APPROXIMATELY ONE HOUR AFTER SUNSET). BASED ON LISTENING TO THE AUDIO PROVIDED BY AIR TRAFFIC CONTROL (ATC) THE FIRST SIGN OF ANY SIGNIFICANT ISSUE WAS WHEN THE PILOT REPORTED, ?RALEIGH TOWER, SARATOGA 34Z, I NEED TO CLIMB, MY GPS, MY APPROACH JUST SHUT OFF.? THIS OCCURRED WHILE ON THE GPS APPROACH INTO RUNWAY 32 AT RDU. FROM THERE, THE PILOT WAS ASSISTED BY ATC WITH HEADING AND ALTITUDE WHILE PERFORMING A GO-AROUND. HOWEVER, THE OPTIONS WERE LIMITED, AS RUNWAY 5L WAS CLOSED AND ALL REMAINING TRAFFIC WAS LANDING EITHER RUNWAY 32 OR RUNWAY 5R. WHEN CHECKING BACK IN WITH RDU TOWER, THE AIRCRAFT REPORTED HAVING THE RUNWAY IN SIGHT. AT THAT POINT, AND THROUGHOUT THE REMAINDER OF THE FLIGHT, IT APPEARED FROM LOOKING AT THE RADAR PLOT THAT THE AIRCRAFT?S HEADING, SPEED, AND ALTITUDE WERE STABLE. IT IS UNCLEAR IF THE GPS OR AUTOPILOT WERE FUNCTIONAL AT THAT TIME. HIS ALTITUDE GRADUALLY DECREASED OVER THE COURSE OF ABOUT TWO MINUTES FROM 1400? MSL UNTIL HIS LAST APPEARANCE AT 700? MSL (APPROXIMATELY 300? AGL), AT WHICH POINT HE DISAPPEARED FROM THE RADAR PLOT AND MADE NO MORE TRANSMISSIONS. NO DISTRESS SIGNAL WAS EVER HEARD; THE PILOT?S LAST TRANSMISSION WAS, ?34Z, I HAVE THE RUNWAY IN SIGHT.? AT THAT POINT, THE RADAR PLOT WAS SHOWING THE AIRCRAFT AT 1000? MSL. FOURTEEN SECONDS LATER, THE RADAR PLOT SHOWED THE AIRCRAFT AT 900? MSL. NINE SECONDS AFTER THAT, THE RADAR PLOT SHOWED THE AIRCRAFT AT 800? MSL. FIFTEEN SECONDS AFTER THAT, THE RADAR PLOT SHOWED THE AIRCRAFT AT 700? MSL, WHERE IT REMAINED ON THE PLOT WITHOUT APPARENT FORWARD MOTION UNTIL IT DROPPED OFF THE RADAR 45 SECONDS LATER. ## 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 ERA20FA014](https://openairdocs.org/ntsb/ERA20FA014), Oct 20, 2019: Piper PA32 (N534Z), Raleigh, NC, destroyed, 2 fatal. Probable cause: The pilot’s failure to maintain a safe glidepath during final approach to the runway, which resulted in a collision with trees and terrain. Contributing was the pilot’s lack of recent instrument… ## Other reports on N534Z (2) Matched to the same aircraft by N-number and date. - [Incident 20040716024499I](https://openairdocs.org/incident/20040716024499I), Jul 16, 2004: Piper PA32301 (N534Z), Fort Pierce, FL. (-23) On 07/16/2004 at 1656Z a Piper PA-32-301 N534Z, piloted by thomas walsh while landing on runway 27 at Fort Pierce, st. Lucie airport, exited the runway… - [Incident 20010505017549I](https://openairdocs.org/incident/20010505017549I), May 5, 2001: Piper PA32301 (N534Z), Fort Pierce, FL, Minor damage. (-23) On may 5, 2001, at 1015EDT, a Piper PA32-301, N534Z, owned by gray walsh, inc., and piloted by Mr. Thomas j. walsh, lost directional control during the… 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.