Accident Details
Probable Cause and Findings
The pilot's selection of unsuitable terrain for landing, and his failure to maintain control of the airplane, which resulted in a nose over during the landing roll. A factor contributing to the accident was uneven terrain.
Aircraft Information
Registered Owner (Current)
Analysis
On May 7, 2005, about 1330 Alaska daylight time, a tundra tire-equipped Piper PA-18 airplane, N9206Y, sustained substantial damage when it nosed over during the landing roll on a remote beach, about 66 miles east of Cordova, Alaska. The airplane was being operated as a visual flight rules (VFR) local area business flight under Title 14, CFR Part 91, when the accident occurred. The airplane was operated by the pilot who was a guide for Fejes Guide Service Ltd., Cordova. The commercial certificated pilot, the sole occupant, was not injured. Visual meteorological conditions prevailed. The flight originated from a lodge in the area, and no flight plan was filed, nor was one required.
During a telephone conversation with the National Transportation Safety Board (NTSB) investigator-in-charge (IIC), on May 8, 2005, the owner of the guide service reported that the pilot was landing on a beach, north-northwest of Midtimber Lake and the Seal River. The owner said the pilot told him that during the landing roll on a flat beach, the airplane encountered a bump in the terrain, and momentarily became airborne. When the airplane touched down again, the pilot applied the brakes and the airplane nosed over. The owner of the guide service stated that he did not know the purpose for the landing. The airplane received structural damage to the fuselage, wing lift struts, propeller and rudder.
In the Pilot/Operator Aircraft Accident Report, (NTSB Form 6120.1) submitted by the pilot, the pilot indicated that during the landing roll, the airplane rolled over an unseen bump, which caused the tailwheel to bounce high enough to cause the airplane to nose over.
Data Source
Data provided by the National Transportation Safety Board (NTSB). For more information on this event, visit the NTSB Records Search website. NTSB# ANC05LA072