# NTSB GAA19CA387: Piper PA32, N3556W, Seldovia, AK, July 7, 2019 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: July 6, 2019, 19:05 local (Jul 7, 2019, 03:05 UTC) - Place: Seldovia, AK - Coordinates: 59.443889, -151.705001 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=59.4439&lon=-151.7050&mi=10 - Phase of flight: [Takeoff](https://openairdocs.org/ntsb-phases/300) (OpenAirDocs' grouping) - Defining event: [Takeoff: Collision during takeoff/land](https://openairdocs.org/ntsb-events/490) - Highest injury: No injuries - Injuries: 5 uninjured - Status: Completed, report May 21, 2020 - Report: Approved by Office Director - NTSB office: General Aviation Accidents - Parties: FAA - NTSB case key (mKey): 99779 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=GAA19CA387 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/99779/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=99779 - Page: https://openairdocs.org/ntsb/GAA19CA387 ## Probable cause The pilot's failure to attain a sufficient climb following a short-field takeoff, which resulted in collision with trees. ## 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-32-260, 18 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=7103206), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Object/animal/substance: tree(s)](https://openairdocs.org/ntsb-findings/03022020): Environmental issues › Physical environment · Effect on operation (probable cause); cases with it: [Piper PA-32-260, 3 cases](https://openairdocs.org/ntsb-findings/03022020/cases.md?model=7103206), [All aircraft, 933 cases](https://openairdocs.org/ntsb-findings/03022020/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-32-260, 1 case](https://openairdocs.org/ntsb-findings/01062035/cases.md?model=7103206), [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. - [Takeoff: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Piper PA-32-260, 30 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=7103206), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) - [Takeoff: Collision during takeoff/land](https://openairdocs.org/ntsb-events/490) (defining event); cases with it: [Piper PA-32-260, 7 cases](https://openairdocs.org/ntsb-events/490/sequence.md?model=7103206), [All aircraft, 1,309 cases](https://openairdocs.org/ntsb-events/490/sequence.md) ## Analysis The pilot reported that the airplane's gross takeoff weight was 300 lbs less than the maximum allowable takeoff weight. He performed a short-field takeoff from the 1,800-ft-long gravel surface, and the initial climb continued as expected. However, the climb performance then degraded and became insufficient to clear 80-ft-tall trees located about 1,000 ft from the departure end of the runway. The airplane collided with treetops, descended, and subsequently impacted a lake and became submerged. The airplane sustained substantial damage to the stabilator. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. ## Factual narrative The pilot reported that the airplane's takeoff gross weight was 300 pounds less than the maximum. He performed a short-field takeoff from the 1,800ft gravel surface, and the initial climb continued as he expected. He recalled that the climb performance degraded and became insufficient to clear the 80ft tall trees located about 1,000ft from the departure end of the runway. The manufacturer's Pilot Operating Handbook (POH) stated that, short field takeoff's that require obstacle clearance will, after breaking ground accelerate to best angle of climb speed, 95 MPH and climb past obstacles. The airplane collided with treetops, descended and subsequently impacted the lake and became submerged. The airplane sustained substantial damage to the stabilator. Additionally, the POH denotes that the minimum runway distance required for the airplane to takeoff over a 50ft barrier was 1,360ft. According to the manufacturer, the minimum runway distance of 1,360ft represents a takeoff from a hard surface runway. Further, the POH specifies the use of a soft-field, obstacle clearance takeoff, as the increase flap setting of 25°, airspeed acceleration and pull nose gear off the ground as soon as possible and at the lowest possible airspeed. Accelerate just above the ground to best angle of climb speed, 95 MPH to climb past obstacle clearance height. Continue to climb while accelerating to best rate of climb, 105 MPH while slowly retracting flaps. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. ## Aircraft - Registration: [N3556W](https://openairdocs.org/deregistered/N3556W-2020-02-28), registration cancelled 2020-02-28, S/N 32-444, built 1966 (OpenAirDocs) - Reported make and model: Piper PA32 (260) - Registry model: [Piper PA-32-260](https://openairdocs.org/model/piper-pa-32-260) (registry code 7103206) (OpenAirDocs) - Registry engine: [Lycoming 0-540 series](https://openairdocs.org/engine/lycoming-0-540-series) (registry code 41532, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 32-444 - Year built: 1966 - Airframe hours: 6643.47 - Engines: Lycoming O-540-E4B5 260 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: 100 hour, July 1, 2019 - Departed: ASP, Seldovia, AK - Destination: AWS, Wasilla, AK - Airport: SOV, Seldovia, runway 34, 1,845 × 80 ft, gravel - Equipment: Handheld GPS, Stall warning system, Auto-pilot, Electronic flight bag or handheld device, Electronic multifunction display, Electronic primary flight display ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 54; injuries: none; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: basicmed; last flight review August 3, 2018; seat: left; restraint: 3-point; flight hours: 1,229 total, 671 in this make and model, 1,194 as pilot in command, 27 in the last 90 days, 10 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: calm - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 68 °F, dew point 55 °F - Altimeter: 30.22 inHg - Observed at: PASO ## 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 20190706009339A](https://openairdocs.org/incident/20190706009339A), Jul 6, 2019: Piper PA-32-260, Seldovia, AK, Substantial damage. Aircraft departed rwy 34 at Seldovia in very light wind conditions and heavy load, though within weight limitations of aircraft. Just after rotation, aircraft… ## Other investigations on N3556W (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 FTW67D0242](https://openairdocs.org/ntsb/FTW67D0242), Oct 2, 1966: Piper PA-32 (N3556W), Dallas, TX, substantial damage ## Docket (3 files) The files NTSB released with the investigation on December 5, 2019, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=99779. 4.2 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 3.7 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40478578&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Manufacturer -Pilot Operating Handbook Procedures (item 2, .PDF, 384 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40478580&FileExtension=.PDF&FileName=Manufacturer%20-Pilot%20Operating%20Handbook%20Procedures-Master.PDF - Photo (item 3, .PDF, 56 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40478583&FileExtension=.PDF&FileName=Photo-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.