# Incident 20060805016589I: Piper PA28140, Milton, FL, August 5, 2006 - Type: FAA incident report (Accident/Incident Data System), as reported - Date: August 5, 2006 - Place: Milton, FL - Airport: Milton T Field Airport - Damage: Minor damage - Phase of flight: Level Off Touchdown - Operating rules: General operating rules (Part 91) - Location: 30.6296° N, 87.0514° W: Placed by OpenAirDocs: center of Milton, FL, within about 6 miles (OpenAirDocs) - Nearby events: https://openairdocs.org/map.md?lat=30.6296&lon=-87.0514&mi=10 - Aircraft: N1364T, a cancelled registration (https://openairdocs.org/deregistered/N1364T-2021-07-17) (OpenAirDocs) - Registry model: Piper PA-28-140 (registry code 7102802, https://openairdocs.org/model/piper-pa-28-140) (OpenAirDocs) - Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs) - Reported make and model: PIPER PA28140 - People aboard: 1 - Fatal injuries: 0 - Pilot certificates: Student - Pilot flight hours: 49 total, 39 in this make and model, 10 in the last 90 days - FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/) - Page: https://openairdocs.org/incident/20060805016589I ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. (-23) DURING LANDING STUDENT PILOT FAILED TO MAINTAIN CONTROL. THE AIRCRAFT VEERED OFF THE RUNWAY WHICH RESULTED IN A PROP STRIKE AND MINOR DAMAGE TO THE NOSE GEAR AND COWLING. PILOT STATEMENT: ON 05 AUGUST 2006, I FLEW PA28-141 N1364T ON A LOCAL SOLO TO THE BEACH PRACTICE AREA. I NOTED NO DISCREPANCIES DURING THE AIRCRAFT PREFLIGHT AND DEEMED THE AIRCRAFT SAFE FOR FLIGHT. START UP, TAXI, AND RUN-UP WERE NORMAL WITH NO PROBLEMS NOTED. I TOOK OFF FROM RUNWAY 18 AT APPROXIMATELY 0845L AND PROCEEDED TO THE BEACH PRACTICE AREA. THE AIRCRAFT PERFORMED SUPERBLY DURING THE FLIGHT AND I REMAINED IN THE BEACH AREA FOR APPROXIMATELY 45 MINUTES AND PROCEEDED AS FAR EAST AS HURLBURT FIELD (HRT). AFTER LEAVING THE PRACTICE AREA, I PROCEEDED AS FAR EAST AS HURLBURT FIELD (HRT). AFTER LEAVING THE PRACTICE AREA, I PROCEEDED DIRECT TO MILTON (2R4) AND ENTERED THE PATTERN FOR A LANDING ON RUNWAY 18. THE WIND WAS CALM AND VISIBILITY WAS EXCELLENT. THE PATTERN WAS EXECUTED VERY WELL ALL THE WAY TO THE FINAL APPROACH. I RECEIVED A RADIO CALL FROM ANOTHER AIRCRAFT STATING THEY WERE GOING TO DEPART FROM RUNWAY 36 AFTER I LANDED, BUT THIS AIRCRAFT WAS NOT A FACTOR IN THE INCIDENT. THE APPROACH TO LANDING WAS EXCELLENT AND I REMEMBER FEELING VERY SATISFIED WITH THE WAY I WAS FLYING AND HOW THE AIRCRAFT WAS PERFORMING. OVER THE NUMBERS, I REDUCED POWER TO IDLE AND ENTERED GROUND EFFECT. AT THIS POINT, I FLARED THE AIRCRAFT AND IT PORPOISED AND CAME DOWN ONTO THE RUNWAY ON ALL THREE WHEELS AND BOUNCED BACK INTO THE AIR. I ESTIMATE THE AIRCRAFT GAINED APPROXIMATELY 6-10 FEET IN ALTITUDE. AT THIS POINT, I SHOULD HAVE INPUT POWER AND ATTEMPTED A GO-AROUND. INSTEAD, I ATTEMPTED TO REDUCE THE FLARE AND TRIED TO BRING THE AIRCRAFT BACK DOWN. THIS WAS A MISTAKE AND SET INTO MOTION THE INCIDENT. IT IS AT THIS POINT THAT I BELIEVE I OVER-CORRECTED AND ACTUALLY NOSED THE AIRCRAFT OVER. THE AIRCRAFT IMPACTED THE RUNWAY VIOLENTLY AND BOUNCED BACK INTO THE AIR AND THIS WAS REPEATED APPROXIMATELY 2 TO 3 MORE TIMES, WITH EACH BOUNCE GAINING MORE ALTITUDE THAN THE FIRST. THOUGH THE LANDING GEAR WAS UNDOUBTEDLY DAMAGED AT THIS POINT, I STILL HAD AMPLE OPPORTUNITY TO CORRECT THE SITUATION BY ADDING POWER. ON THE LAST BOUNCE, THE AIRCRAFT LEFT THE RUNWAY, BOUNCED ON THE INFIELD, AND IMPACTED NOSE FIRST. AFTER COMING TO A BRIEF REST, THE AIRCRAFT FELL BACK ONTO THE LANDING GEAR. AFTER DETERMINING THERE WAS NO FIRE, I SHUT DOWN ALL THE AIRCRAFT SYSTEMS AND I EGRESS THE AIRCRAFT AS QUICKLY AND SAFELY AS POSSIBLE. I WAS MET IMMEDIATELY BY TWO GENTLEMAN WITH A FIRE EXTINGUISHER WHO OFFERED ASSISTANCE. I TOLD THEM I WAS OKAY AND THEY PROCEEDED TO THE FBO TO NOTIFY AMS OF THE INCIDENT. THIS IS A TRUE AND ACCURATE STATEMENT TO THE BEST OF MY KNOWLEDGE. ## Other reports on N1364T (2) Matched to the same aircraft by N-number and date. - [Incident 20050521008369I](https://openairdocs.org/incident/20050521008369I), May 21, 2005: Piper PA28140 (N1364T), Milton, FL, Minor damage. (-23) Pilot stated he landed in monroeville al and then upon take off he heard a loud bang but everything seemed ok, he departed for Milton, FL then upon… - [Incident 19980608012579I](https://openairdocs.org/incident/19980608012579I), Jun 8, 1998: Piper PA28140 (N1364T), Milton, FL, Minor damage. During flight instruction on June 8, 1998 the flight instructor stated at about 300 feet after the third take off and landing it felt like a load shifted in… 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.