CRAWFORDSVILLE, IN, USA
N3298X
CESSNA 310L
THE PILOT TOOK OFF WITH THE INTENTION OF REMAINING IN THE AIRPORT TRAFFIC PATTERN TO PRACTICE THREE TAKEOFFS AND LANDINGS. THE PILOT STATED THAT HE DECIDED TO PRACTICE A POWER OFF LANDING FIRST. DURING THE FIRST LANDING THE PILOT HAD TO ADD POWER TO MAKE IT TO THE RUNWAY. DURING THE SECOND LANDING, THE PILOT STATED HE FLEW A TIGHTER PATTERN. WHILE ON FINAL APPROACH, HE HAD TO REALIGN THE AIRPLANE WITH THE RUNWAY. AT THIS POINT, THE AIRSPEED DROPPED RAPIDLY AND HE DECIDED TO PERFORM A GO AROUND. THE PILOT STATED THE LEFT WING IMPACTED THE RUNWAY, BUT HE HAD TO CONTINUE WITH THE GO AROUND DUE TO TRAFFIC. THE PILOT STATED A THIRD PATTERN WAS DONE USING NORMAL PROCEDURES AND HE LANDED THE AIRPLANE WITH NO FURTHER INCIDENT.
On June 24, 1995, at 1940 eastern daylight time, a Cessna 310L, N3298X, registered to the Engineering & Design Services, Inc., of West Layfayette, Indiana, was substantially damaged while landing at Crawfordsville Municipal Airport, Crawfordsville, Indiana. The pilot and two passengers reported no injuries. The airplane was being operated as a personal flight under 14 CFR Part 91 when the accident occurred. Visual meteorological conditions prevailed at the time and no flight plan was filed. The pilot reported the flight was to be a proficiency flight. His intention was to stay in the airport traffic pattern and practice three takeoffs and landings. For his first landing, the pilot stated he decided to practice a power off landing. While on the downwind leg of the traffic pattern, he pulled both throttles to the idle position. "First landing was firm but decent, only I had to bring power in momentary on the base to make the runway," the pilot stated. The second pattern, he stated, was done without any addition of power, but he had to "...close in on the runway in order to make the runway... ." While on final to land, the pilot stated that he had to realign the airplane with the runway. He stated that at this point the airspeed dropped quickly, and he realized a "bad" situation. The pilot decided to perform a go around. "Abort was to late and I contacted the ground and dragged the left wing - abort was continued due to ground traffic directly ahead," the pilot stated. The third pattern was done using normal procedures and he landed the airplane with no further incidents.
the pilot's failure to maintain adequate airspeed during final approach to landing. A factor in the accident was the pilot's delayed action of aborting the landing.
Source: NTSB Aviation Accident Database
Aviation Accidents App
In-Depth Access to Aviation Accident Reports
