# NTSB GAA15CA241: Cessna 172, N5210A, Upperville, VA, June 22, 2015

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Data collection · Final report
- Date: June 22, 2015, 12:40 local (16:40 UTC)
- Place: Upperville, VA
- Coordinates: 38.971668, -77.86972 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=38.9717&lon=-77.8697&mi=10
- Phase of flight: [Enroute](https://openairdocs.org/ntsb-phases/400) (OpenAirDocs' grouping)
- Defining event: [Enroute-cruise: Birdstrike](https://openairdocs.org/ntsb-events/901)
- Highest injury: No injuries
- Injuries: 1 uninjured
- Status: Completed, report December 17, 2015
- Report: Approved by Office Director
- NTSB office: General Aviation Accidents
- Parties: FAA
- NTSB case key (mKey): 91889
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=GAA15CA241
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/91889/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=91889
- Page: https://openairdocs.org/ntsb/GAA15CA241

## Probable cause

An inflight bird strike, which resulted in wing spar damage.

## 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 · Effect on equipment (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.

- [Enroute-cruise: 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)

## Analysis

According to the student pilot, while flying en route to his home airport, the airplane sustained a bird strike to the right wing. The student pilot reported that he checked the flight controls and engine performance, and made the decision to continue the flight to his destination. He reported that during the approach he noticed that it took an abnormal amount of left aileron to maintain level flight; however, he landed the airplane without further incident. A subsequent examination of the airplane revealed that the airplane sustained substantial damage to the right wing spar. The pilot reported that there were no mechanical failures or anomalies prior to flight that would have prevented normal operation.

## Factual narrative

According to the student pilot, while flying en route to his home airport, the airplane sustained a bird strike to the right wing. The student pilot reported that he checked the flight controls and engine performance, and made the decision to continue the flight to his destination. He reported that during the approach he noticed that it took an abnormal amount of left aileron to maintain level flight; however, he landed the airplane without further incident. A subsequent examination of the airplane revealed that the airplane sustained substantial damage to the right wing spar. The pilot reported that there were no mechanical failures or anomalies prior to flight that would have prevented normal operation.

## Aircraft

- Registration: [N5210A](https://openairdocs.org/aircraft/N5210A), registered now, S/N 172S9118, built 2002 (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: 172S9118
- Year built: 2002
- Airframe hours: 4773
- Engines: LYCOMING IO-360-L2A 180 horsepower reciprocating
- Damage: Substantial damage
- Flight: Instructional, Part 91
- Operator: Aviation Adventures
- Registered owner: Topper Enterprises LLC
- Airworthiness certificate: Standard, Normal
- Last inspection: 100 hour, May 12, 2015, 58 hours before
- Departed: KSHD, Weyers Cave, VA
- Destination: KJYO, Leesburg, VA
- Flight plan: VFR
- Equipment: Stall warning system

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Student pilot; age 32; injuries: none; student; medical: class 3, without waivers/limitations; seat: left; restraint: 3-point; flight hours: 51.7 total, 37 in this make and model, 5 as pilot in command, 19.3 in the last 90 days

## Weather

- Conditions: Visual (VMC), Day
- Wind: 270° at 9 knots, gusting 14
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 86 °F, dew point 68 °F
- Altimeter: 30.05 inHg
- Observed at: KJYO, 16 nm away

## Other investigations on N5210A (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 NYC08CA282](https://openairdocs.org/ntsb/NYC08CA282), Aug 10, 2008: Cessna 172 (N5210A), Charlottesville, VA, substantial damage. Probable cause: The pilot's improper flare while landing. Contributing to the accident was the gusty wind condition.

## Docket (2 files)

The files NTSB released with the investigation on December 10, 2015, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=91889. 763 KB in all.

- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 405 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40434857&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF
- Photos (Courtesy of FAA) (item 2, .PDF, 2 photos, 358 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40434858&FileExtension=.PDF&FileName=Photos%20(Courtesy%20of%20FAA)-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.
