# NTSB WPR14LA336: Piper PA 32R-300, N4646F, West Jordan, UT, August 10, 2014 - Type: NTSB accident investigation - Classification: Accident · Serious injuries · Limited investigation · Final report - Date: August 10, 2014, 09:04 local (15:04 UTC) - Place: West Jordan, UT - Coordinates: 40.60361, -111.991386 - Nearby events: https://openairdocs.org/map.md?lat=40.6036&lon=-111.9914&mi=10 - Phase of flight: [Initial climb](https://openairdocs.org/ntsb-phases/350) (OpenAirDocs' grouping) - Defining event: [Initial climb: Loss of engine power (partial)](https://openairdocs.org/ntsb-events/342) - Highest injury: Serious injuries - Injuries: 3 serious - Status: Completed, report July 13, 2015 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: Federal Aviation Administration, Lycoming Engines, Piper Aircraft - NTSB case key (mKey): 89840 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR14LA336 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/89840/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=89840 - Page: https://openairdocs.org/ntsb/WPR14LA336 ## Probable cause A partial loss of engine power during initial climb for reasons that could not be determined due to the severity of the damage to the engine. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Not determined](https://openairdocs.org/ntsb-findings/05000000): Not determined › Not determined · Unknown/Not determined (probable cause); cases with it: [Piper PA-32R-300, 5 cases](https://openairdocs.org/ntsb-findings/05000000/cases.md?model=7103213), [All aircraft, 2,247 cases](https://openairdocs.org/ntsb-findings/05000000/cases.md) - [Object/animal/substance: pole](https://openairdocs.org/ntsb-findings/03022010): Environmental issues › Physical environment · Not specified; cases with it: [Piper PA-32R-300, 1 case](https://openairdocs.org/ntsb-findings/03022010/cases.md?model=7103213), [All aircraft, 142 cases](https://openairdocs.org/ntsb-findings/03022010/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Initial climb: Loss of engine power (partial)](https://openairdocs.org/ntsb-events/342) (defining event); cases with it: [Piper PA-32R-300, 4 cases](https://openairdocs.org/ntsb-events/342/sequence.md?model=7103213), [All aircraft, 1,858 cases](https://openairdocs.org/ntsb-events/342/sequence.md) - [Initial climb: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Piper PA-32R-300, 32 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=7103213), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis Witnesses located adjacent to the accident site reported that they observed the airplane depart, and that, as it was climbing, they heard the pilot state, "emergency," several times on the airport's common traffic advisory frequency; however, the pilot did not specify the nature of the emergency. The airplane subsequently struck a light post and then landed in an open soccer field south of the airport, and a postimpact fire ensued. Other witnesses located at the airport reported that the engine seemed to be backfiring throughout the entire takeoff and accident sequence. The pilot reported that he recalled the initial takeoff sequence and making the distress call; however, he did not recall the nature of the emergency or the accident sequence. Postaccident examination of the airplane, flight control systems, engine, and propeller revealed no evidence of any preimpact mechanical malfunctions. Review of the airplane manufacturer's takeoff performance charts revealed that, at the time of the accident, the weather and environmental conditions were within the airplane's takeoff performance limitations. Given that the witnesses reported that the engine was backfiring and that the pilot declared an emergency, it is likely that the engine experienced a partial loss of power during initial climb. Due to the severity of the damage to the engine, the reason for the loss of power could not be determined. ## Factual narrative The six-seat, low-wing, retractable-gear airplane, serial number (S/N) 32R-7680471, was powered by a Lycoming IO-540-K1G5D engine, serial number L-15161-48A, rated at 300 horse power. It was equipped with a McCauley model B3D36C433-O/I-90VSA-1 three bladed adjustable pitch propeller. Review of the airplane maintenance logbooks revealed that the most recent annual inspection was conducted on July 27, 2013, at an airframe total time of 1,721 hours. Using the pilot and passenger's reported weights, full fuel, weights of recovered luggage, and an estimated weight of the airplane, it was determined that the airplane would have been under the published maximum gross weight of 3,600 pounds. The actual weight and balance calculations of the airplane were not located within the wreckage, and were most likely consumed by the postimpact fire. Review of the manufacturer's supplied Flaps Up and 25-degree Flaps Takeoff Performance charts, located in the Pilot's Operating Handbook, revealed that the weather conditions present at the time of the accident were within the airplane's performance capability parameters. Using the manufacturer's supplied takeoff ground roll calculation charts for takeoffs with and without two notches of flaps, reported weather conditions, and maximum gross weight of the airplane, the Flaps Up takeoff ground roll was calculated to be about 4,250 feet, and flaps second notch takeoff ground roll to be about 3,000 feet. Using the manufacturer's supplied Gear Up performance calculation charts, reported weather conditions and maximum gross weight of the airplane, the climb performance with the gear in the "UP" position was calculated to be about 500 feet per minute. The South Valley Regional Airport (U42) is a non-towered airport with a reported field elevation of 4,606 feet msl. The airport is equipped with one asphalt runway, runway 16 and 34, which is 5,862 feet long and 100 feet wide. On August 10, 2014, about 0904 mountain daylight time, a Piper PA-32R-300, N4646F, was destroyed during a forced landing shortly after takeoff from the South Valley Regional Airport (U42), West Jordan, Utah. The airplane was registered to and operated by the pilot under the provisions of Title 14 Code of Federal Regulations Part 91. The private pilot and his two passengers sustained serious injuries. Visual meteorological conditions prevailed, and no flight plan was filed for the personal cross-country flight, which was originating at the time of the accident. The intended destination was Boise, Idaho. Witnesses located adjacent to the accident site reported that the airplane departed from runway 16. As the airplane was ascending, a radio transmission from the pilot in the blind on the airports Common Traffic Advisory Frequency (CTAF) stated emergency several times, however, they did not specify what the emergency was. Witnesses reported that the airplane struck a light post and subsequently landed in an open soccer field south of the airport where apostimpact fire ensued. Additional witnesses located at the airport reported that the airplane lifted off the ground about 3,500 feet from the approach end of runway 16, and that the airplane never climbed above 100 to 150 feet above ground level. In addition, they reported that the engine seemed to be backfiring throughout the entire takeoff and accident sequence. Examination of the accident site by a Federal Aviation Administration inspector revealed that the airplane came to rest upright about 0.5 miles south of the departure end of runway 16. All major structural components of the airplane were located within the wreckage debris path. The inboard areas of both wings and the center portion of the fuselage were mostly consumed by fire. The inspector reported that the left outboard wing fuel tank, which was breached, contained blue liquid consistent with 100 low lead fuel. The wreckage was recovered to a secure location for further examination. In a written statement and telephone conversation with the National Transportation Safety Board (NTSB) investigator-in-charge (IIC), the pilot reported that prior to the flight; he conducted a preflight check of the airplane, and noticed no abnormalities with the airplane. After the pilot and passengers boarded the airplane, he started the engine and taxied out to the departure end of the runway. During the pretakeoff engine checks, he noticed that one of the magnetos was fouled, and was able to correct it by leaning the mixture. The pilot stated that he obtained the weather via the airports automated weather observing system, and noted that the density altitude was over 7,000 feet. He added that immediately after lifting off of the runway, he made a distress call over the CTAF, however, did not recall anything about the nature of the emergency or the accident sequence. A review of recorded data from the Salt Lake City International Airport automated weather observation station, located 11 miles north of the accident site, revealed at 0853, conditions were wind from 160 degrees at 4 knots, visibility 10 statute miles, few clouds at 14,000 feet, few clouds at 20,000 feet, temperature 23 degrees Celsius, dew point 9 degrees Celsius, and an altimeter setting of 30.20 inches of mercury. Using the reported weather conditions and airport elevation, the calculated density altitude was about 7,447 feet mean sea level (msl), with a pressure altitude of about 4,348 feet msl. Examination of the recovered wreckage was performed on October 15, 2014, at the facilities of Air Transport, Phoenix, Arizona, by representatives of Piper Aircraft and Lycoming Engines under the supervision of the NTSB IIC. The examination revealed that the engine and right wing were separated to facilitate wreckage recovery and transport. The forward portion of the fuselage from the baggage compartment to the firewall was mostly consumed by fire. Two forward seats (pilot/copilot) and the left and right rear row seats were found installed.Remains of two shoulder restraints were located within the main wreckage. The cockpit controls, including the throttle, propeller, and mixture levers, instruments, and avionics were damaged and mostly consumed by fire. The empennage, including the vertical stabilizer, rudder, and horizontal stabilator remained intact with the exception of each outboard section of the horizontal stabilator, which were cut to facilitate wreckage transport. The trim tab remained attached to its respective mount. The fuel selector valve was found positioned to the right fuel tank. The airframe fuel strainer bowl was removed and found to be full of liquid, which was consistent with 100 low-lead aviation fuel. No debris was noted. Additionally, the fuel screen was free of debris. Flight control continuity was established from the cockpit controls aft to the rudder and horizontal stabilator, and wing roots. The right wing was cut by recovery personnel and the left wing was thermally damaged. Both aileron bell cranks had control cables attached. The stabilator trim drum was found in a position consistent with slight nose up, or takeoff position. The recovered engine, a Lycoming IO-540-K1G5D, serial number L-15161-48A, remained intact and exhibited thermal damage throughout. The propeller governor, propeller, magneto, fuel pump, starter, alternator, and oil filter remained attached to the engine. The rocker box covers and all engine accessories were removed. All intake and exhaust rocker arms were intact. The engine crankshaft was rotated by hand using a hand tool attached to the propeller governor mounting pad. Rotational continuity was established throughout the engine and valve train. Thumb compression and suction was obtained on all six cylinders. The single drive dual magneto exhibited thermal damage, exposing the internal components. All of the internal components were in place, however, were fire damaged. The magneto drive shaft would not rotate by hand. Due to the fire and thermal damage sustained to the magneto assembly and engine, engine-to-magneto timing could not be determined. The top and bottom spark plugs were removed and examined. The electrodes were undamaged and exhibited normal coloration with the exception with the number 1, 2, and 3 bottom plugs, which were covered in oil. The propeller governor remained attached to the engine. The propeller governor linkage remained attached; however, the control arm appeared to be bent forward. No impact damage was noted surrounding the area of the control arm. The propeller governor screen was free of debris. For further information regarding the airframe and engine examination, see the NTSB Airframe and Engine Examination Summary Report within the public docket for this accident. Examination of the propeller was conducted at the facilities of McCauley Propeller Systems, Wichita, Kansas, by representatives of McCauley Propeller Systems and the NTSB IIC on November 20, 2014. The examination of the McCauleyB3D36C433-O/I-90VSA-1 three-bladed propeller revealed that the propeller had damage consistent with impact and mid-level rotational energy absorption. The propeller blades had leading edge impact damage, leading edge polishing, and chordwise gouges and paint scratches. The propeller exhibited no impact signature markings or component positions that would have indicated an angle disagreement between blades at impact. All three propeller blades exhibited indications of functioning in the normal operating range at impact. The exact blade angles at the time of impact were not determined. There was no evidence of any type of propeller failure or malfunction prior to the accident sequence. The Hartzell propeller governor, part number F-4-11B, was retained and subsequently functionally tested using a test bench. During the bench test, no anomalies were noted that would have precluded normal operation. ## Aircraft - Registration: [N4646F](https://openairdocs.org/deregistered/N4646F-2018-01-05), registration cancelled 2018-01-05, S/N 32R-7680471 (OpenAirDocs) - Reported make and model: PIPER PA 32R-300 (300) - Registry model: [Piper PA-32R-300](https://openairdocs.org/model/piper-pa-32r-300) (registry code 7103213) (OpenAirDocs) - Category: Airplane - Serial number: 32R-7680471 - Year built: 1976 - Airframe hours: 1721 - Engines: Lycoming IO-540-K1G5D reciprocating - Damage: Destroyed - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, July 27, 2013 - Departed: U42, West Jordan, UT - Destination: Boise, ID - Airport: U42, South Valley Rgnl, runway 16, 5,862 × 100 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 56; injuries: serious; private; airplane ratings: single-engine land; medical: class 3, unknown; seat: left; restraint: 3-point; flight hours: 243 total ## Weather - Conditions: Visual (VMC), Day - Wind: 160° at 4 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 73 °F, dew point 48 °F - Altimeter: 30.20 inHg - Observed at: KSLC, 11 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 20140810014769A](https://openairdocs.org/incident/20140810014769A), Aug 10, 2014: Piper PA-32R-300, Salt Lake City, UT, Destroyed. Aircraft departed runway 16 at South Valley Regional Airport (U42) at approximately 0901 local time. Aircraft impacted the ground at an approximate heading of… ## Docket (13 files) The files NTSB released with the investigation on June 12, 2015, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=89840. 9.3 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 4.9 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40427784&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - FAA Inspector Record of Conversation – Witnesses (item 2, .PDF, 983 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40427785&FileExtension=.PDF&FileName=FAA%20Inspector%20Record%20of%20Conversation%20%E2%80%93%20Witnesses-Redacted.PDF - Witness Statements (item 3, .PDF, 1.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40427786&FileExtension=.PDF&FileName=Witness%20Statements-Redacted.PDF - FAA Wreckage Diagram (item 4, .PDF, 165 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40427787&FileExtension=.PDF&FileName=FAA%20Wreckage%20Diagram-Master.PDF - McCauley Propeller Examination Report (item 5, .PDF, 52 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40427788&FileExtension=.PDF&FileName=McCauley%20Propeller%20Examination%20Report-Redacted.PDF - Propeller Governor Examination Report (item 6, .PDF, 964 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40427789&FileExtension=.PDF&FileName=Propeller%20Governor%20Examination%20Report-Redacted.PDF - Record of Conversation – Pilot (item 7, .PDF, 56 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40427790&FileExtension=.PDF&FileName=Record%20of%20Conversation%20%E2%80%93%20Pilot-Master.PDF - NTSB Airframe and Engine Examination Summary (item 8, .PDF, 72 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40427791&FileExtension=.PDF&FileName=NTSB%20Airframe%20and%20Engine%20Examination%20Summary-Master.PDF - Statement of Party Representatives to NTSB Investigation – Lycoming Engines (item 9, .PDF, 207 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40427792&FileExtension=.PDF&FileName=Statement%20of%20Party%20Representatives%20to%20NTSB%20Investigation%20%E2%80%93%20Lycoming%20Engines-Redacted.PDF - Statement of Party Representatives to NTSB Investigation – Piper Aircraft (item 10, .PDF, 145 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40427793&FileExtension=.PDF&FileName=Statement%20of%20Party%20Representatives%20to%20NTSB%20Investigation%20%E2%80%93%20Piper%20Aircraft-Redacted.PDF - Release of Aircraft Wreckage, NTSB Form 6120.15 (item 11, .PDF, 571 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40427794&FileExtension=.PDF&FileName=Release%20of%20Aircraft%20Wreckage,%20NTSB%20Form%206120.15-Redacted.PDF - Evidence Control Form (item 12, .PDF, 71 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40427795&FileExtension=.PDF&FileName=Evidence%20Control%20Form-Master.PDF - Evidence Control Form (item 13, .PDF, 71 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40427796&FileExtension=.PDF&FileName=Evidence%20Control%20Form-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.