# NTSB CEN14CA049: Mooney M20R, N1006A, Fort Collins, CO, November 7, 2013 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: November 7, 2013, 11:25 local (18:25 UTC) - Place: Fort Collins, CO - Coordinates: 40.451667, -105.011108 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=40.4517&lon=-105.0111&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-flare/touchdown: Hard landing](https://openairdocs.org/ntsb-events/092) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report February 4, 2014 - Report: Approved by Office Director - NTSB office: Central Region - NTSB case key (mKey): 88416 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN14CA049 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/88416/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=88416 - Page: https://openairdocs.org/ntsb/CEN14CA049 ## Probable cause The pilot did not maintain control of the airplane during the go around. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Performance/control parameters](https://openairdocs.org/ntsb-findings/01062000): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Mooney M20R, 2 cases](https://openairdocs.org/ntsb-findings/01062000/cases.md?model=5870225), [All aircraft, 1,269 cases](https://openairdocs.org/ntsb-findings/01062000/cases.md) - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Mooney M20R, 9 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=5870225), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing-flare/touchdown: Hard landing](https://openairdocs.org/ntsb-events/092) (defining event); cases with it: [Mooney M20R, 3 cases](https://openairdocs.org/ntsb-events/092/sequence.md?model=5870225), [All aircraft, 2,102 cases](https://openairdocs.org/ntsb-events/092/sequence.md) - [Landing-flare/touchdown: Loss of control in flight](https://openairdocs.org/ntsb-events/240); cases with it: [Mooney M20R, 7 cases](https://openairdocs.org/ntsb-events/240/sequence.md?model=5870225), [All aircraft, 5,002 cases](https://openairdocs.org/ntsb-events/240/sequence.md) ## Analysis The pilot was in the traffic pattern for runway 33; planning a full-stop landing. During the landing flare, the airplane touched down and then lifted off of the runway. The pilot maintained that the airplane did not bounce, but rather touched down "very lightly." The pilot added power in order to recover; however, he did not receive the response he was anticipating. Subsequently, the pilot added full power and prepared to go around. Again, the engine did not respond as the pilot had anticipated. The nose of the airplane pitched up and the airplane drifted to the left. The airplane bounced several times before coming to a stop. The wings, fuselage, and firewall were substantially damaged. An examination of the engine and related systems revealed no anomalies. ## Factual narrative The pilot was in the traffic pattern for runway 33; planning a full-stop landing. During the landing flare, the airplane touched down and then lifted off of the runway. The pilot maintained that the airplane did not bounce, but rather touched down "very lightly." The pilot added power in order to recover; however, he did not receive the response he was anticipating. Subsequently, the pilot added full power and prepared to go around. Again, the engine did not respond as the pilot had anticipated. The nose of the airplane pitched up and the airplane drifted to the left. The airplane bounced several times before coming to a stop. The wings, fuselage, and firewall were substantially damaged. An examination of the engine and related systems revealed no anomalies. ## Aircraft - Registration: [N1006A](https://openairdocs.org/aircraft/N1006A), registered now, S/N 29-0284, built 2002 (OpenAirDocs) - Reported make and model: MOONEY M20R (NO SERIES) - Registry model: [Mooney M20R](https://openairdocs.org/model/mooney-m20r) (registry code 5870225) (OpenAirDocs) - Registry engine: [Continental IO-550 series](https://openairdocs.org/engine/continental-io-550-series) (registry code 17042, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 29-0284 - Year built: 2002 - Airframe hours: 1035 - Engines: CONT MOTOR IO-550 280 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Cooper Properties, Inc - Registered owner: Cooper Properties, Inc - Airworthiness certificate: Standard, Normal - Last inspection: Annual, May 1, 2013 - Departed: KBJC, Denver, CO - Destination: KFNL, Fort Collins, CO - Airport: KFNL, Fort Collins-Loveland Municipa, runway 33, 8,500 × 100 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 42; injuries: none; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 3, without waivers/limitations; last flight review June 4, 2013; seat: left; flight hours: 196.5 total, 44.5 in this make and model, 196.5 as pilot in command, 43.5 in the last 90 days ## Weather - Conditions: Visual (VMC), Day - Wind: 350° at 3 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 46 °F, dew point 25 °F - Altimeter: 30.35 inHg - Observed at: KFNL ## 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 20131107021529A](https://openairdocs.org/incident/20131107021529A), Nov 7, 2013: Mooney M20R, Loveland, CO, Substantial damage. On Thursday, November 7, 2013, at approximately 11:25 am MST, a Mooney, M20R, registered as N1006A, recieved substantial damage when the aircraft impacted… ## Docket (1 files) The files NTSB released with the investigation on January 27, 2014, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=88416. 812 KB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 812 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40408400&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.