Murfreesboro, TN, USA
N5624S
Beech V35
The private pilot was conducting a cross-country, personal flight. He reported that, during approach to the destination airport, he had to manually extend the landing gear because he noticed the "down" light was not green. A witness who was in the airport terminal reported that he heard the pilot announce on the CTAF that his airplane was having "amperage" issues and that he might have to land with no radios. The pilot then asked him to confirm that the landing gear were extended. The witness went out to the taxiway and checked the landing gear status as the pilot conducted a low pass over the runway. The landing gear was not extended fully. The pilot stated that he attempted to go around but that the airplane was "sucked down" into trees by "a very strong wind" as the airplane proceeded beyond the departure end of the runway. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airframe or engine that would have precluded normal operation. Examination of the wreckage revealed that the alternator switch was in the "off" position, which would have prevented the battery from charging and likely led to there being insufficient battery power to extend the landing gear. The airport's automated weather observation station reported that, about the time of the accident, there was a right quartering headwind at 14 knots, gusting to 19 knots.
On October 28, 2018, about 1210 central daylight time, a Beech V35, N5624S, was substantially damaged when it impacted trees while maneuvering at low altitude near Murfreesboro Municipal Airport (MBT), Murfreesboro, Tennessee. The private pilot was seriously injured. The airplane was privately owned and operated by the pilot under the provisions of Title 14 Code of Federal Regulations Part 91. Visual meteorological conditions prevailed and no flight plan was filed for the personal flight that originated from Gatlinburg-Pigeon Forge Airport (GKT), Sevierville, Tennessee, about 1000.The pilot reported that he attempted to extend the landing gear while in the airport traffic pattern at MBT. He then noticed that the green cockpit indicator was not illuminated and manually extended the landing gear. The pilot subsequently requested that personnel on the ground confirm that the landing gear was extended and he performed a low pass over runway 18. The pilot was told that the landing gear were not extended, so he attempted a go-around, but was "sucked down" into trees by a very strong wind. Other than a possible electrical issue, the pilot reported that there were no other preimpact mechanical malfunctions with the airframe or engine. A witness stated that he and a friend were in the MBT airport terminal building when they heard the pilot announce on the common traffic advisory frequency that his airplane was having "amperage" issues and he might be performing a landing with no radios. The pilot then asked if the witness could visually confirm that the landing gear was extended. The witness agreed and went to a taxiway with a handheld radio while the pilot performed a low pass over runway 18. The witness reported to the pilot that the landing gear was only partially extended. The airplane then proceeded beyond the departure end of the runway, losing altitude, looked like it stalled and descended into trees. Examination of the wreckage by a Federal Aviation Administration inspector revealed damage to both wings and the fuselage. The inspector noted that the alternator switch was in the off position. The recorded weather at MBT, at 1215, included wind from 210° at 14 knots, gusting to 19 knots, and a clear sky.
The pilot's failure to maintain airplane control while maneuvering at low altitude in gusting wind conditions.
Source: NTSB Aviation Accident Database
Aviation Accidents App
In-Depth Access to Aviation Accident Reports
