# NTSB WPR20LA256: Cessna 172, N55231, San Jose, CA, August 2, 2020 - Type: NTSB accident investigation - Classification: Accident · No injuries · Class 3 · Limited · Final report - Date: August 2, 2020, 10:17 local (17:17 UTC) - Place: San Jose, CA - Coordinates: 37.337776, -121.80027 - Nearby events: https://openairdocs.org/map.md?lat=37.3378&lon=-121.8003&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Defining event: [Approach-VFR pattern downwind: Birdstrike](https://openairdocs.org/ntsb-events/901) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed - Report: Approved by Office Director - Investigation class: Class 3 - NTSB office: Western Pacific Region - Parties: FAA FSDO - NTSB case key (mKey): 101748 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR20LA256 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/101748/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=101748 - Page: https://openairdocs.org/ntsb/WPR20LA256 ## Probable cause The airplane’s collision with a bird while maneuvering in the airport traffic pattern. ## 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: [Cessna 172S, 16 cases](https://openairdocs.org/ntsb-findings/03022045/cases.md?model=2072439), [All aircraft, 358 cases](https://openairdocs.org/ntsb-findings/03022045/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Maneuvering: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Cessna 172S, 118 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=2072439), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) - [Approach-VFR pattern downwind: Birdstrike](https://openairdocs.org/ntsb-events/901) (defining event); cases with it: [Cessna 172S, 13 cases](https://openairdocs.org/ntsb-events/901/sequence.md?model=2072439), [All aircraft, 253 cases](https://openairdocs.org/ntsb-events/901/sequence.md) - [Maneuvering: Birdstrike](https://openairdocs.org/ntsb-events/901); cases with it: [Cessna 172S, 13 cases](https://openairdocs.org/ntsb-events/901/sequence.md?model=2072439), [All aircraft, 253 cases](https://openairdocs.org/ntsb-events/901/sequence.md) ## Analysis The pilot stated that while in the downwind leg of a traffic pattern, the right wing of the airplane impacted an object. Subsequently, the airplane yawed to the right and lost altitude. The pilot notified the tower and immediately executed a precautionary landing. Postaccident examination of the airplane found damage to the right wing’s leading edge, just outboard of the side strut. The leading edge was crushed aft revealing internal surfaces of the wing structure. Feather fragments were later found on the internal surfaces. A large deceased golden eagle and a small hobby drone were found below the downwind leg traffic area during a search. The hobby drone was mostly undamaged and had signatures indicating that it had been in the area for an extended period of time and was not likely impacted by an airplane. Lab results confirmed the airplane impacted a golden eagle. ## Factual narrative On August 2, 2020, about 1017 Pacific daylight time, a Cessna 172 airplane, N55231, was substantially damaged when it was involved in an accident near San Jose, California. The pilot and passenger were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot stated that during the approach to Reid-Hillview (RHV) airport, while in the downwind leg for runway 31, the right wing of the airplane impacted an unknown object. Subsequently, the airplane yawed to the right and lost altitude. The pilot notified the tower and immediately executed a precautionary landing to runway 31. Postaccident examination of the airplane found damage to the right wing’s leading edge, just outboard of the side strut. The leading edge was crushed aft revealing internal surfaces of the wing structure. Feather fragments were later found on the internal surfaces. A large deceased golden eagle and a small hobby drone were found during a search below the downwind leg traffic area. The drone was mostly intact, and the finishes were faded. Search personnel who located the drone stated that it appeared the drone was there for a while. Sections of the airplane wing were sent to the National Transportation Safety Board’s Materials Laboratory for examination. Surfaces of the wing sections were inspected using an ultraviolet light, which revealed a fluorescing substance found to be a candidate for biological fluids. The feathers gathered from the deceased golden eagle and the feathers collected from the airplane’s wing were shipped to the Feather Identification Lab at the Smithsonian Institute National Museum of Natural History to look for avian contamination and identification. The results were consistent with that of a golden eagle or Aquila Chrysaetos, which were consistent with biological material recovered near the accident location. These results were consistent with those of other specimens sent directly to the Feather Identification Lab from the accident airplane, which were also consistent with an in-flight collision with the recovered golden eagle. ## Aircraft - Registration: [N55231](https://openairdocs.org/aircraft/N55231), registered now, S/N 172S11414, built 2014 (OpenAirDocs) - Reported make and model: CESSNA 172 (S) - Registry model: [Cessna 172S](https://openairdocs.org/model/cessna-172s) (registry code 2072439) (OpenAirDocs) - Registry engine: [Lycoming IO-360-L2A](https://openairdocs.org/engine/lycoming-io-360-l2a) (registry code 41597, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 172S11414 - Year built: 2014 - Airframe hours: 1484.3 - Engines: Lycoming IO-360-L2A 180 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: 100 hour, March 5, 2020 - Departed: CXP, Carson City, NV - Destination: RHV, San Jose, CA - Airport: KRHV, Reid Hillview, runway 31R, 3,100 × 75 ft, asphalt - Equipment: Electronic multifunction display, Auto-pilot, ADS-B, Stall warning system, Electronic primary flight display ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 33; injuries: none; private, flight instructor; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 2, without waivers/limitations; last flight review August 26, 2018; seat: left; restraint: 3-point; flight hours: 1,276 total, 1,250 in this make and model, 1,070 as pilot in command, 90 in the last 90 days, 15 in the last 30 days, 4 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: calm - Visibility: 7 statute miles - Lowest ceiling: none - Temperature: 55 °F, dew point 45 °F - Altimeter: 30.05 inHg - Observed at: KRHV ## 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 20200802014109A](https://openairdocs.org/incident/20200802014109A), Aug 2, 2020: Cessna 172S, San Jose, CA, Substantial damage. San Jose, CA (rhv): N55231, C172, rhvorig rptd as bird strike downwind RWY31R. Data was removed from the garmin G1000. Data tracks were removed and laid out… ## Other investigations on N55231 (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 WPR26LA220](https://openairdocs.org/ntsb/WPR26LA220), Jun 11, 2026: Cessna 172S (N55231), Morgan Hill, CA, substantial damage. Probable cause: An in-flight collision with a bird. ## Docket (3 files) The files NTSB released with the investigation on May 10, 2022, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=101748. 5.2 MB in all. - Pilot/operator aircraft accident report, NTSB form 6120.1 (item 1, PDF, 9 pages, 3.3 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13831546&FileExtension=pdf&FileName=NTSB%20Form%206120_1%20N55231%2008022020%20V03redacted%20-%20San-Rel.pdf - Materials laboratory factual report (item 2, PDF, 9 pages, 6 photos, 898 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=11594419&FileExtension=pdf&FileName=20-059%20-%20Materials%20Lab%20Factual%20Report%20(WPR20LA256)_Redacted-Rel.pdf - Photos (item 3, PDF, 3 pages, 932 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13714006&FileExtension=pdf&FileName=Photo%20DMS-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.