Skip to content

SEA05LA076

2005-04-16 · Plant City, Florida, United States · None · 1 aircraft · Status: Completed

Airport PCM

N33CF has since been reassigned. It is now registered to a different aircraft (CIRRUS DESIGN SR22, built 2022), which was not involved in this event.

Aircraft involved

Probable cause & findings

An engine power interruption during takeoff for undetermined reasons.

Factual narrative

On April 16, 2005, about 1755 eastern daylight time, a Beech A36 Bonanza airplane, N33CF, sustained substantial damage following a collision with terrain shortly after takeoff from the Plant City Municipal Airport, Plant City, Florida. The airplane is owned by the pilot, and was being operated as a visual flight rules (VFR) cross-country flight under the provisions of Title 14, CFR Part 91, when the accident occurred. The airline transport pilot, and the five passengers aboard the airplane, were not injured. Visual meteorological conditions prevailed, and no flight plan was filed for the cross-country flight. The pilot's planned destination was Rock Hill (York County) Airport, Rock Hill, South Carolina. During a telephone conversation with the NTSB IIC on April 16, the pilot reported the takeoff roll was normal; however shortly after takeoff during the climb he noted a reduction in the climb performance at takeoff power. He stated the airplane began to settle, eventually impacting terrain in a tail-low attitude. In a written statement, dated April 21, the pilot reported that shortly after retracting the landing gear, during the initial climb out, the engine began to run rough and lose power. The pilot reported that he cycled the fuel boost pump to the low position; however, "no change in power" was noted. The pilot further reported that "…there was a question as to whether the airplane would clear the trees and [I] did not know what was on the other side - so I elected to set the airplane in a field on the airport property." The airplane was powered by a Teledyne Continental IO-550-B engine rated at 300-horsepower. The engine was equipped with, among other things, a Tornado Alley Turbo Whirlwind turbonormalizing package. The airplane was equipped with a J.P. Instruments EDM 700 engine monitoring system. The configuration found in the aircraft recorded, in part, exhaust gas temperature (EGT), cylinder head temperature (CHT), turbine inlet temperature (TIT), oil temperature (OIL) and fuel flow (FF) in gallons per hour. These parameters were recorded using a 6 second sample rate. The system was removed from the wreckage and shipped to J.P. Instruments, Costa Mesa, California, to facilitate data extraction and readout. Data from 24 individual flights, the accident flight and 23 previous flights, were downloaded from the unit's internal digital memory chip. The data file corresponding with the accident flight (file number 55) contained approximately 2.7 minutes of data. The unit began logging engine data at 21:41:16 (when the avionic bus was powered) and the last data entry was recorded at 21:43:58. Comparison evaluation of the data from the accident flight and the most recent flight prior to the accident revealed no significant data influxes or anomalies between the two flights. The EGT's, CHT's, FF and TIT's values recorded on the accident flight were consistent with the values recorded on the previous flight. Representatives from Tornado Alley Turbo, Inc, reviewed the data and reported that the engine values from the accident flight were consistent with normal engine operations and no different from the values found in identically equipped and configured engine installation. Post accident engine examination by representatives from Teledyne Continental Motors and the Federal Aviation Administration revealed no evidence of a mechanical malfunction that would have contributed to a loss of engine power. In a post inspection written report from Teledyne Continental Motors, dated November 29, the representative conducting the engine examination stated, "The inspection of this modified engine did not reveal any visual abnormalities that would have prevented normal operation and production of rated horsepower." The pilot reported the takeoff roll was normal; however shortly after takeoff during the climb he noted a reduction in the climb performance at takeoff power. He stated the airplane began to settle, eventually impacting terrain in a tail-low attitude. The pilot and the five passengers aboard the airplane were not injured and were able to exit the airplane without assistance. Post accident examination of the engine revealed no evidence of a mechanical malfunction that would have contributed to a loss of engine power. Downloaded data for the airplane's engine monitoring system revealed no evidence of an engine anomaly. Data from the accident flight were consistent with normal engine operations and no different from the values found in identically equipped and configured engine. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12

Verbatim from NTSB's published report. Source file NTSB_2005_SEA05LA076.txt. Findings + structured fields enriched from FAA avall.mdb. Full investigation docket on data.ntsb.gov ↗.

Related research

Matched on aircraft type or causal vocabulary (stall). All research papers