# NTSB ERA24LA212: Piper PA-20-135, N8290C, Georgetown, OH, May 2, 2024

- Type: NTSB accident investigation
- Classification: Accident · Minor injuries · Class 4 · Limited · Final report
- Date: May 2, 2024, 19:30 local (23:30 UTC)
- Place: Georgetown, OH · GEO Airport
- Coordinates: 38.882, -83.882667 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=38.8820&lon=-83.8827&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Defining event: [Landing: Aircraft wake turb encounter](https://openairdocs.org/ntsb-events/361)
- Highest injury: Minor injuries
- Injuries: 1 minor, 1 uninjured
- Status: Completed
- Report: Approved by Office Director
- Investigation class: Class 4 - Basic report with no Prelim publish
- NTSB office: Eastern Region Aviation
- Parties: FAA/FSDO
- NTSB case key (mKey): 194226
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA24LA212
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/194226/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=194226
- Page: https://openairdocs.org/ntsb/ERA24LA212

## Probable cause

An inadvertent encounter with the rotor wash of a nearby hovering helicopter during landing, which resulted in a loss of control and a runway excursion.

## Findings

NTSB's coded findings; those marked are part of the probable cause.

- [Turbulence: wake turbulence](https://openairdocs.org/ntsb-findings/03032025): Environmental issues › Conditions/weather/phenomena · Effect on equipment (probable cause); cases with it: [Piper PA-20-135, 1 case](https://openairdocs.org/ntsb-findings/03032025/cases.md?model=7102010), [All aircraft, 47 cases](https://openairdocs.org/ntsb-findings/03032025/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-20-135, 4 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=7102010), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md)
- [Performance/control parameters: lateral/bank control](https://openairdocs.org/ntsb-findings/01062023): Aircraft › Aircraft oper/perf/capability · Attain/maintain not possible (probable cause); cases with it: [Piper PA-20-135, 1 case](https://openairdocs.org/ntsb-findings/01062023/cases.md?model=7102010), [All aircraft, 390 cases](https://openairdocs.org/ntsb-findings/01062023/cases.md)

## Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event best describes what happened.

- [Landing: Aircraft wake turb encounter](https://openairdocs.org/ntsb-events/361) (defining event); cases with it: [Piper PA-20-135, 1 case](https://openairdocs.org/ntsb-events/361/sequence.md?model=7102010), [All aircraft, 37 cases](https://openairdocs.org/ntsb-events/361/sequence.md)
- [Landing: Loss of control on ground](https://openairdocs.org/ntsb-events/230); cases with it: [Piper PA-20-135, 2 cases](https://openairdocs.org/ntsb-events/230/sequence.md?model=7102010), [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md)
- [Landing: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Piper PA-20-135, 1 case](https://openairdocs.org/ntsb-events/300/sequence.md?model=7102010), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md)

## Analysis

The pilot reported that the purpose of the flight was to return to his home airport and that there was a military helicopter and another small single engine airplane in the traffic pattern. While the pilot was landing, the military helicopter was in a hover on the ramp adjacent to the runway. The pilot reported that the airplane touched down normally and that he had positive control of the airplane during the initial landing rollout with all wheels on the ground. Once the airplane passed abeam the helicopter, the pilot described that the airplane “levitated” off the ground in a nose high attitude and began to turn to the right. The pilot attempted to regain control of the airplane, but it continued to the right and departed the runway surface. During the runway excursion, the airplane sustained substantial damage to the fuselage. The pilot reported there were no mechanical failures or anomalies with the airplane that would have precluded normal operation. Based on this information, it is likely that during the landing roll, the airplane encountered the rotor wash of the hovering military helicopter that was adjacent to the runway.

## Aircraft

- Registration: [N8290C](https://openairdocs.org/aircraft/N8290C), registered now, S/N 20-1119, built 1954 (OpenAirDocs)
- Reported make and model: PIPER PA-20-135
- Registry model: [Piper PA-20-135](https://openairdocs.org/model/piper-pa-20-135) (registry code 7102010) (OpenAirDocs)
- Registry engine: [Lycoming 0-290 series](https://openairdocs.org/engine/lycoming-0-290-series) (registry code 41506, 4 cycle) (OpenAirDocs)
- Category: Airplane
- Serial number: 20-1119
- Year built: 1954
- Airframe hours: 2892
- Engines: Lycoming O-290-D2 135 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Airworthiness certificate: Standard, Normal
- Last inspection: Annual, November 10, 2023, 6 hours before
- Departed: TZR, Columbus, OH
- Destination: Same as departure
- Airport: GEO, Brown County, runway 18, 3,530 × 65 ft, asphalt
- Equipment: Electronic flight bag or handheld device, ADS-B

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 36; injuries: none; commercial; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 2, with waivers/limitations; last flight review July 14, 2022; seat: left; restraint: lap only; flight hours: 825 total, 120 in this make and model, 613 as pilot in command, 6 in the last 90 days, 3 in the last 30 days, 0 in the last 24 hours

## Weather

- Conditions: Visual (VMC), Dusk
- Wind: calm
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 82 °F, dew point 55 °F
- Altimeter: 29.93 inHg
- Observed at: FGX, 21 nm away
- METAR: METAR KFGX 022335Z AUTO 00000KT 10SM CLR 28/13 A2993 RMK AO2 T02810133=

## 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 20240502008409A](https://openairdocs.org/incident/20240502008409A), May 2, 2024: Piper PA-20-135, Georgetown, OH, Substantial damage. Piper PA-20 was second in pattern for rwy 18 at kgeo behind a military helicopter. Just past midfield downwind, Piper pilot stated he lost sight of military…

## Other investigations on N8290C (1)

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.

- [NTSB CHI73DEA42](https://openairdocs.org/ntsb/CHI73DEA42), Jun 25, 1973: Piper PA-20 (N8290C), Portland, IN, substantial damage

## Docket (4 files)

The files NTSB released with the investigation on July 18, 2024, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=194226. 5.6 MB in all.

- Pilot/operator aircraft accident report, NTSB form 6120.1 (item 1, PDF, 14 pages, 2.3 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=17291294&FileExtension=pdf&FileName=01%20Pilot%27s%206120%20Form%20with%20Statement%20Attached_Redacted-Rel.pdf
- Pilot's statement (item 2, PDF, 5 pages, 343 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=17291706&FileExtension=pdf&FileName=02%20Pilot%27s%20Statement-Rel.pdf
- Memorandum for record - pilot correspondence (item 3, PDF, 1 page, 66 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=17291455&FileExtension=pdf&FileName=03%20Pilot%20MOR-Rel.pdf
- Investigation photographs (item 4, PDF, 5 pages, 2.9 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=17291631&FileExtension=pdf&FileName=05%20Investigation%20Photographs_Redacted-Rel.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.
