FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW00FAMS1 · Beech M35

3 Apr 2000 · GULF OF MEXICO

Beech M35 · Accident: in flight encounter with weather en route

From Lafayette Regional Airport (LFT) to Sugar Land Regional Airport (SGR)

Report a problem

Event

NTSB case
FTW00FAMS1
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
1 · all aircraft and ground
Ground fatalities
0
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 M35

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
N9778R
Onboard fatalities
Unknown
Route
From Lafayette Regional Airport (LFT), Lafayette, LATo Sugar Land Regional Airport (SGR), Houston, TX
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
First occurrenceThe 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
In flight encounter with weather
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

  • Pilot in command › Aircraft control, not maintained
  • Pilot in command › Flight into known adverse weather, continued

Not plotted · Location withheld: coordinates are missing, conflicting, invalid, or have no accepted acquisition method. No substitute location has been invented.

NTSB narrative

The single-engine airplane is presumed destroyed following an uncontrolled descent into the Gulf of Mexico. The instrument rated private pilot, sole occupant, is presumed fatal. The pilot purchased the airplane 10 days prior to the accident and received dual instruction, which included an instrument competency check, 2 days prior to the accident. The flight instructor reported that no aircraft discrepancies were noted during the dual instructional flights. Subsequently, the cross-country flight departed Florida for Texas. Following a refueling stop in Alabama, the flight diverted to Louisiana, due to en route weather. On the morning of the accident, the pilot obtained a preflight weather briefing. Night instrument meteorological conditions (IMC) prevailed for the flight, and the pilot filed an IFR flight plan. The clearance delivery controller told the pilot about a line of thunderstorms crossing his route of flight and confirmed that the pilot had received all the weather updates from flight service. When the flight was cleared for takeoff, the controller confirmed that the airplane was not equipped with weather detection/avoidance equipment. At an en route altitude of 4,000 feet msl, the airplane deviated to a heading of 220 degrees where the flight path paralleled the line of thunderstorms. Subsequently, the pilot reported 'light to moderate chop.' The controller informed the pilot that a convective sigmet had been issued for an 'area of severe thunderstorms moving from two four zero at thirty knots tops above flight level four five zero tornados hail to two inches and wind gust to sixty knots' to which the pilot replied 'what in the world am I doing out here then.' The pilot requested that the controller keep the airplane out of the weather. The controller informed the pilot that the he would have to take at 'least two thirty heading for the next fifty miles or so before you could turn west bound.' Subsequently, the pilot replied, 'okay we are in moderate chop go ahead if you keep us out of the muck we are heading two three zero right now.' At 0619:38, the flight was cleared to a heading of 240 degrees. At 0621:35, the pilot requested 'you got anything better.' At 0621:41, the pilot told the controller 'we are pretty severe right now.' Review of radar track data for the airplane revealed that about 0620, there were excursions in the airplane's altitude and airspeed consistent with flight into moderate to severe turbulence. At 0621:44, the controller informed the pilot that he could turn the airplane west to a heading of 270 degrees. At 0624:05, radio and radar contact were lost. Houston Center tracked the descending target to 2,700 feet at a position approximately 20 nautical miles offshore southeast of Lake Charles, Louisiana. An extensive sea and air search for the airplane was unsuccessful.

Probable cause

the pilot's continued flight of the airplane into known adverse weather conditions resulting in the pilot's loss of control of the aircraft. Contributing factors were the severe turbulence and windshear.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW00FAMS1
Event ID
20001212X20807
Case number
FTW00FAMS1
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: dfade4cc49e5afc59b1bce20615a018b9fbda141b764c8ccbc219a82025c3abb; retrieved 2026-09-20T21:22:10.898Z.