# NTSB WPR20FA079: Piper PA28, N3672K, Payson, AZ, January 24, 2020 - Type: NTSB accident investigation - Classification: Accident · Fatal · Class 3 · Field · Final report - Date: January 24, 2020, 09:11 local (16:11 UTC) - Place: Payson, AZ - Coordinates: 34.158889, -111.493888 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=34.1589&lon=-111.4939&mi=10 - Phase of flight: [Maneuvering](https://openairdocs.org/ntsb-phases/450) (OpenAirDocs' grouping) - Defining event: [Maneuvering: Loss of control in flight](https://openairdocs.org/ntsb-events/240) - Highest injury: Fatal - Injuries: 1 fatal, 2 serious - Status: Completed - Report: Approved by Office Director - Investigation class: Class 3 - NTSB office: Western Pacific Region - Parties: Piper Aircraft, Lycoming Engines, FAA-FSDO - NTSB case key (mKey): 100858 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR20FA079 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/100858/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=100858 - Page: https://openairdocs.org/ntsb/WPR20FA079 ## Probable cause The pilot's decision to fly into a canyon with rising terrain, and his subsequent loss of aircraft control while maneuvering away from rising terrain. ## 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-28-140, 43 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md?model=7102802), [All aircraft, 3,098 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md) - [Terrain: mountainous/hilly terrain](https://openairdocs.org/ntsb-findings/03021010): Environmental issues › Physical environment · Effect on equipment (probable cause); cases with it: [Piper PA-28-140, 5 cases](https://openairdocs.org/ntsb-findings/03021010/cases.md?model=7102802), [All aircraft, 329 cases](https://openairdocs.org/ntsb-findings/03021010/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-28-140, 103 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=7102802), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Maneuvering: Loss of control in flight](https://openairdocs.org/ntsb-events/240) (defining event); cases with it: [Piper PA-28-140, 44 cases](https://openairdocs.org/ntsb-events/240/sequence.md?model=7102802), [All aircraft, 5,002 cases](https://openairdocs.org/ntsb-events/240/sequence.md) ## Analysis The pilot and passengers decided to fly over the nearby mountains so the passengers could spot wildlife on the terrain below. The pilot and surviving passenger recalled the airplane running well as they made a turn towards the mountains, but neither reported any memories of the flight after that point. Radar flight track data showed the airplane depart and fly to the mountains while maintaining an altitude of about 1,000 ft above ground level. The airplane completed a turning maneuver and descended into a canyon. Near the accident site, the flight track was consistent with the pilot maneuvering to avoid rising terrain. The accident site debris field was in a down-canyon direction. Examination of the wreckage and the accident site revealed that the airplane was in a nose-high attitude at the time of impact and possibly nearing the stall speed of the airplane. The propeller damage suggests that the engine was producing power at the time of impact. The examination of the wreckage revealed no anomalies with the airframe or engine that would have precluded normal operation. ## Factual narrative On January 24, 2020, about 0911 mountain standard time, a Piper PA28-140, airplane, N3672K, was destroyed when it was involved in an accident near Payson, Arizona. One of the two passengers was fatally injured, and the pilot and other passenger were seriously injured. The airplane was operated by the pilot as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot stated in an interview that after a flight earlier that morning from Falcon Field Airport (FFZ), Mesa, Arizona, he landed in PAN, refueled, and departed for the return flight back to FFZ. During the return flight, the pilot decided to fly over the mountains southwest of their position. He stated that he flew about 1,000 ft above ground level (agl) over the mountains, while the passengers were spotting wildlife on the terrain below. The pilot stated the airplane was running well and that he didn’t remember anything else about the flight until 5 hours later, when he woke up injured, laying in a small creek at the accident site. Radar flight track data showed the airplane depart PAN and fly to the Mazatzal Mountain Range. While maintaining an altitude of about 1,000 ft agl above the mountainous terrain, the airplane made a 280° turning maneuver, then descended over and into a canyon with rising terrain. (see Figure 1). About a half mile from the accident site, the flight track showed the airplane turn left and the turn radius increased before the track data stopped. The airplane’s groundspeed through the canyon decreased from 88 to 65 knots and the airplane’s altitude above the ground decreased from about 1,000 ft to 330 ft agl near the accident site. The terrain elevation rose about 800 ft up the canyon. The last recorded flight track data point was located about 500 ft from the accident site. Figure 1-Flight track data and accident site location The Gila County Regional Medical Examiner’s Office, Reno Nevada, performed an autopsy on the passenger. The cause of death was noted as multiple blunt force trauma. Toxicology testing on the passenger’s specimens indicated carbon monoxide levels less than 10% saturation. Examination of the accident site revealed the airplane was destroyed by impact forces, on steep, heavy brush covered terrain. The wreckage, including all major structural airplane components and primary flight controls, were contained within the debris path that was about 145 ft long and oriented on a magnetic heading of about 35°, paralleling and uphill from a small stream. (see Figure 2) Figure 2-Accident site aerial view. The outboard right-wing sections revealed leading-edge circular impact damage, similar in size to the large trees near the beginning of the debris path. The circular impact damage was found on the lower forward side of the wing near the leading edge, consistent with the airplane positioned in a nose up attitude at the time of impact with the ground. The propeller was found about halfway through the debris field and the blades revealedleading edge gouging and loss of blade material at the tips. The main wreckage, including the engine were found on top of the rocks located along the stream. The cabin and forward fuselage were mostly consumed by postimpact fire. The left wing and empennage were found partially attached to the main wreckage and had postimpact fire damage. The wreckage was recovered to a secure facility for further examination. Flight control cable continuity was attained through multiple overload fractures. The exhaust muff was disassembled and examined, and no anomalies were noted. The examination revealed no anomalies with the airframe or engine that would have precluded normal operation. ## Aircraft - Registration: [N3672K](https://openairdocs.org/aircraft/N3672K), registered now, S/N 28-23682, built 1967 (OpenAirDocs) - Reported make and model: Piper PA28 (140) - Registry model: [Piper PA-28-140](https://openairdocs.org/model/piper-pa-28-140) (registry code 7102802) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 28-23682 - Year built: 1967 - Airframe hours: 1194 - Engines: Lycoming O-320 SERIES reciprocating - Damage: Destroyed - Fire: On-Ground - Flight: Personal, Part 91 - Operator: Colton T Egbert - Registered owner: Colton T Egbert - Airworthiness certificate: Standard, Utility; Standard, Normal - Last inspection: 100 hour, March 1, 2019 - Departed: PAN, Payson, AZ - Destination: FFZ, Mesa, AZ - Equipment: Unknown ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 21; injuries: serious; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 1, with waivers/limitations; last flight review November 15, 2019; seat: left; restraint: 3-point; flight hours: 117 total, 44 in this make and model, 89 as pilot in command, 44 in the last 90 days ## Weather - Conditions: Visual (VMC), Day - Wind: calm - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 45 °F, dew point 25 °F - Altimeter: 30.13 inHg - Observed at: KPAN, 10 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 20200124001769A](https://openairdocs.org/incident/20200124001769A), Jan 24, 2020: Piper PA-28-140, Payson, AZ, Destroyed, 1 fatal. PIC moved from reno, NV to mesa, AZ 18 days prior to accident 0900 On the accident day, refueled acft with 30 gallons of 100LL and departed pan direct to ffz.… ## Docket (12 files) The files NTSB released with the investigation on December 15, 2021, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=100858. 53.7 MB in all. - Pilot/operator aircraft accident report, NTSB form 6120.1 (item 1, PDF, 11 pages, 4.7 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=12997707&FileExtension=pdf&FileName=6120%20for%20AS_Redacted-Rel.pdf - Pilot and passenger statements (item 2, PDF, 2 pages, 965 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13012298&FileExtension=pdf&FileName=Pilot%20and%20Passenger%20Statement%202-20-2020-Rel.pdf - Googleearth view of the radar track (item 3, PDF, 1 page, 14.5 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=12992640&FileExtension=pdf&FileName=Radar%20Track%20GoogleEarth%20View-Rel.pdf - Radar data (item 4, PDF, 4 pages, 58 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13000433&FileExtension=pdf&FileName=N3672K%20-%20OV%20Track%20Data-Rel.pdf - NTSB accident site examination summary (item 5, PDF, 11 pages, 9 photos, 2.7 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9738549&FileExtension=pdf&FileName=WPR20FA079%20Accident%20Site%20Examination%20Summary-Rel.pdf - Ntsb-engine examination summary (item 6, PDF, 5 pages, 826 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13002682&FileExtension=pdf&FileName=WPR20FA079%20Engine%20Examination%20Summary-Rel.pdf - Piper off-site examination notes (item 7, PDF, 2 pages, 80 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9737514&FileExtension=pdf&FileName=Piper%20Off-Site%20Exam%20Notes-Rel.pdf - Logbook excerpt-last annual inspection (item 8, PDF, 1 page, 25.8 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9738872&FileExtension=pdf&FileName=Last%20Annual%20and%20ELT%20Logbook%20Entry_Redacted-Rel.pdf - Statement of party representatives to NTSB investigation-piper aircraft (item 9, PDF, 1 page, 509 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9739647&FileExtension=pdf&FileName=Piper%20Party%20Form-redacted-Rel.pdf - Statement of party representatives to NTSB investigation-lycoming engines (item 10, PDF, 1 page, 544 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9740720&FileExtension=pdf&FileName=Lycoming%20Party%20Form-redacted-Rel.pdf - Toxicology report-passenger (item 11, PDF, 4 pages, 163 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13000900&FileExtension=pdf&FileName=Toxicology%20Report_Redacted-Rel.pdf - Release of aircraft wreckage, NTSB form 6120.15 (item 12, PDF, 1 page, 2.8 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9742806&FileExtension=pdf&FileName=Wreckage%20Release_Redacted-Rel.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.