Summary
On August 14, 2002, a Piper PA-32-260 (N3853W) was involved in an accident near Red Devil, AK. The accident resulted in 3 minor injuries. The aircraft sustained substantial damage.
The National Transportation Safety Board determined the probable cause of this accident to be: A partial loss of engine power for an undetermined reason during the initial climb after takeoff that resulted in a collision with trees. A contributing factor in the accident was rising terrain which was unsuitable for a forced landing.
On August 13, 2002, about 1600 Alaska daylight time, a wheel-equipped Piper PA-32-260 airplane, N3853W, sustained substantial damage when it collided with trees along a ridgeline following a partial loss of engine power after takeoff from Red Devil, Alaska. The airplane was being operated as a visual flight rules (VFR) cross-country business flight under Title 14, CFR Part 91, when the accident occurred. The airplane was operated by the pilot. The commercial certificated pilot, and the two passengers, received minor injuries. Visual meteorological conditions prevailed. The intended destination was Stony River, Alaska.
On August 15, 2002, the pilot notified the National Transportation Safety Board's (NTSB) Northwest Field Office of the accident.
This accident is documented in NTSB report ANC02LA095. AviatorDB cross-references NTSB investigation data with FAA registry records to provide comprehensive safety information for aircraft N3853W.
Accident Details
Probable Cause and Findings
A partial loss of engine power for an undetermined reason during the initial climb after takeoff that resulted in a collision with trees. A contributing factor in the accident was rising terrain which was unsuitable for a forced landing.
Aircraft Information
Registered Owner (Historical)
Analysis
On August 13, 2002, about 1600 Alaska daylight time, a wheel-equipped Piper PA-32-260 airplane, N3853W, sustained substantial damage when it collided with trees along a ridgeline following a partial loss of engine power after takeoff from Red Devil, Alaska. The airplane was being operated as a visual flight rules (VFR) cross-country business flight under Title 14, CFR Part 91, when the accident occurred. The airplane was operated by the pilot. The commercial certificated pilot, and the two passengers, received minor injuries. Visual meteorological conditions prevailed. The intended destination was Stony River, Alaska.
On August 15, 2002, the pilot notified the National Transportation Safety Board's (NTSB) Northwest Field Office of the accident. The pilot reported that during the initial climb after takeoff, as he was making a crosswind to downwind turn, the engine began to run rough and lose power. The airplane was unable to maintain altitude and collided with trees about 1.5 miles from the airport.
The Red Devil Airport is located along the banks of the Kuskokwim River. Rising terrain is located on each side of the river valley. The FAA's Airport/Facility Directory, Alaska Supplement, airport remarks for the Red Devil Airport, states, in part: "Airport remarks, Unattended. Caution: Runway condition not monitored, recommend visual inspection prior to using. One-half inch of loose gravel on runway surface. Grass growing in the west 2,000 feet of runway 09/27."
Following the accident, the airplane was recovered to the Red Devil Airport, but no further. Due to the remoteness of the area, a postaccident examination of the engine was not conducted by the owner, insurance company, or the Safety Board.
The closest official weather observation station is the Sparrevohn Long Range Radar Station (LRRS), Sparrevohn, Alaska, which is located 66 nautical miles east-southeast of the accident site. At 1555, an automated weather observation system (AWOS) was reporting in part: Wind, 250 degrees (true) at 5 knots; visibility, 10 statue miles; clouds and sky condition, 4,700 feet scattered; temperature, 59 degrees F; dew point, 39 degrees F; altimeter, 30.25 inHg.
Data Source
Data provided by the National Transportation Safety Board (NTSB). For more information on this event, visit the NTSB Records Search website. NTSB# ANC02LA095