# Incident 20200207000139I: Cessna 340A, Scott City, KS, February 7, 2020

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: February 7, 2020, 08:40 local time
- Place: Scott City, KS
- Airport: Scott City
- Damage: Minor damage
- Phase of flight: Cruise/Level Flight
- Operating rules: General operating rules (Part 91)
- Operator: CXUA
- Location: 38.4750° N, 100.8844° W: Placed by OpenAirDocs at SCOTT CITY MUNI (TQK), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=38.4750&lon=-100.8844&mi=10
- Aircraft: N500CT, registered now (https://openairdocs.org/aircraft/N500CT) (OpenAirDocs)
- Registry model: Cessna 340A (registry code 2076405, https://openairdocs.org/model/cessna-340a) (OpenAirDocs)
- Registry engine: Continental TSIO-520 series (registry code 17040, https://openairdocs.org/engine/continental-tsio-520-series) (OpenAirDocs)
- Reported make and model: CESSNA 340A
- Reported engine: CONT MOTOR TSIO-520 SER
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Commercial pilot
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20200207000139I

## Narrative

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

THE OPERATOR'S CHIEF PILOT INFORMED THE POI THAT ONE OF THEIR AIRCRAFT HAD EXPERIENCED A POSSIBLE INFLIGHT COLLISION WITH AN UNKNOWN OBJECT. THE AIRCRAFT WAS ON A SHORT VFR FLIGHT TO THE OPERATOR'S HOME BASE WITH ONLY THE PILOT ONBOARD, WHEN AN IMPACT OCCURRED AT AN ESTIMATED ALTITUDE OF 2000 FEET AGL. THE PILOT DID NOT SEE THE OBJECT THAT WAS IMPACTED, BUT REACTED BY VERIFYING A LIKELY PROBLEM WITH THE RIGHT ENGINE. THE RIGHT ENGINE WAS THEN SUCCESSFULLY SHUT DOWN AND SECURED. THE AIRCRAFT THEN SAFELY COMPLETED THE SHORT REMAINING FLIGHT TO ITS DESTINATION.

A VISUAL INSPECTION ON THE GROUND AT THE OPERATOR'S HOME BASE THEN REVEALED WHAT APPEARED TO BE IMPACT DAMAGE TO ONE PROPELLER BLADE OF THE RIGHT PROPELLER. THERE WERE NO INDICATIONS OF ORGANIC RESIDUE ON THE PROPELLER, INDICATING A BIRD STRIKE.

FSDO CONTACTED AIRPORT MANAGERS AT THE AIRCRAFT'S RECENT LOCATIONS TO INQUIRE ABOUT ANY DAMAGE TO AIRPORT INFRASTRUCTURE AS A POSSIBLE RESULT OF COLLISION BY A TAXIING AIRCRAFT. MANAGERS STATED THAT NO SUCH DAMAGE HAD BEEN REPORTED OR WAS APPARENT AT THESE TWO AIRPORTS.

ATC QUALITY CONTROL OFFICE WAS UNABLE TO LOCATE THE INCIDENT AIRCRAFT'S VFR TARGET OR OTHER POSSIBLE INCIDENT-RELATED VFR TARGETS ON THE DATE AND TIME IN QUESTION.

THE AIRCRAFT'S MANUFACTURER SAFETY CONSULTANT AND A PROPELLER MANUFACTURER'S ENGINEER WAS CONSULTED. BOTH FELT THAT THE PROPELLER HAD "STRUCK AN OBJECT OF DEFINITE MASS", AND WAS UNLIKELY TO HAVE STRUCK A SMALL, LIGHT, UAS OF PLASTIC CONSTRUCTION.

THE PILOT WAS THE SOLE PERSON PRESENT DURING THE EVENT.  NO OTHER WITNESSES WERE DISCOVERED.

THERE IS NO EVIDENCE TO SUGGEST THAT ANY REGULATIONS WERE VIOLATED OR THAT ANY UNSAFE PRACTICES OCCURRED.

## Other reports on N500CT (1)

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

- [Incident 20100105025639I](https://openairdocs.org/incident/20100105025639I), Jan 5, 2010: Cessna 340A (N500CT), Hays, KS, Minor damage. At approximately 2115 local time, the aircraft made an ILS approach to runway 34 at Hays municipal airport (hys). The pilot verified that all three landing…

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.