# NTSB GAA20CA005: Pavel Vagner Tango, N8445P, Dublin, TX, October 5, 2019 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: October 5, 2019, 10:00 local (15:00 UTC) - Place: Dublin, TX - Coordinates: 32.068332, -98.325279 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=32.0683&lon=-98.3253&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing: Loss of control in flight](https://openairdocs.org/ntsb-events/240) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report May 21, 2020 - Report: Approved by Office Director - NTSB office: General Aviation Accidents - Parties: FAA - NTSB case key (mKey): 100378 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=GAA20CA005 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/100378/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=100378 - Page: https://openairdocs.org/ntsb/GAA20CA005 ## Probable cause The pilot's improper landing flare and failure to maintain lateral control, which resulted in a hard landing, loss of directional control, and subsequent roll-over. ## 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 · Pilot (probable cause); cases with it: [Pavel Vagner TANGO2, 3 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=05637KF), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Performance/control parameters: landing flare](https://openairdocs.org/ntsb-findings/01062041): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Pavel Vagner TANGO2, 1 case](https://openairdocs.org/ntsb-findings/01062041/cases.md?model=05637KF), [All aircraft, 1,285 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md) - [Performance/control parameters: lateral/bank control](https://openairdocs.org/ntsb-findings/01062023): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Pavel Vagner TANGO2, 1 case](https://openairdocs.org/ntsb-findings/01062023/cases.md?model=05637KF), [All aircraft, 390 cases](https://openairdocs.org/ntsb-findings/01062023/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: [Pavel Vagner TANGO2, 1 case](https://openairdocs.org/ntsb-findings/01062020/cases.md?model=05637KF), [All aircraft, 3,958 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing: Loss of control in flight](https://openairdocs.org/ntsb-events/240) (defining event); cases with it: [Pavel Vagner TANGO2, 3 cases](https://openairdocs.org/ntsb-events/240/sequence.md?model=05637KF), [All aircraft, 5,002 cases](https://openairdocs.org/ntsb-events/240/sequence.md) - [Landing: Hard landing](https://openairdocs.org/ntsb-events/092); cases with it: [Pavel Vagner TANGO2, 2 cases](https://openairdocs.org/ntsb-events/092/sequence.md?model=05637KF), [All aircraft, 2,102 cases](https://openairdocs.org/ntsb-events/092/sequence.md) - [Landing: Loss of control on ground](https://openairdocs.org/ntsb-events/230); cases with it: [Pavel Vagner TANGO2, 1 case](https://openairdocs.org/ntsb-events/230/sequence.md?model=05637KF), [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md) - [Landing: Roll over](https://openairdocs.org/ntsb-events/097); cases with it: [Pavel Vagner TANGO2, 1 case](https://openairdocs.org/ntsb-events/097/sequence.md?model=05637KF), [All aircraft, 261 cases](https://openairdocs.org/ntsb-events/097/sequence.md) ## Analysis The pilot reported that, during landing, the gyroplane was too high above the runway. He attempted to "cushion the landing" by forcing the nose up as he "gunned the engine a couple of times." The fluctuations in torque caused the gyroplane to turn right, and he corrected with hard, left rudder application. Because the gyroplane was configured with the front wheel mechanically linked to the rudder for directional control, the front wheel was turned completely left, which resulted in the gyroplane turning "violently" left upon touching down hard and then rolling onto its right side. The gyroplane sustained substantial damage to the main rotor drive system and the empennage. The pilot reported that there were no preaccident mechanical failures or malfunctions with the gyroplane that would have precluded normal operation and that the accident was caused by pilot error. ## Factual narrative The gyroplane pilot reported that during landing, the gyroplane was too high above the runway. He attempted to, "cushion the landing" by forcing the nose up as he, "gunned the engine a couple of times." The fluctuations in torque turned the nose of the gyroplane to the right, and he corrected with a hard-left rudder application. He recalled that the additional thrust from the engine gunning, increased the gyroplanes airspeed. The gyroplane was configured with the front wheel being mechanically linked to the rudder for directional control. When the gyroplane touched down, the pilot's hard left rudder application was also a hard-left turn input. The gyrocopter landed hard and rolled on to its side. The pilot reported that this accident was caused by pilot error. The nearest METAR was 12 NM to the northeast and reported that about the time of the accident the wind was from 170° at 4 knots. The pilot landed on runway 33 and would have produced a left quartering tailwind during the landing. The gyroplane sustained substantial damage to the main rotor drive system and the empennage. The pilot reported that there were no preaccident mechanical failures or malfunctions with the gyroplane that would have precluded normal operation. ## Aircraft - Registration: [N8445P](https://openairdocs.org/deregistered/N8445P-2022-02-24), registration cancelled 2022-02-24, S/N 000009, built 2018 (OpenAirDocs) - Reported make and model: Pavel Vagner TANGO (2) - Registry model: [Pavel Vagner TANGO2](https://openairdocs.org/model/pavel-vagner-tango2) (registry code 05637KF) (OpenAirDocs) - Registry engine: [Yamaha ALL MDLS A/B](https://openairdocs.org/engine/yamaha-all-mdls-a-b) (registry code 80000, reciprocating) (OpenAirDocs) - Category: Gyroplane, amateur-built - Serial number: 000009 - Year built: 2018 - Airframe hours: 67 - Engines: Yamaha Genesis/130 130 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Special, Experimental (Special) - Last inspection: Condition, November 16, 2018 - Departed: 0TX1, Granbury, TX - Destination: 9F0, Dublin, TX - Airport: 9F0, Dublin Muni, runway 33, 3,200 × 60 ft, asphalt - Equipment: Handheld GPS, ADS-B ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 70; injuries: none; sport pilot, foreign; medical: sport pilot; last flight review November 6, 2017; seat: front; restraint: 3-point; flight hours: 176 total, 25.5 in this make and model, 28.7 as pilot in command, 21.2 in the last 90 days, 7 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: 170° at 4 knots - Visibility: 10 statute miles - Temperature: 77 °F, dew point 66 °F - Altimeter: 30.07 inHg - Observed at: KSEP, 12 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 20191005024049A](https://openairdocs.org/incident/20191005024049A), Oct 5, 2019: Pavel Vagner TANGO2, Dublin, TX, Substantial damage. The aircraft did not come to a complete stop before he dropped the nose down. The aircraft pulled right and the blade impacted the ground. The impacted blade… ## Docket (2 files) The files NTSB released with the investigation on January 8, 2020, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=100378. 1.5 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 1.3 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40479687&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Photo (item 2, .PDF, 131 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40479688&FileExtension=.PDF&FileName=Photo-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.