DECATUR, AR, USA
N3424B
Beech D35
The pilot stated that he made visual contact with the destination airport when he was 'several miles out.' He flew a left base for runway 31, close in, and hurried to get things set up for the turn to final. On short final, he noticed that the airplane was extremely fast, and as the airplane approached the runway, the pilot remarked to his passenger that 'something was not right.' He then noticed that the landing gear handle was in the retracted position and initiated a go-around. Simultaneously, he heard scraping as if the airplane had contacted the runway. The pilot stated that he believes 'the prop hit the runway.' During the go-around, the pilot noticed that the airplane would not maintain a positive rate of climb. The pilot initiated an approach to a field, but 'pulled the airplane up' to clear trees and, subsequently, the airplane stalled, impacted the ground, and came to rest upright.
On July, 15, 2000, at 1300 central daylight time, a Beech D35 airplane, N3424B, was substantially damaged when it impacted terrain during a go-around near Decatur, Arkansas. The commercial pilot, who was the registered owner and operator, and his passenger sustained minor injuries. Visual meteorological conditions prevailed for the 14 Code of Federal Regulations Part 91 personal flight, for which no flight plan was filed. The flight originated from Smith Field, Siloam Springs, Arkansas, approximately 1255, and was destined for the Crystal Lake Airport, Decatur, Arkansas. According to the pilot, the flight departed Siloam Springs for the eight nautical mile trip to Decatur. The pilot visually located the airport when he was "several miles out." He stated that he was "in a left base, close in, and hurried to get things set up for the turn to final. On short final, [he] noticed [they] were extremely fast, and as [they] got closer to the runway, remarked that things were not right." He then noticed that the landing gear handle was in the retracted position, and he had not extended the landing gear. He initiated a go-around and simultaneously, he heard scraping as if the airplane had contacted the runway surface. The pilot stated that he believes "the prop hit the runway." The pilot further stated that the airplane responded when he "jerked back on the controls, but the engine did not develop full power." The airplane reached a height of 100 feet agl and then would not maintain a positive rate of climb. The pilot initiated a forced landing to an open field off the departure end of the runway 31. During the approach, the pilot "pulled the airplane up to clear trees," and subsequently, the airplane stalled. The airplane impacted the ground, slid 100 feet, and came to rest upright in the field. The FAA inspector, who examined the airplane at the accident site, reported that the ruddervator and both wings were structurally damaged and the engine firewall was buckled.
The inadvertent stall while maneuvering to avoid obstructions during a forced landing. A factor was the pilot's failure to extend the landing gear, which resulted in a partial loss of engine power due to the propeller blades striking the runway.
Source: NTSB Aviation Accident Database
Aviation Accidents App
In-Depth Access to Aviation Accident Reports
