# NTSB CEN20LA118: Piper PA32R, N599ST, Rensselaer, IN, March 11, 2020 - Type: NTSB accident investigation - Classification: Accident · Serious injuries · Class 3 · Limited · Final report - Date: March 11, 2020, 06:36 local (11:36 UTC) - Place: Rensselaer, IN - Coordinates: 40.948333, -87.178886 - Nearby events: https://openairdocs.org/map.md?lat=40.9483&lon=-87.1789&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Defining event: [Approach-IFR missed approach: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470) - Highest injury: Serious injuries - Injuries: 1 serious - Status: Completed - Report: Approved by Office Director - Investigation class: Class 3 - NTSB office: Central Region - Parties: FAA - FSDO, Piper Aircraft, Inc, Lycoming Aircraft Engines - NTSB case key (mKey): 101061 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN20LA118 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/101061/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=101061 - Page: https://openairdocs.org/ntsb/CEN20LA118 ## Probable cause The non-instrument rated pilot’s failure to establish a climb while initiating a missed approach after conducting an instrument approach below weather minimums. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Piper PA-32R-301T, 8 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=7103220), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Experience/qualifications: qualification/certification](https://openairdocs.org/ntsb-findings/02031010): Personnel issues › Experience/knowledge · Pilot; cases with it: [Piper PA-32R-301T, 1 case](https://openairdocs.org/ntsb-findings/02031010/cases.md?model=7103220), [All aircraft, 280 cases](https://openairdocs.org/ntsb-findings/02031010/cases.md) - [Ceiling/visibility/precip: low ceiling](https://openairdocs.org/ntsb-findings/03035010): Environmental issues › Conditions/weather/phenomena · Effect on operation; cases with it: [Piper PA-32R-301T, 2 cases](https://openairdocs.org/ntsb-findings/03035010/cases.md?model=7103220), [All aircraft, 190 cases](https://openairdocs.org/ntsb-findings/03035010/cases.md) - [Ceiling/visibility/precip: low visibility](https://openairdocs.org/ntsb-findings/03035015): Environmental issues › Conditions/weather/phenomena · Effect on operation; cases with it: [Piper PA-32R-301T, 1 case](https://openairdocs.org/ntsb-findings/03035015/cases.md?model=7103220), [All aircraft, 175 cases](https://openairdocs.org/ntsb-findings/03035015/cases.md) - [Performance/control parameters: climb rate](https://openairdocs.org/ntsb-findings/01062035): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Piper PA-32R-301T, 1 case](https://openairdocs.org/ntsb-findings/01062035/cases.md?model=7103220), [All aircraft, 265 cases](https://openairdocs.org/ntsb-findings/01062035/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Approach-IFR missed approach: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470) (defining event); cases with it: [Piper PA-32R-301T, 19 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=7103220), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis 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. ## Factual narrative On March 11, 2020, about 0636 central daylight time, a Piper PA-32R-301T airplane, N599ST, was destroyed when it was involved in an accident near Jasper County Airport (RZL), Rensselaer, Indiana. The pilot was seriously injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. 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 revealed that the airplane departed the Purdue University Airport (LAF) at 0607 on an IFR flight plan en route to RZL. At 0620, the pilot was cleared for the area navigation approach (RNAV) to runway 18. At 0626, the pilot was instructed to change to the airport common traffic advisory frequency (CTAF) and to cancel the flight plan through flight service after landing. The pilot acknowledged and no further communications were recorded. Position data depicted the airplane proceed inbound and descend along the approach course. At 0635:49, the airplane crossed the runway approach threshold about 1,000 ft mean sea level (msl). The airplane entered a gradual left turn; however, the descent continued. The final data point was recorded at 0636:07. The airplane was about 0.14 mile east of the runway and about 800 ft msl. The airport elevation was 698 ft. Due to his injuries and hospitalization, the pilot was unable to provide a statement until several months after the accident. The pilot indicated that his memory of the accident was vague due to his injuries; however, he remembered that before the flight he obtained a weather briefing and departed without a flight plan. He added that the automated weather station at RZL reported overcast clouds at 400 ft. and one mile visibility, so he elected to conduct a RNAV/GPS approach to runway 18. He was unable to see the runway and executed a missed approach. He believed at some point on the missed approach that he either made a “bad input” into the autopilot or the autopilot commanded a slight turn or descent. The RNAV 18 approach 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. At 0635, the automated weather reporting station at RZL recorded calm winds, one-half mile visibility in fog, and an overcast ceiling at 200 ft above ground level. Federal Aviation Administration records indicated that the pilot held a private pilot certificate with a single-engine land airplane rating; however, he did not have an instrument rating. The airplane wreckage was recovered to a salvage facility where engine and airframe examinations were conducted. The airframe had extensive fire and thermal damage which limited the scope of the examination. Much of the cabin and instrument panel was destroyed by the fire. Flight control continuity from the cockpit to the ailerons, rudder, and stabilator wasestablished, with the exception of a broken cable segment. Further examination of the cable segment observed failure signatures consistent with fracture after exposure to the postimpact fire while still under tension. The stabilator trim assembly corresponded to a neutral trim setting. The flap control rod position was consistent with a flaps up (retracted) setting. The nose and left main landing gear actuators were in the extended position which corresponded to a landing gear down (extended) position. The right landing gear was impact separated and its actuator was observed about mid-travel position. Examination of the engine and propeller did not identify any preimpact abnormalities. ## Aircraft - Registration: [N599ST](https://openairdocs.org/deregistered/N599ST-2021-07-03), registration cancelled 2021-07-03, S/N 3257383, built 2005 (OpenAirDocs) - Reported make and model: Piper PA32R (301T) - Registry model: [Piper PA-32R-301T](https://openairdocs.org/model/piper-pa-32r-301t) (registry code 7103220) (OpenAirDocs) - Registry engine: [Lycoming TI0-540 series](https://openairdocs.org/engine/lycoming-ti0-540-series) (registry code 41533, turbo-prop) (OpenAirDocs) - Category: Airplane - Serial number: 3257383 - Year built: 2005 - Airframe hours: 2650 - Engines: Lycoming TIO-540 300 horsepower reciprocating - Damage: Destroyed - Fire: On-Ground - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, December 27, 2019, 20 hours before - Departed: LAF, LaFayette, IN - Destination: RZL, Rensselaer, IN - Flight plan: IFR - Airport: RZL, Jasper County, runway 18, 4,000 × 60 ft, concrete - Equipment: ADS-B, Auto-pilot ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 48; injuries: serious; private; airplane ratings: single-engine land; medical: class 3, without waivers/limitations; last flight review September 26, 2019; seat: left; restraint: 3-point; flight hours: 1,012 total, 600 in this make and model ## Weather - Conditions: Instrument (IMC), Not reported - Wind: 0° at 0 knots - Visibility: 0.5 statute miles - Lowest ceiling: 200 ft overcast - Temperature: 36 °F, dew point 36 °F - Altimeter: 30.08 inHg - Observed at: KRZL - METAR: KRZL 111135Z AUTO 00000KT 1/2SM FG OVC002 02/02 A3008 RMK AO2= ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20200311001439A](https://openairdocs.org/incident/20200311001439A), Mar 11, 2020: Piper PA-32R-301T, Rensselaer, IN, Destroyed. Note: purdue airport in west lafayette operates on eastern time. Jasper County Airport operates on central time. The duration of the flight was about a half… ## Docket (13 files) The files NTSB released with the investigation on February 23, 2022, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=101061. 216 MB in all. - Pilot/operator aircraft accident report, NTSB form 6120.1 (item 1, PDF, 9 pages, 565 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=12490084&FileExtension=pdf&FileName=NTSB%20Pilot%20Aircraft%20Accident%20Report%20-%20Jonkman_Redacted-Rel.pdf - Memo exam (item 2, PDF, 2 pages, 155 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13188263&FileExtension=pdf&FileName=Examination%20Summary-Rel.pdf - Photos (item 3, PDF, 6 pages, 6.4 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=12830402&FileExtension=pdf&FileName=Photo%201-Rel.pdf - Statement of party representatives to NTSB investigation (item 4, PDF, 2 pages, 520 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=12490173&FileExtension=pdf&FileName=Party%20Forms_Redacted-Rel.pdf - Rwy 18 approach (item 5, PDF, 1 page, 220 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=12490248&FileExtension=pdf&FileName=RWY%2018%20Approach-Rel.pdf - Weather reports and records (item 6, PDF, 1 page, 277 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=12490094&FileExtension=pdf&FileName=WX-Rel.pdf - Materials laboratory factual report (item 7, PDF, 24 pages, 31 photos, 5.4 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13140874&FileExtension=pdf&FileName=21-099%20-%20Materials%20Lab%20Factual%20Report%20(CEN20LA118)-Rel.pdf - Release of aircraft wreckage, NTSB form 6120.15 (item 8, PDF, 1 page, 281 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13158994&FileExtension=pdf&FileName=Release-of-Wreckage-Form%20(printed)-Rel.pdf - ATC specialists factual report (item 9, PDF, 5 pages, 734 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13179198&FileExtension=pdf&FileName=CEN20LA118%20-%20ATC%20Specialists%20Report-Rel.pdf - ATC attachment 1 - ADS-B data (item 10, CSV, 702 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13179105&FileExtension=csv&FileName=CEN20LA118%20-%20ADS-B%20Data-Rel.csv - ATC attachment 2 - ATC audio transcript - partial (item 11, PDF, 3 pages, 62 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13179003&FileExtension=pdf&FileName=CEN20LA118%20-%20ATC%20Specialists%20Report%20-%20Attachment%202-Rel.pdf - ATC attachment 3 - flight track graphics (item 12, PDF, 4 pages, 1.8 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13178175&FileExtension=pdf&FileName=CEN20LA118%20-%20ATC%20Specialists%20Report%20-%20Attachment%203-Rel.pdf - ATC attachment 4 - ATC audio - sector 51 radar (R51) controller (item 13, WAV, 199 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13179274&FileExtension=wav&FileName=CEN20LA118%20-%20ATC%20Audio%20-%20R51-Rel.wav 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. --- 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.