# NTSB CHI06CA172: Piper PA-18-150, N82223, Minong, WI, June 26, 2006 - Type: NTSB accident investigation - Classification: Accident · Minor injuries · Data collection · Final report - Date: June 26, 2006, 11:00 local (16:00 UTC) - Place: Minong, WI - Coordinates: 46.10361, -91.903892 - Nearby events: https://openairdocs.org/map.md?lat=46.1036&lon=-91.9039&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Highest injury: Minor injuries - Injuries: 2 minor - Status: Completed, report October 3, 2006 - Report: Approved by Office Director - Parties: FAA-Minneapolis FSDO - NTSB case key (mKey): 64192 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CHI06CA172 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/64192/pdf - Page: https://openairdocs.org/ntsb/CHI06CA172 ## Probable cause Restriction of the elevator control system due to the camera placed in the seat back pocket and the inadvertent stall/mush condition encountered during the go-around. The trees impacted after the stall were a contributing factor. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - In flight collision with object, go-around (vfr) - stall/mush - inadvertent, pilot in command (cause) - flt control syst,elevator control - restricted (cause) - object - tree(s) (contributing factor) - In flight collision with terrain/water, descent - uncontrolled - terrain condition - ground ## Analysis The airplane was substantially damaged when it impacted trees and terrain during a go-around. The pilot and passenger reported minor injuries. The pilot stated that he entered the traffic pattern at the intended destination. He noted that on final approach he applied full flaps and the approach appeared "OK." However, as the airplane crossed the runway threshold, the pilot thought that the airspeed was "a bit fast" and he elected to execute a go-around. He applied full throttle and raised the flaps one notch. He stated, "The stick felt jammed. I could not get the stick forward enough to lower the nose to accelerate." The airplane remained in a nose high climb attitude. The pilot stated that the airspeed decayed until he felt a pre-stall buffet. He noted, "I felt trees to my right . . . would be better than the highway to land on as we were stalling and were going to drop. We mushed into the trees and came down to [the] ground." The pilot reported that before the flight he had placed a digital camera in the front seat back pocket. He stated that the before takeoff flight control check was normal and that the initial takeoff on the accident flight was without incident. A post accident inspection revealed no anomalies with the flight control system. The inspection also revealed that forward travel of the rear seat control stick was restricted when it came in contact with an object the size of the digital camera placed in the seat back pocket. ## Factual narrative The airplane was substantially damaged when it impacted trees and terrain during a go-around. The pilot and passenger reported minor injuries. The pilot stated that he entered the traffic pattern at the intended destination. He noted that on final approach he applied full flaps and the approach appeared "OK." However, as the airplane crossed the runway threshold, the pilot thought that the airspeed was "a bit fast" and he elected to execute a go-around. He applied full throttle and raised the flaps one notch. He stated, "The stick felt jammed. I could not get the stick forward enough to lower the nose to accelerate." The airplane remained in a nose high climb attitude. The pilot stated that the airspeed decayed until he felt a pre-stall buffet. He noted, "I felt trees to my right . . . would be better than the highway to land on as we were stalling and were going to drop. We mushed into the trees and came down to [the] ground." The pilot reported that before the flight he had placed a digital camera in the front seat back pocket. He stated that the before takeoff flight control check was normal and that the initial takeoff on the accident flight was without incident. A post accident inspection revealed no anomalies with the flight control system. The inspection also revealed that forward travel of the rear seat control stick was restricted when it came in contact with an object the size of the digital camera placed in the seat back pocket. ## Aircraft - Registration: N82223 (not matched to a registry record) - Reported make and model: Piper PA-18-150 - Category: Airplane - Serial number: 18-7909071 - Airframe hours: 480 - Engines: Lycoming O-320 reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Thomas A Holdeman - Registered owner: Arthur McKinley LC - Airworthiness certificate: Standard, Utility; Standard, Normal - Last inspection: Annual, July 1, 2005 - Departed: HYR, Hayward, WI - Destination: Miinong, WI - Airport: HYR, Hayward Muni, runway 36, 2,076 × 100 ft, grass/turf ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 46; injuries: minor; commercial; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 2, with waivers/limitations; last flight review March 1, 2006; seat: front; flight hours: 972 total, 180 in this make and model, 948 as pilot in command, 15 in the last 90 days, 8 in the last 30 days, 3 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: calm - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 79 °F, dew point 45 °F - Altimeter: 30.12 inHg - Observed at: HYR, 30 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 20060626014029A](https://openairdocs.org/incident/20060626014029A), Jun 26, 2006: Piper PA18150, Minong, WI, Substantial damage. (-23) On final approach to Minong, WI, the pilot decided he was out of position and initiated a go around. Pilot stated he applied power and pulled the nose… 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.