N412JP Pratt Ultravia Pelican-PL accident

NTSB NYC05LA119 · 2005-07-12 · Middlebury, VT · near 6B0

Docket — crew, injuries and powerplant

Summary

About five months prior to the accident, the pilot installed a new engine in the homebuilt airplane. The engine was a 138-horsepower conversion of a Subaru automobile engine, and had accumulated about 13 hours of operation until the time of the accident. On the day of the accident, no anomalies were noted during the preflight inspection, start-up, or taxi. The engine normally operated about 5,700 rpm, with the propeller turning about 2,500 rpm. During the takeoff roll, the propeller rpm was at 2,000, and the pilot adjusted propeller pitch to increase the rpm to 2,500. Shortly after takeoff, the airplane experienced a partial loss of engine power, and the rpm dropped to approximately 1,500. There was not enough power remaining to return to the airport, so the pilot performed a forced landing, straight ahead, into trees. Examination of the engine, fuel system, ignition system, and propeller system did not reveal any pre-impact mechanical malfunctions.

Full narrative

On July 12, 2005, about 0815 eastern daylight time, a homebuilt Ultravia Pelican-PL amphibian, N412JP, was substantially damaged during a forced landing, following a partial loss of engine power while departing Middlebury State Airport (6B0), Middlebury, Vermont. The certificated commercial pilot was not injured. Visual meteorological conditions prevailed, and no flight plan was filed for the local personal flight conducted under 14 CFR Part 91.

The pilot stated that he completed construction of the airplane in 1999. The airplane had accumulated about 150 total hours of operation at the time of the accident. In addition, the pilot installed a new Ram Racing Engines EA81, 138-horsepower engine, in March, 2005. The engine was a conversion of a Subaru automobile engine, and had accumulated about 13 hours of operation at the time of the accident. Prior to the flight, the pilot performed a preflight inspection on the airplane, which included a check of both fuel tanks and the gascolator. The inspection revealed approximately 11 gallons of fuel on board, and no water or contamination was observed in the fuel.

The start-up, taxi, and takeoff roll were normal except that the propeller rpm was a "bit low" on takeoff. The engine normally operated about 5,700 rpm, with the propeller turning about 2,500 rpm. The pilot adjusted the propeller pitch to increase rpm from 2,000 to 2,500. Shortly after takeoff from 6B0, the airplane experienced a partial loss of engine power, and the rpm dropped to approximately 1,500. Since there was not enough power remaining to return to the airport, the pilot performed a forced landing, straight ahead, into trees.

The pilot further stated that he examined the wreckage, and did not find any mechanical malfunctions with the engine, fuel system, or ignition system. The airplane was equipped with a three-bladed propeller that had a controllable pitch (approximately 11 degrees to 22 degrees) via a spring switch and electric motor. The pilot initially believed that the controllable pitch propeller went uncommanded to full cruise pitch during the initial climb. However, he subsequently tested the propeller, and determined that it worked correctly, and was in the "full fine" pitch position at the time of the accident.

Examination of the airplane by a Federal Aviation Administration inspector did not reveal any pre-impact mechanical malfunctions.

Probable cause

A partial loss of engine power for undetermined reasons. The National Transportation Safety Board determined the probable cause of this accident.

Circumstances

Event type
Accident
Highest injury
None
Weather conditions
Visual Meteorological Cond
Light condition
Day
Sky condition
NONE
Ceiling (ft)
0
Visibility (sm)
10
Wind direction
0
Temperature (F)
64
Nearest airport
Middlebury State Airport
Distance from field
1.0
Airport elevation
490

Aircraft

RegistrationMakeModelDamageFAR part
N412JP Pratt Ultravia Pelican-PL SUBS 091

Sequence of events

#OccurrencePhase
1 350 Cruise
2 180 Cruise
3 220 Cruise

Findings

Finding
25000 cause
20200