# NTSB GAA17CA072: Piper PA 28R, N9466K, Payallup, WA, November 11, 2016 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: November 11, 2016, 12:30 local (20:30 UTC) - Place: Payallup, WA - Coordinates: 47.103889, -122.287223 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=47.1039&lon=-122.2872&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Defining event: [Approach: Controlled flight into terr/obj (CFIT)](https://openairdocs.org/ntsb-events/120) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report July 5, 2017 - Report: Approved by Office Director - NTSB office: General Aviation Accidents - Parties: FAA - NTSB case key (mKey): 94391 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=GAA17CA072 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/94391/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=94391 - Page: https://openairdocs.org/ntsb/GAA17CA072 ## Probable cause The airport’s failure to issue a NOTAM regarding the deployment of the traffic monitoring camera system before the accident, which resulted in the airplane striking the camera system during a short-field approach and landing. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Policy/procedure: adequacy of policy/proc](https://openairdocs.org/ntsb-findings/04021015): Organizational issues › Management · Airport (probable cause); cases with it: [Piper PA-28R-200, 1 case](https://openairdocs.org/ntsb-findings/04021015/cases.md?model=7102811), [All aircraft, 106 cases](https://openairdocs.org/ntsb-findings/04021015/cases.md) - [Object/animal/substance: ground equipment](https://openairdocs.org/ntsb-findings/03022050): Environmental issues › Physical environment · Effect on equipment (probable cause); cases with it: [Piper PA-28R-200, 1 case](https://openairdocs.org/ntsb-findings/03022050/cases.md?model=7102811), [All aircraft, 52 cases](https://openairdocs.org/ntsb-findings/03022050/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Approach: Controlled flight into terr/obj (CFIT)](https://openairdocs.org/ntsb-events/120) (defining event); cases with it: [Piper PA-28R-200, 5 cases](https://openairdocs.org/ntsb-events/120/sequence.md?model=7102811), [All aircraft, 1,074 cases](https://openairdocs.org/ntsb-events/120/sequence.md) - [Landing-flare/touchdown: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Piper PA-28R-200, 45 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=7102811), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis According to the pilot under examination, he was to accomplish a short-field landing to the runway 17 numbers during his single-engine airplane flight instructor practical examination. He reported that, during the transition from final to the flare, the bottom of the fuselage struck an aircraft traffic monitoring camera system. The camera system was located about 125 ft north of the runway 17 threshold and was about 8 inches high. After striking the camera, the pilot added power and landed the airplane on the runway 17 numbers. There were no NOTAMs regarding the use of the aircraft traffic monitoring camera system issued at the time of the accident. However, the next day, the airport manager issued a NOTAM regarding the deployment of the camera system. The airplane sustained substantial damage to the right wing spar. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation. ## Factual narrative According to the pilot under examination, he was to accomplish a short field landing to the runway 17 numbers, during his single engine airplane flight instructor practical examination. He reported that during the transition from final to the flare, the bottom of the fuselage struck an aircraft traffic monitoring camera system. The camera system was located about 125 ft. north of the runway 17 threshold, and stood about 8 inches in height. After striking the camera, the pilot added power and landed the airplane on the runway 17 numbers. There were no NOTAM's regarding the use of the aircraft traffic monitoring system issued at the time of the accident. However, the next day a NOTAM regarding the deployment of the camera system was issued by the airport manager. The airplane sustained substantial damage to the right wing spar. The pilot reported that there were no pre-accident mechanical malfunctions or failures with the airplane that would have precluded normal operation. ## Aircraft - Registration: [N9466K](https://openairdocs.org/aircraft/N9466K), registered now, S/N 28R-7635244, built 1976 (OpenAirDocs) - Reported make and model: PIPER PA 28R (200) - Registry model: [Piper PA-28R-200](https://openairdocs.org/model/piper-pa-28r-200) (registry code 7102811) (OpenAirDocs) - Registry engine: [Lycoming I0360 series](https://openairdocs.org/engine/lycoming-i0360-series) (registry code 41515, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 28R-7635244 - Year built: 1976 - Airframe hours: 8457.9 - Engines: LYCOMING IO-360 200 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Spanaflight LLC - Registered owner: Spanaflight LLC - Airworthiness certificate: Standard, Normal - Last inspection: Annual, November 4, 2016 - Departed: KPLU, Puyallup, WA - Destination: KPLU, Puyallup, WA - Airport: PLU, Pierce County - Thun Field, runway 17, 3,650 × 60 ft, asphalt - Equipment: Stall warning system ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 34; injuries: none; commercial; airplane ratings: single-engine sea, single-engine land; instrument ratings: airplane; medical: class 2, with waivers/limitations; last flight review June 9, 2016; seat: right; restraint: 3-point; flight hours: 470 total, 37 in this make and model, 427 as pilot in command, 18 in the last 90 days, 8 in the last 30 days, 2 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: calm - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 59 °F, dew point 55 °F - Altimeter: 29.90 inHg - Observed at: PLU ## 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 20161111021319A](https://openairdocs.org/incident/20161111021319A), Nov 11, 2016: Piper PA-28R-200, Puyallup, WA, Substantial damage. Applicant demonstrating shortfield approach and landing to runway 17 during practical test. The aircraft was low on short final and the right main gear struck… ## Other investigations on N9466K (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 SEA02LA016](https://openairdocs.org/ntsb/SEA02LA016), Nov 10, 2001: Piper PA-28R-200 (N9466K), Puyallup, WA, substantial damage. Probable cause: The pilots' failure to maintain aircraft control on short final, resulting in a touchdown off of the prepared landing surface. A factor was grassy terrain encountered on the landing rollout. ## Docket (2 files) The files NTSB released with the investigation on June 14, 2017, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=94391. 3.9 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=40453110&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Photos (Courtesy of FAA) (item 2, .PDF, 3 photos, 226 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40453111&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.