# Incident 20240124003299I: Cessna 172S, Phoenix, AZ, January 24, 2024

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: January 24, 2024, 15:05 local time
- Place: Phoenix, AZ
- Airport: Phoenix-Mesa Gateway
- Damage: Minor damage
- Phase of flight: Landing: Rollout
- Operating rules: General operating rules (Part 91)
- Location: 33.4484° N, 112.0740° W: Placed by OpenAirDocs: center of Phoenix, AZ, within about 13 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=33.4484&lon=-112.0740&mi=10
- Aircraft: N117SV, registered now (https://openairdocs.org/aircraft/N117SV) (OpenAirDocs)
- Registry model: Cessna 172S (registry code 2072439, https://openairdocs.org/model/cessna-172s) (OpenAirDocs)
- Registry engine: Lycoming IO-360-L2A (registry code 41597, https://openairdocs.org/engine/lycoming-io-360-l2a) (OpenAirDocs)
- Reported make and model: CESSNA 172S
- Reported engine: LYCOMING IO-360-L2A
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Commercial pilot, flight instructor
- Pilot flight hours: 900 total
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20240124003299I

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

DURING THE THIRD AND FINAL LAP IN THE TRAFFIC PATTERN THE PIC EXPERIENCED A BIRD STRIKE DURING AN INSTRUCTIONAL FLIGHT.  THE PIC RECALLED AS THE AIRCRAFT TURNED FINAL, THEY CHECKED THE RUNWAY AND DID NOT SEE ANY BIRDS NEAR THE RUNWAY. UPON COMPLETING THE LANDING CHECKLIST THE PIC AGAIN OBSERVED A CLEAR RUNWAY. AS THE AIRCRAFT WAS IN THE FLARE AND IN THE TOUCHDOWN ROLL, A GROUPING OF BIRDS FLEW INTO THE AIRCRAFT’S FLIGHT PATH. THE PIC HEARD A CLUNK ON THE RIGHT WING FROM A BIRD HITTING THE RIGHT WING. AFTER HEARING THE BIRD HIT THE AIRCRAFT THE PIC CLOSED THE THROTTLE AND ADVISED THE TOWER, THAT THEY HAD EXPERIENCED A BIRD STRIKE AND NEEDED A FULL STOP. UPON EXITING THE RUNWAY, THE PIC OBSERVED THE PART OF THE AIRCRAFT THEY COULD SEE AND DETERMINED THE AIRCRAFT COULD TAXI BACK TO THE RAMP.   THE PIC CALLED FOR TAXI TO THE RAMP WHICH WAS FOLLOWED BY THE SHUT-DOWN CHECKLIST. AFTER THE AIRCRAFT WAS SECURED, THE PIC DID A THOROUGH EXTERIOR OBSERVATION OF THE AIRCRAFT TO DETERMINE WHAT DAMAGE HAD BEEN OBSERVED.

## Other reports on N117SV (1)

Matched to the same aircraft by N-number and date.

- [Incident 20161212024609I](https://openairdocs.org/incident/20161212024609I), Dec 12, 2016: Cessna 172S (N117SV), No damage. Aircraft suffered intermittent loss of engine power during initial climb out. CFI aboard felt the engine was not running properly and requested to return and…

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
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.