# NTSB GAA16CA012: Piper PA 46-350P, N945S, Kanab, UT, October 11, 2015 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: October 11, 2015, 10:30 local (16:30 UTC) - Place: Kanab, UT - Coordinates: 37.010276, -112.529724 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=37.0103&lon=-112.5297&mi=10 - Phase of flight: [Standing](https://openairdocs.org/ntsb-phases/150) (OpenAirDocs' grouping) - Defining event: [Standing-engine(s) operating: Airport occurrence](https://openairdocs.org/ntsb-events/070) - Highest injury: No injuries - Injuries: 4 uninjured - Status: Completed, report December 3, 2015 - Report: Approved by Office Director - NTSB office: General Aviation Accidents - Parties: Federal Aviation Administration - NTSB case key (mKey): 92168 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=GAA16CA012 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/92168/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=92168 - Page: https://openairdocs.org/ntsb/GAA16CA012 ## Probable cause The pilot's failure to monitor the airplane's movement on the ground while programming the GPS, which resulted in a collision with a pole. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Attention/monitoring: task monitoring/vigilance](https://openairdocs.org/ntsb-findings/02021520): Personnel issues › Psychological · Pilot (probable cause); cases with it: [Piper PA 46-350P, 3 cases](https://openairdocs.org/ntsb-findings/02021520/cases.md?model=7104620), [All aircraft, 330 cases](https://openairdocs.org/ntsb-findings/02021520/cases.md) - [Towing and taxiing: taxiing](https://openairdocs.org/ntsb-findings/01010920): Aircraft › Aircraft handling/service · Incorrect use/operation (probable cause); cases with it: [Piper PA 46-350P, 1 case](https://openairdocs.org/ntsb-findings/01010920/cases.md?model=7104620), [All aircraft, 27 cases](https://openairdocs.org/ntsb-findings/01010920/cases.md) - [Object/animal/substance: pole](https://openairdocs.org/ntsb-findings/03022010): Environmental issues › Physical environment · Effect on equipment; cases with it: [Piper PA 46-350P, 1 case](https://openairdocs.org/ntsb-findings/03022010/cases.md?model=7104620), [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. - [Standing-engine(s) operating: Airport occurrence](https://openairdocs.org/ntsb-events/070) (defining event); cases with it: [Piper PA 46-350P, 2 cases](https://openairdocs.org/ntsb-events/070/sequence.md?model=7104620), [All aircraft, 57 cases](https://openairdocs.org/ntsb-events/070/sequence.md) - [Standing-engine(s) operating: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Piper PA 46-350P, 40 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=7104620), [All aircraft, 10,154 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The pilot reported that after he had started the airplane's engine, he noticed an error in the route programmed in the global positioning system (GPS). The pilot reported the airplane had begun to roll forward as he made changes to the GPS programming and he was not aware the airplane was moving. The airplane collided with a steel pole and sustained substantial damage to fuselage and wing. The pilot reported no preimpact mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation. ## Factual narrative The pilot reported that after he had started the airplane's engine, he noticed an error in the route programmed in the global positioning system (GPS). The pilot reported the airplane had begun to roll forward as he made changes to the GPS programming and he was not aware the airplane was moving. The airplane collided with a steel pole and sustained substantial damage to fuselage and wing. The pilot reported no preimpact mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation. ## Aircraft - Registration: [N945S](https://openairdocs.org/deregistered/N945S-2023-04-23), registration cancelled 2023-04-23, S/N 4636495, built 2011 (OpenAirDocs) - Reported make and model: PIPER PA 46-350P - Registry model: [Piper PA 46-350P](https://openairdocs.org/model/piper-pa-46-350p) (registry code 7104620) (OpenAirDocs) - Registry engine: [Lycoming TIO-540-AE2A](https://openairdocs.org/engine/lycoming-tio-540-ae2a) (registry code 41999, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 4636495 - Year built: 2011 - Airframe hours: 637 - Engines: LYCOMING TIO-540-AE2A 350 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Scepter Inc - Registered owner: Scepter Inc - Airworthiness certificate: Standard, Normal - Last inspection: Annual, April 18, 2015 - Departed: KNB, Kanab, UT - Destination: 1G4, PEACH SPRINGS, AZ - Airport: KNB, Kanab Muni - Equipment: Electronic flight bag or handheld device, Electronic multifunction display, Electronic primary flight display, Onboard weather, Satellite tracking device, Stall warning system, Auto-pilot, Data recorder ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 79; injuries: none; private, commercial; airplane ratings: single-engine land, single-engine sea; instrument ratings: airplane; medical: class 2, with waivers/limitations; last flight review January 9, 2015; seat: left; restraint: 3-point; flight hours: 6,376 total, 2,581 in this make and model, 6,156 as pilot in command, 27 in the last 90 days, 17 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: calm - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 72 °F, dew point 46 °F - Altimeter: 30.26 inHg - Observed at: KAZC, 23 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 20151011017369A](https://openairdocs.org/incident/20151011017369A), Oct 11, 2015: Piper PA 46-350P, Kanab, UT, Substantial damage. Pilot was making changes to pre-loaded flight plan in GPS while taxiing for departure and was not aware that he departed the taxiway where he struck a pole… ## Docket (2 files) The files NTSB released with the investigation on November 23, 2015, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=92168. 4.7 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 4.4 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40434187&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Photos (Courtesy of FAA) (item 2, .PDF, 2 photos, 326 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40434188&FileExtension=.PDF&FileName=Photos%20(Courtesy%20of%20FAA)-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.