Accident Beechcraft V35B Bonanza N6659L,
ASN logo
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information.

Date:Thursday 1 February 2024
Type:Silhouette image of generic BE35 model; specific model in this crash may look slightly different    
Beechcraft V35B Bonanza
Owner/operator:Control Data Inc
Registration: N6659L
MSN: D-10279
Year of manufacture:1979
Fatalities:Fatalities: 1 / Occupants: 1
Other fatalities:2
Aircraft damage: Destroyed
Location:Clearwater, FL -   United States of America
Phase: Approach
Departure airport:Vero Beach Regional Airport, FL (VRB/KVRB)
Destination airport:Clearwater Airpark, FL (CLW/KCLW)
Investigating agency: NTSB
Confidence Rating: Information verified through data from accident investigation authorities
On February 1, 2024, about 1907 eastern standard time, a Beech V35B, N6659L, was destroyed when it impacted two residences and the ground near Clearwater, Florida. The commercial pilot was fatally injured. Additionally, two occupants of one residence were fatally injured, and one occupant of a second residence sustained minor injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

According to Federal Aviation Administration (FAA) Automatic Dependent Surveillance – Broadcast (ADS-B) data and preliminary air traffic control radar and audio information, the flight departed about 1809 from Vero Beach Municipal Airport (VRB), Vero Beach, Florida, on an instrument flight rules (IFR) flight plan destined for Clearwater Air Park (CLW), Clearwater, Florida. About 1900, when the flight was about 4.1 nautical miles east-southeast from the runway 34 displaced threshold at CLW, the pilot cancelled the IFR clearance. The pilot was advised by air traffic control that radar services were terminated, and he proceeded under visual flight rules (VFR).

According to two individuals who were at CLW, the pilot broadcast on the common traffic advisory frequency (CTAF) that he could not find the airport and asked them to turn on the runway lights which were already on from an airplane that had just landed. They also stated that after the pilot requested a second time to turn the runway lights on, the pilot controlled runway lighting was changed to the highest intensity. Both individuals then heard the pilot announce he had a “fire.” The airplane’s location at that time was not determined, and the CTAF was not recorded.

While flying VFR, the flight proceeded west of CLW then turned to a northwesterly heading nearly parallel to runway 34. The flight continued on the northwesterly heading north of CLW, then at 1903:46, the pilot turned left and proceeded on a southeasterly heading. At 1905:15, the airplane was west of CLW 1,100 ft msl, when a 7700 transponder code was displayed on the controller’s scope. At 1905:47, while flying at 1,300 ft msl, the pilot stated, “nine five lima” and, “coming to Albert Whitted I can’t see the other airport.” The controller advised the pilot that the flight was 1 mile south of CLW and asked if he could turn to heading 180° and to maintain the present altitude. At 1906:15, the pilot advised the controller, “i’m losing engine” to which the controller asked the pilot if he could see the St Pete-Clearwater International Airport (PIE), St Petersburg-Clearwater, Florida, that was 3 miles ahead of his position. The controller also advised the pilot that runways 18/36 were available at PIE. There were no further transmissions from the pilot.

A pilot flying nearby reported seeing the accident airplane in a 30° to 40° nose-low descent that he described as, “like an uncontrolled descent.” He added that while the airplane was descending, he saw a “very bright light” descending very fast to impact.

Another witness who was a passenger in a car northwest of the accident site reported seeing the accident airplane flying ahead of their position from the right to the left, or west to east. She said she did not hear any sound and reported seeing a “fireball” or something on fire while airborne before the impact. She did not identify the object as an airplane at that time. She described the fire as a round fireball with a white cone in the front portion.

The pilot who was flying nearby observed the impact and reported it to air traffic control.

Multiple videos from commercial businesses west of the accident site depicted a light descending steeply with sounds associated with engine operation, followed by a fireball. The videos were provided to the NTSB Vehicle Recorders Laboratory for further review.

The remains of the extensively heat damaged and impact fragmented wreckage was secured for further examination.

Accident investigation:
Investigating agency: NTSB
Report number: 
Status: Preliminary report
Download report: Preliminary report


NTSB (photo)




Revision history:

02-Feb-2024 06:00 Captain Adam Added
02-Feb-2024 13:22 Anon. Updated [Category]
02-Feb-2024 14:02 gerard57 Updated [Total fatalities, Total occupants, Other fatalities, Source, Narrative]
02-Feb-2024 14:11 RobertMB Updated [Time, Location, Source, Narrative, Category]
02-Feb-2024 15:12 Anon. Updated [Category]
02-Feb-2024 15:23 Captain Adam Updated [Source, Narrative]
02-Feb-2024 15:48 Planeguy777 Updated [Narrative]
02-Feb-2024 16:01 Iceman 29 Updated [Destination airport, Embed code, Narrative, Photo]
02-Feb-2024 16:05 Iceman 29 Updated [Embed code]
02-Feb-2024 16:06 Iceman 29 Updated [Embed code]
03-Feb-2024 08:27 RobertMB Updated [Location, Source, Narrative, Category]
06-Mar-2024 08:37 Captain Adam Updated [Time, Source, Narrative, Category, Accident report]

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314