Piper PA32 N534Z

Summary

On 20 October 2019 at about 23:21 local time, a Piper PA32 registered N534Z was involved in an accident near Raleigh, North Carolina, United States. 2 people were on board and 2 died. The aircraft was destroyed. The NTSB has published a probable cause for this accident; it is quoted in full below.

Date

20 October 2019 at 23:21

Classification

Accident

Location

Raleigh, North Carolina, United States

Nearest airport

Raleigh-Durham Int (RDU)

Coordinates

35.8542, -78.7577

Aircraft

Piper PA32

Registration

N534Z

Category

Airplane

Year built

1989

Engines

1

Operator

Not recorded

Operating rule

Part 91: General Aviation

Purpose of flight

Personal

Phase of flight

Not recorded

Route

Columbus → Raleigh

Aircraft damage

Destroyed

Weather

VMC

Light

Night/Dark

NTSB number

ERA20FA014

2 people died.

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 flight experience.

Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.

Read the full NTSB narrative

During a night, instrument flight rules flight in instrument meteorological conditions, the pilot checked in with approach control and was told to expect an instrument approach to a different runway than the one he had planned for. According to air traffic control communications, the pilot subsequently reported some issues interacting with his airplane’s GPS and autopilot. He had difficulty reading back instructions, missed radio calls, and did not maintain assigned altitudes and headings. The air traffic controller eventually provided him with radar vectors onto the final approach course, and when the airplane was about 9 miles away from the airport the pilot reported that he had broken out of the clouds and could see lights below. The controller cleared the pilot for a visual approach, but the pilot had difficulty visually acquiring the runway lights, and the controller increased their intensity. The controller subsequently issued two low altitude alerts to the pilot while on final approach. The pilot’s last radio transmission indicated he had the runway in sight, but radio and radar contact were lost when the airplane was on short final approach. The wreckage was found the next morning in a densely wooded and sparsely lit state park about just over a mile from the runway threshold with the wreckage facing the runway; the airplane was destroyed. Damage to the treetops indicated a controlled, gradual descent into the trees, indicative of the pilot not maintaining adequate clearance from the ground during final approach. Postaccident examination of the wreckage did not reveal evidence of a mechanical malfunction or anomaly with the airplane that would have precluded normal operation. A review of the pilot’s logbook revealed a lack of recent night and instrument experience; he had not logged the required night and instrument procedures to act as pilot-in-command for a flight carrying passengers at night and in IMC. The pilot’s issues with using his airplane’s GPS and autopilot during the accident flight were likely due to a lack of recent use in actual or simulated instrument conditions.

Quoted verbatim from the NTSB record.