Aviation Accident Summaries

Aviation Accident Summary MIA06LA019

Heathrow, FL, USA

Aircraft #1

N7453J

Piper PA-28R-180

Analysis

The airplane collided with trees, a house and then the ground during a forced landing following a loss of engine power. According to the pilot during the preflight inspection he noted the fuel level in the left tank to be nearly full, and the fuel level in the right tank to be slightly above the tab. He further stated that after several touch-and-go landings and one full stop landing at various airports, he proceeded back to Orlando Sanford International Airport (KSFB). During descent to KSFB, the engine went to idle and was operating rough, but did not lose power. The pilot recalls advancing the mixture control to full rich, verifying that auxiliary fuel pump was in the "on" position, and that the fuel selector valve was in the left tank position. After changing the fuel selector valve to the right tank position, which had no affect on engine performance, he trimmed the airplane for 80 knots and executed an emergency descent to landing on a small community road. The airplane impacted the roof of a house and trees during the landing. The fuel selector was found halfway between the right tank and one of the off detents. Fuel was found in the fuel strainer, fuel lines in the engine compartment, and fuel distributor valve. An operational test of the fuel selector valve in the "as found" position was performed by blowing air into the gascolator inlet; resistance was noted. The same test was then performed by blowing air into the gascolator inlet with the fuel selector positioned to each respective tank, no resistance was noted. No discrepancies with the engine were noted during the postaccident examination.

Factual Information

On November 15, 2005, about 2053 eastern standard time, a Piper PA-28R-180, N7453J, registered to Magic Interiors, collided with trees, the roof of a house, then the ground during a forced landing in a residential area near Heathrow, Florida. Visual meteorological conditions prevailed at the time and no flight plan was filed for the 14 CFR Part 91 personal, local flight from Orlando Sanford International Airport (KSFB). The airplane was substantially damaged and the commercial-rated pilot and one passenger sustained minor injuries. The flight originated about 1923, from Orlando Sanford International Airport. The pilot stated that during his preflight inspection of the airplane he noted the fuel level in the left and right fuel tanks were nearly full, and slightly above the tab, respectively. No contaminants were noted when examining each fuel tank and the fuel strainer. The engine was started with the fuel selector positioned to the right tank, and after engine start, he contacted air traffic control (ATC) and was cleared to taxi to runway 9R. He repositioned the fuel selector to the left tank and performed an engine run-up with no discrepancies reported. He was cleared for takeoff and remained in the traffic pattern for runway 9R where he performed 3 or 4 touch-and-go landings. After the last landing he exited the traffic pattern to the west and proceeded to Leesburg Regional Airport where he performed a full-stop landing on runway 31. He taxied back to runway 31, departed, and climbed to 1,000 feet. He exited the traffic pattern to the east and climbed to 2,000 feet where he reduced the throttle control to 23 inches manifold pressure and the propeller to 2,400 rpm. He also leaned the fuel/air ratio, and proceeded towards KSFB. When the flight was 9.8 miles from KSFB and near Orlando Class B airspace, he established contact with KSFB ATCT. The controller advised him to contact them when the flight was 3 miles away but the controller contacted him before then and advised of nearby traffic. He descended to 1,500 feet and approximately 1 minute later, the engine went to idle and was operating rough but did not quit. He immediately looked at the oil pressure and temperature gauges and noted both indications were in the green arc. He did not recall looking at the tachometer or the fuel flow gauge at the time of the loss of engine power. The pilot further stated he could not recall the sequence but he "worked" the throttle control which only momentarily corrected the loss of engine power. The engine did hesitate/sputter each time he increased the throttle control. He placed the mixture control to full rich, and verified the auxiliary fuel pump was in the "on" position, and the fuel selector was on the left tank position. The fuel pump and fuel selector had been unchanged from the moment of takeoff at KSFB. He repositioned the fuel selector to the right tank which had no affect, and verified the ignition switch was in the "both" position; he did not check the magnetos. He trimmed the airplane to maintain 80 mph, and looked for a place to land. He saw I-4, but knew because of his altitude that was not an option. At 500 feet he observed lights and saw a small road in a community that was located to his left. He reported that the landing gear extended automatically which occurred because of a decrease in engine rpm, and headed towards the road. He was committed to a landing on the road and began a turn to line up parallel. Looking to the side of the airplane as he turned, he saw a tree dead ahead covered by the darkness. He banked to avoid the tree, but knew impact with the tree would occur. The airplane impacted trees, he closed his eyes, and could not recall the ground impact. He and the passenger unbelted their seatbelts, and exited the airplane; he experienced no difficulty exiting the airplane. Post accident examination of the wreckage by an FAA airworthiness inspector revealed that both wings were separated at the wing roots. The left wing was located close to the main wreckage of the aircraft and was dripping fuel from a fractured fuel line, which the local fire department attempted to stop by plugging the line. The right wing was located in a tree and did not appear to contain any fuel. The fuel selector was found halfway between the right tank and one of the off detents and did not show any signs of impact damage. No fuel stains were noted aft of either fuel cap or on the bottom skin of either wing and no fuel contamination was found. Fuel was found in the fuel strainer. The ignition switch was found in the both position, and the throttle, mixture, and propeller controls were found connected, in the full forward positions, with no binding noted. An operational test of the fuel selector valve in the "as found" position was performed by blowing air into the gascolator inlet line; resistance was noted. Air was then blown into the gascolator inlet line with the fuel selector placed to the left and right positions; no resistance was noted. Post accident testing of the engine and fuel system by an FAA inspector revealed the air induction system was free of obstructions and the engine oil quantity was full. Fuel was noted in flexible fuel lines in the engine compartment and also in the fuel distributor valve. Crankshaft, camshaft, and valve train continuity was confirmed. Suction and compression was noted to all cylinders, and spark was noted at all spark plugs during engine rotation. With battery power applied, the auxiliary fuel pump was activated and fuel flow was noted from all fuel injector nozzles. The passenger in the airplane is the holder of a restricted FAA issued foreign based private pilot certificate with airplane single engine land rating. At the time of the accident she was reportedly seated in the right front seat with access to flight controls; the pilot-in-command reported she did not touch the flight controls at any time during the flight. The NTSB requested through the pilot's attorney to have the passenger complete the "Second Pilot Information" blocks on the NTSB "Pilot/Operator Aircraft Accident Report" form, and also to prepare a detailed statement. The request was not complied with.

Probable Cause and Findings

A partial loss of engine power due to undetermined reasons resulting in a forced landing in a residential area.

 

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