# Incident 20100421037719I: Cirrus Desi SR20, Hutchinson, KS, April 21, 2010 - Type: FAA incident report (Accident/Incident Data System), as reported - Date: April 21, 2010, 14:35 local time - Place: Hutchinson, KS - Airport: Hutchinson Municipal Airport - Damage: Minor damage - Phase of flight: Landing: Touchdown - Operating rules: General operating rules (Part 91) - Location: 38.0662° N, 97.8605° W: Placed by OpenAirDocs at HUTCHINSON RGNL (HUT), within about a mile (OpenAirDocs) - Nearby events: https://openairdocs.org/map.md?lat=38.0662&lon=-97.8605&mi=10 - Aircraft: N620DA, registered now (https://openairdocs.org/aircraft/N620DA) (OpenAirDocs) - Registry model: Cirrus Design SR20 (registry code 2130000, https://openairdocs.org/model/cirrus-design-sr20) (OpenAirDocs) - Registry engine: Continental IO-360-ES (registry code 17160, https://openairdocs.org/engine/continental-io-360-es) (OpenAirDocs) - Reported make and model: CIRRUS DESI SR20 - Reported engine: CONT MOTOR IO-360-ES - People aboard: 1 - Fatal injuries: 0 - Other injuries: 0 - Pilot certificates: Student - Pilot flight hours: 84 total, 60 in this make and model, 60 in the last 90 days - FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/) - Page: https://openairdocs.org/incident/20100421037719I ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. ON APRIL 21, 2010, AT APPROXIMATELY 1435 LOCAL TIME, A STUDENT PILOT WAS INVOLVED IN AN AIRCRAFT INCIDENT WHILE LANDING AT THE HUTCHINSON MUNICIPAL AIRPORT (KHUT), HUTCHINSON, KANSAS. THE AIRCRAFT INVOLVED IN THIS INCIDENT IS A CIRRUS SR-20, WHICH IS OWNED AND OPERATED BY A LOCAL FLIGHT SCHOOL. VISUAL METEOROLOGICAL CONDITIONS (VMC) EXISTED AT THE TIME OF THE INCIDENT; THE AIRCRAFT WAS LANDING ON RUNWAY 17. IMMEDIATELY BEFORE THIS INCIDENT OCCURRED, THE AIRMAN HAD PERFORMED 3 FULL-STOP LANDINGS WITH THE CERTIFIED FLIGHT INSTRUCTOR. AFTER THIS DUAL FLIGHT, THE AIRMAN DEPARTED TO CONDUCT 3 FULL-STOP LANDINGS AS THE SOLO PILOT; THIS WAS THE AIRMAN'S SECOND SOLO FLIGHT. THE FIRST LANDING WAS PERFORMED IN A SATISFACTORY MANNER. HOWEVER, DURING THE SECOND APPROACH TO LANDING ON RUNWAY 17, THE AIRMAN STATED THAT UPON EXECUTING A NORMAL TOUCHDOWN, THE AIRCRAFT IMMEDIATELY BECAME AIRBORNE AND STARTED TO PORPOISE. THE AIRMAN ELECTED TO CONDUCT A GO-AROUND BY ADVANCING FULL POWER AND RAISING THE FLAPS TO THE 50 % POSITION. PER THE AIRMAN'S STATEMENT, DUE TO THE AIRCRAFT NOT PERFORMING AS DESIRED, THE GO-AROUND WAS ABORTED. DURING THE TIME THAT THE AIRMAN ELECTED TO GO-AROUND UNTIL THE TIME THAT IT WAS REJECTED, THE AIRCRAFT ROLLED RIGHT CAUSING THE RIGHT WINGTIP TO CONTACT THE RUNWAY. A SUBSEQUENT UNCOORDINATED ROLL TO THE LEFT ENSUED CAUSING THE LEFT HORIZONTAL STABILIZER TO ALSO CONTACT THE RUNWAY. THE RELATIVELY HIGH PITCH ATTITUDE THAT WAS ESTABLISHED IN THE ATTEMPTED GO-AROUND DAMAGED THE PLASTIC TAIL TIE-DOWN ON THE LOWER PORTION OF THE EMPENNAGE. THE AIRMAN EVENTUALLY REGAINED CONTROL; HOWEVER, DURING THE ROLLOUT, DEPARTED THE END OF THE RUNWAY SURFACE, STRIKING TWO RUNWAY END LIGHTS WITH THE PROPELLER. A POST-INCIDENT INSPECTION OF THE AIRCRAFT CONFIRMED THE MINOR DAMAGE SUSTAINED DURING THE LANDING AND ATTEMPTED GO-AROUND; HOWEVER, THE AIRCRAFT'S FLAPS WERE DISCOVERED IN THE UP POSITION. THE STUDENT PILOT WAS UNINJURED IN THIS INCIDENT. ## Other reports on N620DA (2) Matched to the same aircraft by N-number and date. - [Incident 20090815015029I](https://openairdocs.org/incident/20090815015029I), Aug 15, 2009: Cirrus SR20 (N620DA), Hutchinson, KS, Minor damage. (-23) Cirrus N620DA had been making consecutive touch and go landings to runway 17 at Hutchinson muni (hut). Weather was clear below 10,000 MSL and wind was… - [Incident 20090107000029I](https://openairdocs.org/incident/20090107000029I), Jan 7, 2009: Cirrus SR20 (N620DA), Hutchinson, KS, Minor damage. While on a solo flight in the local traffic pattern the student pilot failed to maintain control of the aircraft during landing on runway 17. Evidence… 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.