# NTSB CEN11CA290: Cessna 182H, N8364S, Park Falls, WI, April 14, 2011 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: April 14, 2011, 13:00 local (18:00 UTC) - Place: Park Falls, WI - Coordinates: 45.955001, -90.424163 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=45.9550&lon=-90.4242&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Defining event: [Approach-VFR go-around: Loss of control in flight](https://openairdocs.org/ntsb-events/240) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report July 12, 2011 - Report: Approved by Office Director - NTSB office: Central Region - Parties: Federal Aviation Administration - NTSB case key (mKey): 78889 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN11CA290 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/78889/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=78889 - Page: https://openairdocs.org/ntsb/CEN11CA290 ## Probable cause The student pilot's failure to maintain aircraft control during an aborted landing. ## 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 · Student/instructed pilot (probable cause); cases with it: [Cessna 182H, 12 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2072718), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Performance/control parameters](https://openairdocs.org/ntsb-findings/01062000): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cessna 182H, 3 cases](https://openairdocs.org/ntsb-findings/01062000/cases.md?model=2072718), [All aircraft, 1,269 cases](https://openairdocs.org/ntsb-findings/01062000/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Approach-VFR go-around: Loss of control in flight](https://openairdocs.org/ntsb-events/240) (defining event); cases with it: [Cessna 182H, 8 cases](https://openairdocs.org/ntsb-events/240/sequence.md?model=2072718), [All aircraft, 5,002 cases](https://openairdocs.org/ntsb-events/240/sequence.md) - [Approach-VFR go-around: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Cessna 182H, 13 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=2072718), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis While on final approach to the runway, the airplane encountered unexpected wind, and the student pilot decided to abort the landing. He then applied full throttle and increased pitch. During the attempted aborted landing, a right quartering tailwind blew the airplane off the runway area, and the left wing and nose wheel contacted the terrain. The airplane came to rest upright adjacent to the runway and sustained substantial damage to the engine firewall and both wings. The student pilot stated there were no anomalies with the airframe or engine. He recommended that the accident could have been prevented if he maintained sufficient airspeed during final approach. ## Factual narrative While on final approach to the runway, the airplane encountered unexpected winds, and the student pilot decided to abort the landing. He then applied full throttle and increased pitch. During the attempted aborted landing, a right quartering tailwind "blew the airplane off the runway area", and the left wing and nose wheel contacted the terrain. The airplane came to rest upright adjacent to the runway and sustained substantial damage to the engine firewall and both wings. The student pilot stated there were no anomalies with the airframe or engine. He recommended that the accident could have been prevented if he maintained sufficient airspeed during final approach. ## Aircraft - Registration: [N8364S](https://openairdocs.org/deregistered/N8364S-2013-09-17), registration cancelled 2013-09-17, S/N 18256464, built 1965 (OpenAirDocs) - Reported make and model: CESSNA 182H - Registry model: [Cessna 182H](https://openairdocs.org/model/cessna-182h) (registry code 2072718) (OpenAirDocs) - Registry engine: [Continental O-470 series](https://openairdocs.org/engine/continental-o-470-series) (registry code 17026, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 18256464 - Airframe hours: 3282 - Engines: CONT MOTOR O-470-R 230 horsepower reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, August 6, 2010 - Departed: RPD, Rice Lake, WI - Destination: PKF, Park Falls, WI - Airport: PKF, Park Falls Municipal Airport, runway 36, 3,200 × 60 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Student pilot; age 59; injuries: none; student; medical: class 3, with waivers/limitations; seat: left; flight hours: 41 total, 39 in this make and model ## Weather - Conditions: Visual (VMC), Day - Visibility: 10 statute miles - Lowest ceiling: none ## 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 20110414006009A](https://openairdocs.org/incident/20110414006009A), Apr 14, 2011: Cessna 182H, Park Falls, WI, Substantial damage. Upon approach to landing at Park Falls Municipal Airport (pkf) the student pilot was caught by the winds and lost control of the airplane and crashed to the… ## Docket (1 files) The files NTSB released with the investigation on May 9, 2011, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=78889. 522 KB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 522 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40347192&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.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.