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

Piper PA32R accident near Rensselaer, Indiana, March 11, 2020

On March 11, 2020 at about 11:36 am local time, a 2005 Piper PA32R, registered N599ST, was destroyed in an accident during approach (IFR missed approach) near Rensselaer, Indiana (Jasper County airport). It was a personal flight under general aviation rules (Part 91). 1 person was seriously injured. The weather was instrument conditions (cloud, fog or low visibility).

The NTSB's probable cause their words, unchanged

The non-instrument rated pilot’s failure to establish a climb while initiating a missed approach after conducting an instrument approach below weather minimums.

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

What the record shows

Date
March 11, 2020 · about 11:36 am local time
Place
Rensselaer, Indiana · Jasper County · map
Type
Accident
Injuries
1 person was seriously injured.
Weather
instrument conditions (cloud, fog or low visibility)
Aircraft
Piper PA32R 301T, built 2005 · all PA32Rs on the register
Registration
N599ST · no longer on the register · serial 3257383
Damage
Destroyed
Flight
Personal flight · general aviation rules (Part 91)

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

The non-instrument rated pilot planned a cross-country flight in instrument meteorological conditions. The pilot obtained weather information and filed an instrument flight rules (IFR) flight plan through his on-line weather/flight planning account the day of the accident. Air traffic control data indicated that the flight and initial portion of the instrument approach proceeded normally. Position data revealed that the airplane proceeded inbound and descended as expected along the assigned approach course. The airplane passed the runway approach threshold at an altitude of about 300 ft above ground level (agl) and entered a gradual left turn; however, the established descent continued. The final data point depicted the airplane about 0.14 mile east of the runway, about 100 ft agl. The pilot’s memory of the instrument approach was vague due to his injuries; however, he stated that he was unable to see the runway and decided to execute a missed approach. At some point, he either made a “bad input” into the autopilot or the autopilot commanded a slight turn or descent. The accident site was located immediately southeast of the final position data point. A postimpact fire destroyed much of the airplane. A postaccident examination did not identify any preimpact abnormities that would have contributed to the accident. The instrument approach procedure allowed for descent as low as 250 ft above the runway elevation and required 1-3/8 to 1 mile flight visibility to land depending on the capabilities of the airplane. Just before the accident the automated weather reporting station recorded calm winds, one-half mile visibility in fog, and an overcast ceiling at 200 ft above ground level. The pilot held a private pilot certificate with a single-engine land airplane rating; however, he did not have an instrument rating. The accident was consistent with the non-instrument rated pilot’s loss of control during a go-around attempt after conducting an instrument approach in weather conditions that were below minimums.

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. Collision with terrain or object (not controlled flight into terrain) during approach (IFR missed approach) defining event

The NTSB's findings

  • Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • Personnel issues › Experience/knowledge › Experience/qualifications › Qualification/certification › Pilot
  • Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Low ceiling › Effect on operation
  • Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Low visibility › Effect on operation
  • Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Climb rate › Not attained/maintained

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 1,012 hours in all; 600 in this make and model
  • Last flight review: September 26, 2019
  • Medical certificate: Class 3 (without waivers/limitations)
  • Seat: left
  • Injury: serious injuries

The aircraft

  • Airframe total time: 2,650 hours
  • Last inspection: annual inspection, December 27, 2019; 20 hours since
  • Maximum gross weight: 3,800 lb
  • Seats: 6
  • Landing gear: retractable
  • Engine: Lycoming TIO-540 (piston); 610 hours total
  • Fire on the ground

The flight

  • Departed from: LAF Lafayette IN at 10:05 am
  • Destination: RZL Rensselaer IN
  • Flight plan: IFR
  • Runway 18, 4,000 ft by 60 ft

Weather at the time

  • Light: not reported
  • Wind: at 0 knots
  • Visibility: 0.5 statute miles
  • Sky: overcast at 200 ft
  • Temperature: 36°F (2°C), dew point 36°F (2°C)
  • Altimeter: 30.08 inHg
  • Observation at 11:35 am from KRZL

Weather report (METAR): KRZL 111135Z AUTO 00000KT 1/2SM FG OVC002 02/02 A3008 RMK AO2=

Injuries

FatalSeriousMinorNone
Flight crew1

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

13 documents, released by the NTSB on February 23, 2022. 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.