# Incident 20210629012959I: Commander Aircraft Co 114TC, Winstonsalem, NC, June 29, 2021

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: June 29, 2021, 14:22 local time
- Place: Winstonsalem, NC
- Damage: Minor damage
- Phase of flight: Landing: Rollout
- Operating rules: General operating rules (Part 91)
- Location: 36.0999° N, 80.2442° W: Placed by OpenAirDocs: center of Winston-Salem, NC, within about 7 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=36.0999&lon=-80.2442&mi=10
- Aircraft: N5424D, registered now (https://openairdocs.org/aircraft/N5424D) (OpenAirDocs)
- Registry model: Commander 114TC (registry code 0145002, https://openairdocs.org/model/commander-114tc) (OpenAirDocs)
- Registry engine: Lycoming TI0-540 series (registry code 41533, https://openairdocs.org/engine/lycoming-ti0-540-series) (OpenAirDocs)
- Reported make and model: COMMANDER AIRCRAFT CO 114TC
- Reported engine: LYCOMING TI0-540 SER
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Private pilot
- Pilot flight hours: 1,600 total, 1,581 in this make and model, 25 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20210629012959I

## Narrative

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

PILOT STATEMENT: AT APPROXIMATELY 9:40 PM ON TUESDAY JUNE 29TH, I WAS LANDING ON RUNWAY 33 AT KINT (WINSTON SALEM, NC).I HAD JUST COMPLETED THE RNAV 33.I WAS TALKING TO GREENSBORO ATC AND THEY WERE PROVIDING FLIGHT FOLLOWING. THE TOWER HAD CLOSED AT 9:30 PM.

IT WAS A CLEAR NIGHT AND VERY SMOOTH. I LANDED AND HAD TRAVELLED APPROXIMATELY 500 FEET. I WAS SLOWING DOWN FROM ABOUT A 75 KNOT TOUCHDOWN. I HAD NOT STARTED TO BRAKE YET AS IT WAS A 6655 FOOT RUNWAY AND I WAS TRAVELING ALL THE WAY TO THE END TO PARK AT SIGNATURE FBO. WITHIN A BLINK OF AN EYE, I NOTICED A LARGE FEMALE DEER RUNNING FROM MY LEFT TO RIGHT AT A FAST PACE. I QUICKLY SWERVED AS FAST AND SAFELY AS I COULD TO AVOID THE DEER. HOWEVER, WHAT I COULDN?T AVOID WAS THE SECOND DEER TRAILING THE FIRST. I FELT THE DEER HIT MY RIGHT WING. I WAS ABLE TO TAXI THE REMAINING 4000 PLUS FEET OF RUNWAY WITHOUT INCIDENT. THE PLANE TAXIED STRAIGHT AND SAFELY. I DIDN?T KNOW UNTIL I GOT TO SIGNATURE, THE EXTENT OF THE DAMAGE TO MY WING. I NOTIFIED THE LINE PERSONNEL WHAT HAD HAPPENED. I FILLED OUT A REPORT TO ONE OF THE FIREMEN THAT WAS ON DUTY AT THE TIME. HE SAID HE WOULD NOTIFY THE APPROPRIATE PERSONNEL. UPON FURTHER INSPECTION, IT WAS DETERMINED THAT THE DEER HIT ONE OF THE BLADES ON MY PROPELLOR BEFORE HITTING MY RIGHT WING. THE FIREMAN TOLD ME THEY WERE ABLE TO LOCATE THE DEER APPROXIMATELY WHERE I STATED AND DISPOSED OF THE DEER AND REOPENED THE RUNWAY.

THE FAA DID NOT DISPATCH TO THE INCIDENT SCENE. A REVIEW OF THE PICTURES, PIC STATEMENT PHONE CONVERSATION AND REPAIR PERSONNEL CONFIRMED THE INITIAL INCIDENT REPORT OF A DEER STRIKE TO THE FAA ROC. THE AIRCRAFT WILL BE REPAIRED THEN RETURNED TO SERVICE.

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.