# NTSB WPR09CA370: Christopher Vans RV-4, N202CL, Wendover, UT, July 10, 2009 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: July 10, 2009, 13:25 local (19:25 UTC) - Place: Wendover, UT - Coordinates: 40.717777, -114.025276 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=40.7178&lon=-114.0253&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-flare/touchdown: Abnormal runway contact](https://openairdocs.org/ntsb-events/090) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report October 19, 2009 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: Federal Aviation Administration - NTSB case key (mKey): 74376 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR09CA370 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/74376/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=74376 - Page: https://openairdocs.org/ntsb/WPR09CA370 ## Probable cause The pilot's inadequate flare during touchdown and failure to maintain directional control, which resulted in a ground loop. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Performance/control parameters: landing flare](https://openairdocs.org/ntsb-findings/01062041): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [All aircraft, 1,285 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md) - [Performance/control parameters: directional control](https://openairdocs.org/ntsb-findings/01062020): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [All aircraft, 3,958 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md) - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [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: Abnormal runway contact](https://openairdocs.org/ntsb-events/090) (defining event); cases with it: [All aircraft, 1,506 cases](https://openairdocs.org/ntsb-events/090/sequence.md) - [Landing-flare/touchdown: Loss of control on ground](https://openairdocs.org/ntsb-events/230); cases with it: [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md) ## Analysis As the pilot maneuvered the airplane into a flare, its tail wheel touched down on the runway surface. The pilot applied full power in an effort to abort the landing. The resulting torque from the power increase led to the airplane's nose veering to the left. The airplane ground looped to the left leaving the runway surface. The wings both impacted the ground and the airplane nosed over. The pilot reported no preimpact mechanical malfunctions or failures with the airframe or engine. ## Factual narrative In a written statement, the pilot reported that he configured the airplane for landing and continued on a stabilized approach to the destination runway. As he maneuvered the airplane into a flare, the tail wheel touched down on the runway surface. The pilot applied full power in an effort to abort the landing. The resulting torque from the power increase led to the airplane's nose veering to the left. The airplane ground looped to the left leaving the runway surface. The wings both impacted the ground and the airplane nosed over. As a result of the impact, the airplane sustained damage to the wings. In the pilot's written submission to the Safety Board (NTSB Form 6120.1; Pilot/Operator Aircraft Accident/Incident Report), in the section titled RECOMMENDATION (How could this accident/incident have been prevented), the pilot stated that he needed "more practice." The pilot reported no preimpact mechanical malfunctions or failures with the airframe or engine. ## Aircraft - Registration: N202CL (not matched to a registry record) - Reported make and model: CHRISTOPHER VANS RV-4 - Category: Airplane, amateur-built - Serial number: 4490 - Airframe hours: 120 - Engines: LYCOMING O-320-E2A 150 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Scott Stewart - Registered owner: Ryan Christopher C - Airworthiness certificate: Special, Experimental (Special) - Last inspection: Annual, July 1, 2008 - Departed: Ogden, UT - Destination: ENV, Wendover, UT - Airport: ENV, Wendover Airport, runway 08, 6,000 × 150 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 54; injuries: none; private; airplane ratings: single-engine land; medical: class 3, with waivers/limitations; seat: front; flight hours: 502 total, 170 in this make and model, 6 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: 110° at 5 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 79 °F, dew point 34 °F - Altimeter: 30.11 inHg - Observed at: ENV ## 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 20090710010469A](https://openairdocs.org/incident/20090710010469A), Jul 10, 2009: Amtr VANSRV4, Wendover, UT, Substantial damage. (-23) Pilot stated that upon landing he felt like landing was gong to be bad. While attempting to correct the situation the pilot added full power causing… ## Docket (1 files) The files NTSB released with the investigation on September 24, 2009, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=74376. 5.2 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 5.2 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40317506&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.