# Incident 20210604009449I: Cirrus SR22, Philipsburg, OH, June 4, 2021 - Type: FAA incident report (Accident/Incident Data System), as reported - Date: June 4, 2021, 10:42 local time - Place: Philipsburg, OH - Damage: Minor damage - Phase of flight: Landing: Touchdown - Operating rules: General operating rules (Part 91) - Aircraft: N75SA, registered now (https://openairdocs.org/aircraft/N75SA) (OpenAirDocs) - Registry model: Cirrus Design SR22 (registry code 2130001, https://openairdocs.org/model/cirrus-design-sr22) (OpenAirDocs) - Registry engine: Continental IO-550 series (registry code 17042, https://openairdocs.org/engine/continental-io-550-series) (OpenAirDocs) - Reported make and model: CIRRUS SR22 - People aboard: 1 - Fatal injuries: 0 - Other injuries: 0 - Pilot certificates: Private pilot - Pilot flight hours: 375 total, 40 in this make and model, 40 in the last 90 days - FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/) - Page: https://openairdocs.org/incident/20210604009449I ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. DESCRIPTION: ON FRIDAY, JUNE 4, 2021 AT APPROXIMATELY 1042 EDT, AN INCIDENT OCCURRED AT THE K3I7 DAYTON-PHILLIPSBURG AIRPORT INVOLVING AIRCRAFT REGISTRATION N75SA, A CIRRUS SR22, SERIAL NUMBER 0955. THE PILOT-IN-COMMAND (PIC) LOST CONTROL OF THE AIRCRAFT DURING THE LANDING PHASE AND ALLOWED THE AIRCRAFT TO DEPART THE CENTERLINE OF RUNWAY 21 AFTER INITIAL TOUCHDOWN AND BAULKED LANDING AT THE K3I7 AIRPORT. THE PIC STATED HE WAS ATTEMPTING A SHORT FIELD LANDING AND EXPERIENCED A HARD LANDING ON RUNWAY 21. AFTER THE HARD LANDING, THE AIRCRAFT BOUNCED BACK INTO THE AIR AND THE PIC STATED HE ATTEMPTED TO PERFORM A GO AROUND BUT THE AIRCRAFT HAD INSUFFICIENT ENERGY TO GAIN ALTITUDE DESPITE ADDING FULL THROTTLE POWER. THE PIC STATED THE AIRCRAFT VEERED TO THE LEFT, DESCENDED, AND CAME TO A STOP ON THE GRASS PARALLEL TO RUNWAY 21. THE PIC WAS THE ONLY PERSON ONBOARD THE AIRCRAFT AND NO INJURIES WERE REPORTED. THE AIRCRAFT SUSTAINED MINOR DAMAGE. THE PIC OF THE FLIGHT^PRIVACY DATA OMITTED^ WHO INDICATED HE WAS CONDUCTING A SOLO FLIGHT IN ACCORDANCE WITH 14 CFR PART 91. THE PIC HAD DEPARTED THE KBAK AIRPORT EARLIER THE SAME DAY AT APPROXIMATELY 1002 EDT AND WAS PERFORMING A SOLO CROSS-COUNTRY FLIGHT IN THE INCIDENT AIRCRAFT. THE AIRCRAFT WAS PURCHASED APPROXIMATELY TWO MONTHS PRIOR TO THE INCIDENT AND THE PIC HAD BEEN RECEIVING FLIGHT INSTRUCTION IN THE AIRCRAFT SINCE HE LACKED EXPERIENCE IN A SIMILAR MAKE/MODEL OF AIRCRAFT. THE INCIDENT FLIGHT WAS THE FIRST FLIGHT THE PIC CONDUCTED IN THE INCIDENT AIRCRAFT WITHOUT HIS FLIGHT INSTRUCTOR ONBOARD. INSPECTORS INVESTIGATING THE INCIDENT DID NOT FIND ANY OTHER MECHANICAL ABNORMALITIES OF THE AIRCRAFT. THE FLIGHT WAS CONDUCTED UNDER VISUAL METEOROLOGICAL CONDITIONS AND NEITHER THE RUNWAY CONDITIONS NOR THE WEATHER CONDITIONS AT THE K3I7 AIRPORT WERE A CONTRIBUTING FACTOR OF THE INCIDENT. 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.