# NTSB GAA19CA069: Piper PA32R, N4137W, Versailles, OH, November 17, 2018 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: November 17, 2018, 16:20 local (22:20 UTC) - Place: Versailles, OH - Coordinates: 40.204444, -84.532501 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=40.2044&lon=-84.5325&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-flare/touchdown: Loss of control on ground](https://openairdocs.org/ntsb-events/230) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report June 16, 2020 - Report: Approved by Office Director - NTSB office: General Aviation Accidents - Parties: FAA - NTSB case key (mKey): 98665 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=GAA19CA069 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/98665/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=98665 - Page: https://openairdocs.org/ntsb/GAA19CA069 ## Probable cause The pilot's improper landing flare, which resulted in landing on the landing gear first and a subsequent loss of directional control, a runway excursion, and impact with a tree and a fence during an attempted go-around. ## 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: [Piper PA-32R-301, 2 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md?model=7103218), [All aircraft, 1,285 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md) - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Piper PA-32R-301, 10 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=7103218), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/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: [Piper PA-32R-301, 2 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md?model=7103218), [All aircraft, 3,958 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md) - [Object/animal/substance: tree(s)](https://openairdocs.org/ntsb-findings/03022020): Environmental issues › Physical environment · Effect on operation (probable cause); cases with it: [Piper PA-32R-301, 2 cases](https://openairdocs.org/ntsb-findings/03022020/cases.md?model=7103218), [All aircraft, 933 cases](https://openairdocs.org/ntsb-findings/03022020/cases.md) - [Object/animal/substance: fence/fence post](https://openairdocs.org/ntsb-findings/03022047): Environmental issues › Physical environment · Effect on operation (probable cause); cases with it: [Piper PA-32R-301, 1 case](https://openairdocs.org/ntsb-findings/03022047/cases.md?model=7103218), [All aircraft, 313 cases](https://openairdocs.org/ntsb-findings/03022047/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); cases with it: [Piper PA-32R-301, 5 cases](https://openairdocs.org/ntsb-events/090/sequence.md?model=7103218), [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) (defining event); cases with it: [Piper PA-32R-301, 2 cases](https://openairdocs.org/ntsb-events/230/sequence.md?model=7103218), [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md) - [Landing-flare/touchdown: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Piper PA-32R-301, 3 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=7103218), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md) - [Landing-flare/touchdown: Attempted remediation/recovery](https://openairdocs.org/ntsb-events/060); cases with it: [Piper PA-32R-301, 1 case](https://openairdocs.org/ntsb-events/060/sequence.md?model=7103218), [All aircraft, 1,422 cases](https://openairdocs.org/ntsb-events/060/sequence.md) - [Landing-flare/touchdown: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Piper PA-32R-301, 12 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=7103218), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis During the initial approach, the pilot and airplane owner were not able to see the airport environment due to haze, but both of them were able to see the ground. The pilot continued to use the GPS for navigation, and once the airplane was above the airport, they were able to see the runway. The pilot then made a 180º turn to align for a final approach; however, the approach was not stabilized, so the pilot initiated a go-around. After the climbout, he made another 180º turn for final approach to the opposite runway. The airplane touched down on the nose landing gear first and then immediately veered left and exited the runway. The pilot attempted another go-around, but the airplane struck a tree and then an airport perimeter fence. The airplane sustained substantial damage to the left wing. The owner reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. ## Factual narrative The owner of the airplane reported that he hired the accident pilot to fly him to the destination airport. During the initial approach, they were not able to see the airport environment due to the haze, but both were able to see the ground. The pilot continued to use the GPS for navigation and once they were above the airport, they were able to see the runway. The pilot then made a 180º turn to align for a final approach to runway 27; however, the approach was not stabilized so the pilot initiated a go-around. After the climb out, he turned 180º for a final approach to runway 09. The airplane touched down nose landing gear first, then immediately veered left and exited the runway. The pilot attempted another go-around, but the airplane struck a tree and impacted the airport perimeter fence. The airplane sustained substantial damage to the left wing. The owner reported that there were no mechanical failures or malfunctions with the airplane that would have precluded normal operation. ## Aircraft - Registration: [N4137W](https://openairdocs.org/deregistered/N4137W-2020-05-29), registration cancelled 2020-05-29, S/N 3246138, built 1999 (OpenAirDocs) - Reported make and model: Piper PA32R (301) - Registry model: [Piper PA-32R-301](https://openairdocs.org/model/piper-pa-32r-301) (registry code 7103218) (OpenAirDocs) - Registry engine: [Lycoming IO-540 series](https://openairdocs.org/engine/lycoming-io-540-series) (registry code 41530, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 3246138 - Year built: 1999 - Engines: Lycoming IO-540 reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: 335 Aviation LLC - Registered owner: 335 Aviation LLC - Airworthiness certificate: Standard, Normal - Departed: XNX, Gallatin, TN - Destination: VES, Versailles, OH - Airport: VES, Darke County, runway 09, 4,802 × 75 ft, asphalt - Equipment: Unknown ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 77; injuries: none; commercial; airplane ratings: multi-engine land, single-engine land; instrument ratings: airplane; medical: class 2, with waivers/limitations; seat: left; flight hours: 4,000 total, 2 in this make and model ## Weather - Conditions: Visual (VMC), Day - Wind: calm - Visibility: 10 statute miles - Lowest ceiling: 2,000 ft overcast - Temperature: 37 °F, dew point 34 °F - Altimeter: 30.23 inHg - Observed at: KVES ## 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 20181117022609A](https://openairdocs.org/incident/20181117022609A), Nov 17, 2018: Piper PA-32R-301, Versailles, OH, Substantial damage. On touchdown skid marks on the runway showed the nose touched down on the centerline of the runway then the aircraft started too veere off the left side of… ## Docket (3 files) The files NTSB released with the investigation on April 17, 2020, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=98665. 282 KB in all. - Pilot's Statement (item 1, .PDF, 112 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40482594&FileExtension=.PDF&FileName=Pilot%27s%20Statement-Master.PDF - FAA Inspector's Statement (item 2, .PDF, 65 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40482595&FileExtension=.PDF&FileName=FAA%20Inspector%27s%20Statement-Master.PDF - Accident Photo (item 3, .PDF, 105 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40482596&FileExtension=.PDF&FileName=Accident%20Photo-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.