# NTSB WPR15LA190: Piper PA 20, N6939K, Yellow Pine, ID, June 18, 2015 - Type: NTSB accident investigation - Classification: Accident · Serious injuries · Limited investigation · Final report - Date: June 18, 2015, 12:20 local (18:20 UTC) - Place: Yellow Pine, ID - Coordinates: 44.905555, -115.487503 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=44.9056&lon=-115.4875&mi=10 - Phase of flight: [Initial climb](https://openairdocs.org/ntsb-phases/350) (OpenAirDocs' grouping) - Defining event: [Initial climb: Controlled flight into terr/obj (CFIT)](https://openairdocs.org/ntsb-events/120) - Highest injury: Serious injuries - Injuries: 2 serious - Status: Completed, report November 19, 2015 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: FAA FSDO - NTSB case key (mKey): 91393 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR15LA190 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/91393/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=91393 - Page: https://openairdocs.org/ntsb/WPR15LA190 ## Probable cause The pilot's delayed decision to go around after realizing that the airplane’s airspeed and altitude were too high, which resulted in an inadequate flare and bounced landing and a subsequent go-around in high-density altitude conditions. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Info processing/decision: decision making/judgment](https://openairdocs.org/ntsb-findings/02041520): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Piper PA-20, 5 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md?model=7102002), [All aircraft, 3,098 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md) - [Performance/control parameters: landing flare](https://openairdocs.org/ntsb-findings/01062041): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Piper PA-20, 4 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md?model=7102002), [All aircraft, 1,285 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md) - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Piper PA-20, 25 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=7102002), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/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-20, 1 case](https://openairdocs.org/ntsb-findings/01062035/cases.md?model=7102002), [All aircraft, 265 cases](https://openairdocs.org/ntsb-findings/01062035/cases.md) - [Temp/humidity/pressure: high density altitude](https://openairdocs.org/ntsb-findings/03031020): Environmental issues › Conditions/weather/phenomena · Effect on equipment; cases with it: [Piper PA-20, 1 case](https://openairdocs.org/ntsb-findings/03031020/cases.md?model=7102002), [All aircraft, 278 cases](https://openairdocs.org/ntsb-findings/03031020/cases.md) - [Object/animal/substance: tree(s)](https://openairdocs.org/ntsb-findings/03022020): Environmental issues › Physical environment · Contributed to outcome; cases with it: [Piper PA-20, 2 cases](https://openairdocs.org/ntsb-findings/03022020/cases.md?model=7102002), [All aircraft, 933 cases](https://openairdocs.org/ntsb-findings/03022020/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing-flare/touchdown: Abnormal runway contact](https://openairdocs.org/ntsb-events/090); cases with it: [Piper PA-20, 4 cases](https://openairdocs.org/ntsb-events/090/sequence.md?model=7102002), [All aircraft, 1,506 cases](https://openairdocs.org/ntsb-events/090/sequence.md) - [Landing-flare/touchdown: Loss of control on ground](https://openairdocs.org/ntsb-events/230); cases with it: [Piper PA-20, 21 cases](https://openairdocs.org/ntsb-events/230/sequence.md?model=7102002), [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md) - [Landing-aborted after touchdown: Loss of control on ground](https://openairdocs.org/ntsb-events/230); cases with it: [Piper PA-20, 21 cases](https://openairdocs.org/ntsb-events/230/sequence.md?model=7102002), [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md) - [Initial climb: Attempted remediation/recovery](https://openairdocs.org/ntsb-events/060); cases with it: [Piper PA-20, 6 cases](https://openairdocs.org/ntsb-events/060/sequence.md?model=7102002), [All aircraft, 1,422 cases](https://openairdocs.org/ntsb-events/060/sequence.md) - [Initial climb: Controlled flight into terr/obj (CFIT)](https://openairdocs.org/ntsb-events/120) (defining event); cases with it: [Piper PA-20, 2 cases](https://openairdocs.org/ntsb-events/120/sequence.md?model=7102002), [All aircraft, 1,074 cases](https://openairdocs.org/ntsb-events/120/sequence.md) ## Analysis The pilot reported that, while the airplane was on final approach to the airport, he realized that it was too high, so he performed a slip to lose altitude; however, due to the excessive speed and descent rate, the airplane subsequently landed hard just before midfield and bounced twice. The pilot then added full power to initiate a go-around. However, the airplane would not climb at a sufficient rate to clear the trees at the end of the runway. The airplane collided with a tree and subsequently impacted the ground adjacent to the departure end of the runway. Postaccident examination of the airplane revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation. The calculated density altitude was 7,697 ft mean sea level and the airplane was about 46 lbs under its maximum gross weight at the time of the accident. It is possible that these issues adversely affected the airplane's climb rate during the go-around. ## Factual narrative HISTORY OF FLIGHT On June 18, 2015, about 1220 mountain daylight time, a Piper PA-20 airplane, N6939K, sustained substantial damage when it impacted a tree and the ground during an aborted landing at the Johnson Creek Airport (3U2), Yellow Pine, Idaho. The private pilot and pilot-rated passenger were seriously injured. The airplane was registered to and operated by the pilot under the provisions of 14 Code of Federal Regulations Part 91 as a personal flight. Visual meteorological conditions prevailed for the flight and a flight plan was not filed. The cross-country flight originated from the Joseph State Airport (JSY), Joseph, Oregon, at an undetermined time. A witness reported to a Federal Aviation Administration (FAA) inspector that the airplane touched down just before mid-field and bounced twice before the pilot added power for a go-around. During the go-around, the nose of the airplane pitched up to a high angle while it was airborne and traveling down the runway. The left wing dipped shortly before colliding with a large tree about 30 feet above the ground near the southeast corner of the departure end of the runway. Subsequently, the airplane impacted a parked vehicle at the base of the tree. The pilot reported to an FAA inspector that as he turned onto final approach for runway 17, he realized he was too high in altitude, and initiated a slip to lose altitude. The pilot stated that there were three airplanes ahead of him on final, and two following him in the airport traffic pattern. The three airplanes ahead of him were clear of the runway and in the process of parking when he had crossed over the runway approach end of runway 17. He stated his forward speed and descent rate were too fast which resulted in a hard landing and subsequent bounces. The pilot said that he added full power to attempt a go-around. Despite his efforts, the airplane was not producing a positive rate of climb. As the airplane was approaching the departure end of the runway, the pilot turned the airplane to the left towards a small opening in the trees. During the turn, the left wing began to drop and the pilot corrected by leveling the wings. Subsequently, the airplane collided with a tree near the departure end of the runway. Postaccident examination of the airplane was conducted on site by the FAA inspector. The left wing separated and the fuselage and right wing were substantially damaged. The examination of the airplane revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation. AIRCRAFT INFORMATION The four-seat, high-wing, fixed-gear airplane, serial number (S/N) 20-43, was powered by a Lycoming O-290 engine, rated at 135 horse power. Using the pilot and passenger's reported weights, fuel onboard, weights of recovered luggage, and an estimated empty weight of the airplane, it was determined that the airplane would have been about 46 pounds under the published maximum gross weight of 1,800 pounds at the time of theaccident. METEOROLOGICAL INFORMATION A review of recorded data from the McCall Municipal Airport automated weather observation station, located 26 miles west of the accident site, revealed at 1151, conditions were wind variable at 3 knots, visibility 10 statute miles, clear skies, temperature 23 degrees Celsius, dew point 7 degrees Celsius, and an altimeter setting of 30.05 inches of mercury. Using the reported weather conditions and airport elevation, the calculated density altitude was about 6,998 feet mean sea level (msl), with a pressure altitude of about 4,839 feet msl. According to the FAA inspector, temperature at U42 at the time of the accident was about 29 degrees Celsius, calculates the density altitude to about 7,697 feet msl. AIRPORT INFORMATION The Johnson Creek Airport (U42) is a non-towered airport with a reported field elevation of 4,960 feet msl. The airport is equipped with one turf runway, runway 17 and 35, which is 3,400 feet in length and 150 feet wide. The airport is located in the bottom of a canyon surrounded by heavily wooded mountainous terrain. Numerous large trees border the sides and ends of the runway. TEST AND RESEARCH The manufacturer's supplied Airplane Flight Manual performance charts, revealed that the weather conditions present at the time of the accident, maximum gross weight of the airplane, and at the chart's maximum altitude value of 7,000 feet msl, the airplane would have a normal rate of climb of 360 feet per minute. ## Aircraft - Registration: [N6939K](https://openairdocs.org/deregistered/N6939K-2019-01-09), registration cancelled 2019-01-09, S/N 20-43, built 1950 (OpenAirDocs) - Reported make and model: PIPER PA 20 (150) - Registry model: [Piper PA-20](https://openairdocs.org/model/piper-pa-20) (registry code 7102002) (OpenAirDocs) - Registry engine: [Lycoming 0-290 series](https://openairdocs.org/engine/lycoming-0-290-series) (registry code 41506, 4 cycle) (OpenAirDocs) - Category: Airplane - Serial number: 20-43 - Year built: 1950 - Engines: LYCOMING O-290 SERIES 135 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Departed: JSY, JOSEPH, OR - Destination: 3U2, Yellow Pine, ID - Airport: 3U2, Johnson Creek, runway 17, 3,400 × 150 ft, grass/turf ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 54; injuries: serious; private; airplane ratings: single-engine land; medical: class 3, with waivers/limitations; seat: left; flight hours: 145 total - Pilot; age 49; injuries: serious; private; airplane ratings: single-engine land; medical: class 3, with waivers/limitations; seat: right; flight hours: 85 total ## Weather - Conditions: Visual (VMC), Day - Wind: variable at 3 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 72 °F, dew point 45 °F - Altimeter: 30.04 inHg - Observed at: KMYL, 26 nm away ## 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 20150618009079A](https://openairdocs.org/incident/20150618009079A), Jun 18, 2015: Piper PA-20, Yellow Pine, ID, Destroyed. The pilot flew the aircraft from joseph, or (jsy) to Johnson Creek, ID (3U2) with 200 lbs of gear (note: the gear that was in the aircraft was weighed on… ## Other investigations on N6939K (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 WPR13CA372](https://openairdocs.org/ntsb/WPR13CA372), Aug 14, 2013: Piper PA-20 (N6939K), Aurora, OR, substantial damage. Probable cause: The pilot's failure to maintain directional control while landing in gusting wind conditions, which resulted in a ground-loop. ## Docket (5 files) The files NTSB released with the investigation on October 19, 2015, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=91393. 1.2 MB in all. - FAA - Record of Conversation, Pilot (item 1, .PDF, 281 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40432896&FileExtension=.PDF&FileName=FAA%20-%20Record%20of%20Conversation,%20Pilot-Master.PDF - FAA - Record of Conversation, Witness (item 2, .PDF, 106 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40432897&FileExtension=.PDF&FileName=FAA%20-%20Record%20of%20Conversation,%20Witness-Master.PDF - FAA - Weight and Balance Calculations (item 3, .PDF, 81 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40432898&FileExtension=.PDF&FileName=FAA%20-%20Weight%20and%20Balance%20Calculations-Master.PDF - Piper-Airplane Flight Manual, Performance Excerpt (item 4, .PDF, 372 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40432899&FileExtension=.PDF&FileName=Piper-Airplane%20Flight%20Manual,%20Performance%20Excerpt-Master.PDF - Photographs (item 5, .PDF, 2 photos, 359 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40432900&FileExtension=.PDF&FileName=Photographs-Master.PDF 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.