Aviation Accident Summaries

Aviation Accident Summary ERA09LA143

Everglades City, FL, USA

Aircraft #1

N1006J

AERO COMMANDER 112A

Analysis

During takeoff, at approximately 15 feet above the ground, the engine lost partial power, and the airplane descended back down to the runway. The pilot tried to get airborne again; however, the airplane touched down hard, bounced, and traveled off the end of the runway into a mangrove swamp. Examination of the airplane by a Federal Aviation Administration inspector revealed that no flight control anomalies were found. During a post-accident examination, fuel was supplied to the engine and the engine was started. The engine ran at 1700 rpm with no anomalies noted. However, it could not be run any higher than 1700 rpm due to a bent propeller shaft that was damaged during the accident impact.

Factual Information

On January 25, 2009, at about 1450 eastern standard time, an Aero Commander 112A, N1006J collided with a mangrove swamp at the end of the runway, during takeoff from the Everglades Airpark, Everglades City, Florida. The certificated private pilot and the passenger received minor injuries and the airplane was substantially damaged. The airplane was operated as a personal flight under the provisions of 14 Code of Federal Regulations (CFR) Part 91. No flight plan was filed. Visual meteorological conditions prevailed for the flight to North Perry Airport, Hollywood, Florida. The pilot stated that after run-up, he taxied to the departure end of runway 33. All engine indications were normal when he began the takeoff roll. He said that about halfway down the runway, the airplane lifted off and climbed out at 75 knots. Approximately 15 feet above the ground, the engine lost partial power, and the airplane descended to the runway. The pilot said he tried to get airborne again; however, the airplane touched down hard, bounced, and traveled off the end of the runway into a mangrove swamp. Examination of the airplane by a Federal Aviation Administration inspector revealed that no flight control anomalies were found. A cursory examination of the engine revealed that it had minimal external damage and was able to be run. The fuel was examined prior to the engine run and no contaminates were noted in the fuel. The propeller shaft was bent, and the damaged propeller blades were cut to facilitate the engine run. Fuel was supplied to the engine and the engine was started. The engine ran up to 1700 rpm with no anomalies noted. However, it could not be run any higher due to the violent shaking of the bent propeller shaft.

Probable Cause and Findings

The partial loss of engine power for an undetermined reason. Contributing to the accident was the pilot's attempt to continue takeoff with partial engine power.

 

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