# NTSB GAA19CA304: Piper PA32R, N9966G, Flippin, AR, June 2, 2019

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Data collection · Final report
- Date: June 1, 2019, 20:15 local (Jun 2, 2019, 01:15 UTC)
- Place: Flippin, AR
- Coordinates: 36.290832, -92.590278 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=36.2908&lon=-92.5903&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Defining event: [Landing: Wildlife encounter (non-bird)](https://openairdocs.org/ntsb-events/310)
- Highest injury: No injuries
- Injuries: 2 uninjured
- Status: Completed, report November 6, 2019
- Report: Approved by Office Director
- NTSB office: General Aviation Accidents
- Parties: FAA
- NTSB case key (mKey): 99530
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=GAA19CA304
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/99530/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=99530
- Page: https://openairdocs.org/ntsb/GAA19CA304

## Probable cause

The airplane’s collision with deer during the landing and the airport’s failure to provide an adequate barrier to prevent wildlife from entering the runway environment despite previous deer strikes.

## Findings

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

- [Object/animal/substance: animal(s)/bird(s)](https://openairdocs.org/ntsb-findings/03022045): Environmental issues › Physical environment · Ability to respond/compensate (probable cause); cases with it: [Piper PA-32R-301T, 1 case](https://openairdocs.org/ntsb-findings/03022045/cases.md?model=7103220), [All aircraft, 358 cases](https://openairdocs.org/ntsb-findings/03022045/cases.md)
- [Object/animal/substance: animal(s)/bird(s)](https://openairdocs.org/ntsb-findings/03022045): Environmental issues › Physical environment · Effect on equipment (probable cause); cases with it: [Piper PA-32R-301T, 1 case](https://openairdocs.org/ntsb-findings/03022045/cases.md?model=7103220), [All aircraft, 358 cases](https://openairdocs.org/ntsb-findings/03022045/cases.md)
- [Airport facilities/design: security](https://openairdocs.org/ntsb-findings/03017080): Environmental issues › Operating environment · Effect on operation (probable cause); cases with it: [Piper PA-32R-301T, 1 case](https://openairdocs.org/ntsb-findings/03017080/cases.md?model=7103220), [All aircraft, 4 cases](https://openairdocs.org/ntsb-findings/03017080/cases.md)
- [Airport facilities/design: security](https://openairdocs.org/ntsb-findings/03017080): Environmental issues › Operating environment · Contributed to outcome (probable cause); cases with it: [Piper PA-32R-301T, 1 case](https://openairdocs.org/ntsb-findings/03017080/cases.md?model=7103220), [All aircraft, 4 cases](https://openairdocs.org/ntsb-findings/03017080/cases.md)

## Sequence of events

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

- [Landing: Wildlife encounter (non-bird)](https://openairdocs.org/ntsb-events/310) (defining event); cases with it: [Piper PA-32R-301T, 1 case](https://openairdocs.org/ntsb-events/310/sequence.md?model=7103220), [All aircraft, 107 cases](https://openairdocs.org/ntsb-events/310/sequence.md)

## Analysis

The pilot reported that, during the landing roll, three deer ran across the runway. He felt a hard strike on the inboard section of the right wing, saw a deer roll over the right wing, and felt a sensation like the right landing gear "hopped" as it ran over a second deer. The pilot was able to maintain control of the airplane and taxied to the ramp without further incident. The airplane sustained substantial damage to the right wing. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. The pilot added that this was the second deer strike the airplane experienced in the previous three weeks, that he had seen deer standing on the runway numerous times, and that airport management was aware of the situation. He stated that the airport had only 500 linear ft of chain-link fence and a gate at the airport entrance and that the rest of the airport was only surrounded by three strands of barbed wire in "various states of disrepair." The Federal Aviation Administration Chart Supplement, South Central U.S. page for the accident airport, in part, stated the following: "Wildlife on and [in vicinity of] airport."

## Factual narrative

The pilot reported that, during the landing roll, three deer ran from right to left across the runway. He felt a hard strike on the inboard section of the right wing, observed a deer roll over the right wing, and felt a sensation of the right landing gear "hopped" as it ran over a second deer. The pilot was able to maintain control of the airplane and taxied to the ramp without further incident. The airplane sustained substantial damage to the right wing. The pilot and passenger had to egress through the rear baggage door due to damage to the cabin door. After exiting the plane, the pilot noticed copious amounts of fuel pouring from the damaged wing. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. The pilot added that this was the second deer strike the airplane experienced in the previous three weeks, and airport management was aware of the situation. The Federal Aviation Administration Chart Supplement, South Central U.S. page for the accident airport, in part, stated: "Wildlife on and [in vicinity of] airport."

## Aircraft

- Registration: [N9966G](https://openairdocs.org/aircraft/N9966G), registered now, S/N 3257370, built 2005 (OpenAirDocs)
- Reported make and model: Piper PA32R (301T)
- Registry model: [Piper PA-32R-301T](https://openairdocs.org/model/piper-pa-32r-301t) (registry code 7103220) (OpenAirDocs)
- Registry engine: [Lycoming TIO-540 series](https://openairdocs.org/engine/lycoming-tio-540-series) (registry code 41569, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 3257370
- Year built: 2005
- Airframe hours: 1087
- Engines: Lycoming TIO-540-AHIA 300 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Airworthiness certificate: Standard, Normal
- Last inspection: Annual, October 1, 2018
- Departed: FLP, Flippin, AR
- Destination: FLP, Flippin, AR
- Airport: FLP, Marion County Rgnl, runway 04, 5,001 × 75 ft
- Equipment: Electronic flight bag or handheld device, Auto-pilot, ADS-B, Electronic multifunction display, Electronic primary flight display, Handheld GPS, Onboard weather, Stall warning system

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 48; injuries: none; private; airplane ratings: single-engine land; medical: basicmed, with waivers/limitations; last flight review June 28, 2018; seat: left; restraint: 3-point; flight hours: 916 total, 313 in this make and model, 452 as pilot in command, 31 in the last 90 days, 4 in the last 30 days, 1 in the last 24 hours

## Weather

- Conditions: Visual (VMC), Day
- Wind: 270° at 3 knots
- Visibility: 10 statute miles
- Temperature: 77 °F, dew point 68 °F
- Altimeter: 29.88 inHg
- Observed at: KFLP

## 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 20190601016399A](https://openairdocs.org/incident/20190601016399A), Jun 1, 2019: Piper PA-32R-301T, Flippin, AR, Substantial damage. On June 1, 2019, about 2030 central standard time, a Piper PA32R-301T, N9966G sustained substantial damage when the plane collided with a deer during landing…

## Docket (3 files)

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

- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 1.9 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40474274&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF
- Federal Aviation Administration Chart Supplement, South Central U.S. (item 2, .PDF, 1.3 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40474275&FileExtension=.PDF&FileName=Federal%20Aviation%20Administration%20Chart%20Supplement,%20South%20Central%20U.S.-Master.PDF
- Accident Photo (item 3, .PDF, 1 photo, 233 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40474276&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.
