The U.S. aircraft register, updated daily
Accidents · NTSB ERA09FA074 · Final report

Beech 35-B33 accident near Homosassa Spgs., Florida, November 30, 2008

On November 30, 2008 at about 11:18 pm local time, a Beech 35-B33, registered N945T, was destroyed in an accident during enroute (cruise) near Homosassa Spgs., Florida. It was a personal flight under general aviation rules (Part 91). 2 people were killed. The weather was instrument conditions (cloud, fog or low visibility).

The NTSB's probable cause their words, unchanged

The pilot’s continued flight into known adverse weather conditions.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
November 30, 2008 · about 11:18 pm local time
Place
Homosassa Spgs., Florida · map
Type
Accident
Injuries
2 people were killed.
Weather
instrument conditions (cloud, fog or low visibility)
Aircraft
Beech 35-B33 · all 35-B33s on the register
Registration
N945T · registry record · serial CD-704
Damage
Destroyed
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The day of the accident the pilot contacted the St. Petersburg Flight Service Station at 0852, 1308, and 1701 local time. Each time, he requested an abbreviated weather briefing and was told of embedded thunderstorms and convective activity along the route of flight. He was also told that there was a tornado watch in effect for central and southern Florida. After amending the instrument-flight-rules flight plan takeoff time three times, the flight was cleared to take off from runway 36 at 1730. After takeoff the flight was handed off to Jacksonville Center (ZJX) and the controller provided information on the moderate and heavy precipitation along the pilot's route of flight for the next 100 miles. The pilot requested deviation of "any holes" left or right of the flight path. The controller informed him that the moderate to heavy precipitation was to the left and right of them for 200 miles. About 10 minutes after the initial contact with the controller, the pilot asked "How much further does it look for us?...Getting bumped around pretty bad here." The ZJX controller advised that they were in moderate precipitation for the next 30 miles and briefed them on what to expect for the next several miles; the pilot acknowledged the transmission. After about 5 minutes, the controller informed the pilot that they were in a patch with no precipitation and again briefed him on what to expect for the remainder of the flight; the pilot never acknowledged the transmission and no further transmissions were received. About 30 seconds later, with the flight over the Gulf of Mexico and on a southeast heading at approximately 5,000 feet msl, radar contact was lost. Prior to the loss of contact radar returns show that the airplane began a right descending turn. At that time, satellite weather imagery depicted a line of clouds along a front and over the last radar hit consisting of nimbostratus to embedded cumulonimbus clouds with level 3 to 4 intensity echoes. The airplane was most likely not equipped with any airborne weather detection and avoidance systems. The main wreckage was never located; however, some personal items and a small amount of debris from the airplane were found floating on the surface of the water near the last recorded radar return.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Windshear or thunderstorm during enroute (cruise) defining event
  2. Loss of control in flight during enroute (cruise)

The NTSB's findings

  • cause Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
  • cause Environmental issues › Conditions/weather/phenomena › Convective weather › Thunderstorm › Decision related to condition
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › (general) › Not attained/maintained

Pilot

  • Certificate: private
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 1,057 hours in all; 144 in this make and model; 28 in the last 90 days; 904 as pilot in command
  • Medical certificate: Class 1 (without waivers/limitations)
  • Seat: unk
  • Injury: fatal

Crew member

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 130 hours in all
  • Medical certificate: Class 3 (without waivers/limitations)
  • Seat: unk
  • Injury: fatal

The aircraft

  • Airframe total time: 7,992 hours
  • Last inspection: annual inspection, November 10, 2008
  • Maximum gross weight: 3,000 lb
  • Seats: 4
  • Landing gear: retractable
  • Engine: Cont Motor IO-550 SERIES (piston); 0 hours total

The flight

  • Departed from: TLH Tallahassee FL at 10:40 pm
  • Destination: VDF Tampa FL
  • Flight plan: IFR
  • A second pilot was aboard

Weather at the time

  • Light: night
  • Wind: from 230° at 3 knots
  • Visibility: 10 statute miles
  • Sky: overcast at 800 ft; scat at 600 ft
  • Temperature: 64°F (18°C), dew point 63°F (17°C)
  • Altimeter: 29.70 inHg
  • Observation at 11:20 pm from KVDF, 45 miles away

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.