Aviation Accident Summaries

Aviation Accident Summary MIA08LA156

Peachtree City, GA, USA

Aircraft #1

N227RD

DIAMOND DA-20-C1

Analysis

Maintenance was performed to the airplane's rudder system and the operator requested a test flight. During the test flight the pilot noted no discrepancies with the airplane until the downwind to base turn; the engine would not produce full power. The pilot elected to perform a forced landing in an open field prior to the runway to avoid impacting trees that were in the flight path to the threshold. The terrain was full of debris, resulting in substantial damage to the airplane. The wreckage examination revealed no discrepancies with the airplane's flight control systems. The examination discovered that a check valve from the engine mechanical fuel pump return hose line back to the fuel tank was installed incorrectly (backwards). The engine was test run with the check valve installed both correctly and incorrectly. During both test phases, the engine accelerated normally without any hesitation or interruption in power. No discrepancies were noted that would have prevented the engine from producing power for normal flight operations.

Factual Information

On August 1, 2008, at 1450 eastern daylight time, a Diamond DA-20-C1, N227RD, incurred substantial damage during a forced landing following a partial loss of engine power, near the Peachtree City Airport-Falcon Field (FFC), Atlanta, Georgia. The certificated private pilot and the passenger received minor injuries. Visual meteorological conditions prevailed and no flight plan was filed. The airplane was operated by Falcon Aviation Academy, under the provisions of Title 14 Code of Federal Regulations Part 91 as a local maintenance test flight. The airplane’s rudder cables were scheduled for replacement as required by the manufacturer maintenance program. The airplane’s fuel tank was removed to gain access to the cables. The cables were replaced and the fuel tank was installed. All of the required functional test and leak checks were completed as required in the maintenance manual; with no discrepancies noted. The operator’s maintenance representative wanted to have the airplane flown in the airport traffic pattern once to ensure the airplane’s rudder system was working properly before putting it back into service for the academy. The pilot stated that he was requested to conduct the post maintenance test flight by the operator’s representative. The pilot did not observe any deficiencies with the airplane during the preflight inspection. The fuel gage reading coincided with the dip stick reading of half a tank during the fuel check. There were no abnormalities noted during the start up, taxi, and pre-takeoff run up. The airplane's climb rate was 700 to 800 feet per minute after the takeoff. The throttle was maintained at full takeoff power during the upwind, crosswind, and the left downwind. Once the airplane was 45 degrees abeam to the approach end of the landing runway, the pilot reduced the engine power to a setting of 1,500 rpm. He extended the downwind an additional 1/2 -mile due to other traffic in the pattern. While turning for base, the pilot felt a little more power was needed to make the runway. By this time, he had started the descent from pattern traffic altitude of 1,000 feet above ground level and was about 1 1/2 miles away from runway 31. As he advanced the throttle, he noted the engine did not respond and observed the tachometer was indicating 800 rpm. He applied full power and the engine did not advance in rpm as he turned for final. The pilot did not recall at what altitude he was at but was aware the airplane was not going to reach the runway and elected to make a force landing in an open field. During the landing roll the airplane encountered cut tree debris, separating the empennage and engine from the fuselage before coming to a stop. The pilot and the passenger exited the airplane without assistance. At the time of the accident the pilot had a total flight time of 237 hours, which 60 of those hours were in the accident make and model airplane. The airplane had a total time of 2,807 hours at the time of the accident. The IO-240-B Teledyne Continental Motor engine had 547 hours since major overhaul and a total time in service of 2,538 hours. A wreckage examination was conducted with the airplane’s airframe and engine manufacturer, along with a representative from the operator; with Federal Aviation Administration oversight. No discrepancies were noted with the airplane’s flight control system that would have prevented normal operation. The examination discovered that a check valve from the engine mechanical fuel pump return hose line back to the fuel tank was install incorrectly (the arrow stamped on the valve, indicating the flow was backwards) to the fuel tank. The check valve was not removed during the removal and installation of the fuel tank, rather the hose itself was removed. The condition of the check valve was consistent with it being installed at time of the airplane’s assembly. The check valve has no time replacement requirements as per the airframe manufacturer. The airplane’s maintenance manual instructions for removing and installing the fuel tank does not have a step to check to insure the check valve is installed correctly. The check valve was removed and retained with the engine to be examined at Teledyne Continental Motors, Inc (TCM) facility. The engine was examined and test run at the TCM facility with National Transportation Safety Board oversight. Two test runs were conducted, one with the check valve installed correctly and the other with the check valve installed backwards. There were minimal parameter deviations during the tests. During both test phases, the engine accelerated normally without any hesitation or interruption in power. No discrepancies were noted that would have prevented the engine from producing power for normal flight operations.

Probable Cause and Findings

A partial loss of engine power for undetermined reasons.

 

Source: NTSB Aviation Accident Database

Get all the details on your iPhone or iPad with:

Aviation Accidents App

In-Depth Access to Aviation Accident Reports