# Incident 20200513003449I: Piper PA-28RT-201, Lakeville, MN, May 13, 2020 - Type: FAA incident report (Accident/Incident Data System), as reported - Date: May 13, 2020, 13:30 local time - Place: Lakeville, MN - Airport: Airlake - Damage: Minor damage - Phase of flight: Landing: Touchdown - Operating rules: Pilot school (Part 141) - Operator: TBDS - Location: 44.6279° N, 93.2281° W: Placed by OpenAirDocs at AIRLAKE (LVN), within about a mile (OpenAirDocs) - Nearby events: https://openairdocs.org/map.md?lat=44.6279&lon=-93.2281&mi=10 - Aircraft: N8265S, registered now (https://openairdocs.org/aircraft/N8265S) (OpenAirDocs) - Registry model: Piper PA-28RT-201 (registry code 7102818, https://openairdocs.org/model/piper-pa-28rt-201) (OpenAirDocs) - Registry engine: Lycoming I0360 SER A&C (registry code 41511, https://openairdocs.org/engine/lycoming-i0360-ser-a-c) (OpenAirDocs) - Reported make and model: PIPER PA-28RT-201 - Reported engine: LYCOMING I0360 SER A&C - People aboard: 2 - Fatal injuries: 0 - Other injuries: 0 - Pilot certificates: Commercial pilot, flight instructor, private pilot - Pilot flight hours: 927 total, 75 in this make and model, 74 in the last 90 days - FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/) - Page: https://openairdocs.org/incident/20200513003449I ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. 2020-05-13 PIPER ARROW N8265S HAD A GEAR UP LANDING AT AIRLAKE KLVN. AFTER LANDING AT 1 A.M. THE PIC/CFI WENT HOME AND CAME BACK TO WORK AT 0800L TO FACILITATE HIS MANAGER DUTIES. THE PIC HAD AN 1100L BRIEF WITH A STUDENT THAT WAS NOT ONE OF HIS REGULARS. THE STUDENT WAS EXPERIENCING SOME KNOWN TRAINING CHALLENGES AND SO THE PLAN OF THE DAY WAS TO WORK ON LAZY 8'S. THE STUDENT STRUGGLED, BUT MANEUVER COMPLETE, THE STUDENT ASKED FOR HELP WITH THE 180 POWER OFF. THE AIRCRAFT PROCEEDED TO KLVN, THE STUDENT PERFORMED ONE LANDING TO A FULL STOP. THE NEXT LANDING WAS TO BE A 180 POWER OFF. THE CFI STATES THAT PRIOR MANEUVER PERFORMANCE HAD HIM FOCUSING VERY MUCH ON THE STUDENTS AIRSPEED THROUGH THE LEFT TURN TO FINAL, AND BELIEVES THIS COMBINED WITH FATIGUE, HE WAS NOT ON HIS A-GAME AND DID NOT PERFORM HIS 180/BASE/AND FINAL GEAR CHECKS. HE DOES NOT RECALL HEARING A GEAR WARNING HORN. HE DID NOTICE THAT THE AIRPLANE WAS FLOATING DOWN THE RUNWAY AND WAS GETTING READY TO TAKE CONTROLS FOR GO-AROUND WHEN THE FBO RADIO CALL STATING CHECK GEAR WAS HEARD. THE PIC EXECUTED THE GO-AROUND, PROP STRIKES WITH MINIMAL BEND, TAIL SKID SCRAPE AND INBOARD PORTION OF LEFT FLAP HAD DAMAGE. THE AIRCRAFT HAD A NORMAL TAKEOFF, NO ABNORMAL VIBE, LOWERED THE GEAR AND CAME BACK FOR FULL STOP WITH THE PIC AT CONTROLS. AIRCRAFT WAS HANGARED AT KLVN FOR MAINTENANCE WORK. ## Other reports on N8265S (4) Matched to the same aircraft by N-number and date. - [Incident 20110629014549I](https://openairdocs.org/incident/20110629014549I), Jun 29, 2011: Piper PA-28RT-201 (N8265S), Maple Lake, MN, Minor damage. Lake airport, Minnesota. During the landing flare, [privacy data omitted] hard the propeller strike the ground and realized had had not lowered the landing… - [Incident 20050930033519I](https://openairdocs.org/incident/20050930033519I), Sep 30, 2005: Piper PA28RT201 (N8265S), Glencoe, MN, Minor damage. (-23) The pilot flight instructor [privacy data omitted] administered a complex aircraft checkout to private pilot [privacy data omitted] at the Glencoe… - [Incident 20030305003159I](https://openairdocs.org/incident/20030305003159I), Mar 5, 2003: Piper PA28RT201 (N8265S), Tecumseh, NE. (-23) On 3/6/2003 at approximately 1620 cmt on flight from flying cloud airport minneapolis MN. (Fcm) to do some recreational sight seeing, and two hour into… - [Incident 19991020032369I](https://openairdocs.org/incident/19991020032369I), Oct 20, 1999: Piper PA28RT201 (N8265S), Clear Lake, MN, Minor damage. (-23) The airplane started shaking during cruise. The PIC headed for a grass strip nearby. He saw a cylinder break through the cowling. He estimated that they… 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.