NTSB Factual Report

On July 18, 2003, approximately 1515 central daylight time, a Beech 35-A33 single-engine airplane, N44CN, was substantially damaged during a forced landing following a loss of engine power during a go-around at the Hicks Airfield Airport (T67), near Fort Worth, Texas. The airplane was registered to and operated by a private individual. The commercial pilot and two passengers sustained minor injuries and one passenger sustained serious injuries. Visual meteorological conditions prevailed and a flight plan was filed for the 14 Code of Federal Regulations Part 91 personal flight. The 159.3 nautical miles cross-country flight originated from the A. L. Mangham Jr. Regional Airport (OCH), near Nacogdoches, Texas, approximately 1330.

According to the Pilot/Operator Aircraft Accident Report (NTSB Form 6120.1/2), the 1,834-hour pilot, who reported having accumulated 9 hours in the accident aircraft, stated that during the preflight inspection, he found no deficiencies and confirmed about 1.1 hours of fuel consumed from the 80 gallons aboard from the previous flight. The pilot stated that enroute, the engine performance "appeared normal," however, he stated that air traffic control (ATC) communications became difficult. He reported to have had intermittent radio trouble with Houston Air Route Traffic Control Center and Waco Approach Control. The pilot contacted Fort Worth Flight Service Station and obtained a frequency for Dallas/Fort Worth (DFW) Regional Approach Control. He received a new frequency, squawk and an assigned heading and altitude.

The pilot reported that he experienced intermittent radio contact with DFW Regional Approach Control, and heard a loud "buzzing" noise in his headset. At this time, the fuel gages "showed" a sudden change, indicating low fuel. The pilot announced to DFW Regional Approach Control (in the blind) that he had lost radio contact and would proceed directly to T67, in accordance with the flight plan. He heard no response from DFW. The pilot configured the airplane for an approach to Runway 32. As he continued the approach, he stated that he visually confirmed that the flaps were extended but the landing gear had not fully extended.

The pilot elected to initiate a go-around. He "pushed" all of the power controls forward; however, he heard the engine "sputter" and reported that it did not produce enough power to induce a positive rate of climb. He flew the airplane towards the west to avoid colliding with the airport hangars. At this time he switched fuel tanks and checked the "boost pump on" but still did not attain adequate power or a significant climb rate. The pilot elected to execute an off airport landing. The aircraft came to rest between two railroad tracks, and the pilot stated that he closed all engine controls, shut off the fuel, and shut off all electrical switches. All four occupants were able to evacuate the aircraft.

An examination of the airplane, by the FAA inspector who responded to the accident site revealed that the right wing and the fuselage was buckled. The propeller was bent aft. The landing gear was found in the retracted position, and the landing gear control switch was found in the gear down position. The battery was removed and a gravity test was performed. The results were that the battery was "dead." The alternator was removed, tested for function, and passed. A total of 31.5 gallons of fuel was removed from the aircraft. The mixture control was found halfway between the full-rich and cut-off position. The owner stated in a written statement provided to the Investigator-In-Charge, "the engine roughness was due to the pilot's failure to push the mixture control to the full-rich position prior to the approach/landing."

NTSB Probable Cause

The loss of engine power due to the pilot's improper use of the mixture control. Contributing factors were the pilot's failure to select the battery/alternator circuit, resulting in a loss of battery power, the pilot's failure to follow a checklist and the lack of suitable terrain for landing.