The U.S. aircraft register, updated daily
Accidents · NTSB ERA20FA014 · Final report

Piper PA32 accident near Raleigh, North Carolina, October 20, 2019

On October 20, 2019 at about 11:21 pm local time, a 1989 Piper PA32, registered N534Z, was destroyed in an accident during approach (IFR final approach) near Raleigh, North Carolina (Raleigh-Durham Int airport). It was a personal flight under general aviation rules (Part 91). 2 people were killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

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.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
October 20, 2019 · about 11:21 pm local time
Place
Raleigh, North Carolina · Raleigh-Durham Int · map
Type
Accident
Injuries
2 people were killed.
Weather
visual conditions (good weather)
Aircraft
Piper PA32 301, built 1989 · all PA32s on the register
Registration
N534Z · no longer on the register · serial 3206054
Damage
Destroyed
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Controlled flight into terrain or object (CFIT) during approach (IFR final approach) defining event

The NTSB's findings

  • Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Descent/approach/glide path › Not attained/maintained
  • Personnel issues › Action/decision › Info processing/decision › Identification/recognition › Pilot
  • Personnel issues › Experience/knowledge › Experience/qualifications › Recent instrument experience › Pilot

Pilot

  • Certificate: private
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 2,956 hours in all; 10 in the last 90 days; 4 in the last 30 days
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: fatal

The aircraft

  • Airframe total time: 2,172 hours
  • Last inspection: annual inspection, December 14, 2018; 48 hours since
  • Maximum gross weight: 3,600 lb
  • Seats: 6
  • Landing gear: fixed
  • Engine: Lycoming IO-540-K1G5 (piston); 2,172 hours total

The flight

  • Departed from: CSG Columbus GA at 8:05 pm
  • Destination: RDU Raleigh NC
  • Flight plan: IFR
  • Runway 32, 3,570 ft by 100 ft

Weather at the time

  • Light: night, dark
  • Wind: at 6 knots
  • Visibility: 10 statute miles
  • Sky: broken clouds at 1,000 ft
  • Temperature: 61°F (16°C), dew point 57°F (14°C)
  • Altimeter: 29.86 inHg
  • Observation at 10:51 pm from KRDU, 1 miles away

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

24 documents, released by the NTSB on November 3, 2021. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.