Monday, June 15, 2026

Loss of control in flight: Beechcraft V35 Bonanza, N47WT, fatal accident occurred on May 15, 2024, near Franklin, Tennessee


  • Location: Franklin, Tennessee
  • Accident Number: ERA24FA217
  • Date & Time: May 15, 2024, 12:02 Local
  • Registration: N47WT
  • Aircraft: Beech V35
  • Aircraft Damage: Destroyed
  • Defining Event: Loss of control in flight
  • Injuries: 3 Fatal
  • Flight Conducted Under: Part 91: General aviation - Personal

https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/194264/pdf

https://data.ntsb.gov/Docket?ProjectID=194264

On May 15, 2024, at 1202 central daylight time (CDT), a Beech V35-TC airplane, N47WT, was destroyed when it was involved in an accident near Franklin, Tennessee. The pilot and two passengers were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight

The pilot and two passengers were about 380 nautical miles (nm) into a planned 550-nm, instrument flight rules (IFR) flight; the pilot was in communication with air traffic control. After flying at an altitude of about 7,000 ft mean sea level (msl) for a majority of the flight, the pilot requested to fly at 9,000 ft msl, as well as minor course deviations. The deviation requests were likely for weather avoidance although the pilot gave no explanation, and the controllers did not request the reason for the pilot’s requests.

The controller assigned a heading to the north, informing the pilot that the turn north would be temporary and to expect a turn back to the original course; the pilot acknowledged the clearance and turned north. Weather data indicated that, as the airplane was climbing through 9,400 ft msl, it likely encountered light to moderate rain showers and updrafts. 

The controller then cleared the pilot to resume his previously assigned route; however, the pilot continued on his northerly heading and remained at 9,500 ft msl. The controller made several requests to the pilot to descend as he remained above 9,000 ft msl. The airplane then turned to the northeast, flying further into a significant area of developing convective weather with rain showers and updrafts. After another request by the controller, the pilot responded, “Uh descending to nine thousand for four seven whiskey.” There were no further communications from the pilot.

A performance study based on ADS-B data indicated that, about 1 minute after the last transmission, while on a track of about 070° and at a groundspeed of 180 kts (calibrated airspeed 152 kts), the airplane entered a tightening right turn and began to descend. Initially, the descent rate did not exceed 3,000 ft per minute (fpm) but then rapidly increased to over 10,000 fpm while continuing in the right turn. Dispersal of the airplane wreckage was indicative of an inflight breakup. 

Examination of the airplane and engine revealed no evidence of a pre-accident anomaly that would have prevented normal operation. 

The area of moderate precipitation encountered by the flight was not displayed on the controller’s standard terminal automation replacement system (STARS) display. A postaccident review of the weather information available to the controller on the STARS display showed that the display was underreporting the weather intensity. Due to this underreporting, the weather intensity depiction on the controller’s display showed no available weather near the accident airplane at the time of the accident and limited the controller’s ability to accurately warn the pilot of hazardous weather along the route of flight. Further investigation indicated that the primary reason the storm was not displayed to the controller was that the developing storm was initially too small to survive the spatial smoothing processing of the facility’s radar system. 

Based on the airplane’s flight track data, it likely encountered strong updrafts while in growing areas of precipitation and instrument meteorological conditions, which ultimately resulted in the pilot’s spatial disorientation, loss of airplane control, and an in-flight breakup as aerodynamic forces on the airplane exceeded the structural integrity of the airframe. Contributing to the accident was the anomalous and intermittent display of weather intensity on the controller’s STARS display, which prevented his ability to accurately warn the pilot of hazardous weather. 

- Probable Cause: The pilot’s flight into convective weather, which resulted in a loss of control due to spatial disorientation and a subsequent inflight breakup of the airplane. Contributing to the accident was the lack of accurate weather intensity depiction on the controller’s display, which limited the controller’s ability to warn the pilot of hazardous weather along the route of flight.

Controlled flight into terr/obj (CFIT): Luscombe 8A Silvaire, N37081, fatal accident occurred on June 12, 2024, near South Lake Tahoe, California

  • Location: South Lake Tahoe, California 
  • Accident Number: WPR24FA195 
  • Date & Time: June 12, 2024, 15:25 Local 
  • Registration: N37081 
  • Aircraft: Luscombe 8A 
  • Aircraft Damage: Substantial 
  • Defining Event: Controlled flight into terr/obj (CFIT) 
  • Injuries: 2 Fatal 
  • Flight Conducted Under: Part 91: General aviation - Unknown

https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/194461/pdf

https://data.ntsb.gov/Docket?ProjectID=194461

On June 12, 2024, at 1525 Pacific daylight time, a Luscombe 8A airplane, N37081, was substantially damaged when it was involved in an accident near South Lake Tahoe, California. The pilot and passenger were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

The pilot and passenger were conducting a cross-country flight in the 65-horsepower, tailwheel equipped airplane to an airport located in mountainous terrain. In-flight photos taken by the passenger showed the airplane at low altitude over the mountains, heading toward higher terrain, about 1/2 mile from the accident site. Accident site signatures were consistent with a collision with trees and subsequent impact with terrain. Examination of the wreckage revealed no evidence of preaccident mechanical malfunctions or failures that would have precluded normal operation.

The calculated density altitude at the accident site was about 11,329 ft. Review of the Koch chart using the estimated conditions present at the accident site showed about an 80% decrease in the airplane’s published climb performance under these conditions, which would have resulted in a rate of climb of about 150 ft per minute. The circumstances of the accident are consistent with the pilot’s decision to conduct low-altitude flight into mountainous terrain under density altitude conditions that significantly degraded the airplane’s performance, which resulted in impact with trees and terrain.

- Probable Cause: The pilot’s decision to continue low-altitude flight toward rising mountainous terrain in high density altitude conditions, which resulted in collision with trees and terrain.