FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA09FA074 · Beech 35-B33

30 Nov 2008 · Homosassa Spgs., FL, United States

Beech 35-B33 · Accident: windshear or thunderstorm en route

From Tallahassee International Airport (TLH) to Tampa Executive Airport (VDF)

Report a problem

Event

NTSB case
ERA09FA074
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
2 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Instrument Meteorological Cond

Beech 35-B33

Aircraft type
Beechcraft 35
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N945T
Operator
Unknown
Onboard fatalities
Unknown
Route
From Tallahassee International Airport (TLH), Tallahassee, FLTo Tampa Executive Airport (VDF), Tampa, FL
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
En route · cruise
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Windshear or thunderstorm
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Action/decision

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

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.

Probable cause

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

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA09FA074
Event ID
20081201X70139
Case number
ERA09FA074
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 9dc8d2540f928ff29ed163b92dc4ef8ed0a19c8e79f4cb8d7d6aa6b3dac20b19; retrieved 2026-09-13T19:50:42.962Z.