FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN10FA028 · Beech B100

26 Oct 2009 · Benavides, TX, United States

Mazak Properties Beech B100 · Accident: loss of control in flight en route

From Garner Field (UVA) to Leesburg International Airport (LEE)

Report a problem

Event

NTSB case
CEN10FA028
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
4 · 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 B100

Aircraft type
Beechcraft 100
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
N729MS
Onboard fatalities
Unknown
Route
From Garner Field (UVA), Uvalde, TXTo Leesburg International Airport (LEE), Leesburg, 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
Loss of control in flight
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

  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Action/decision

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

NTSB narrative

The pilot obtained three weather briefings before departure. At that time, the current weather along the route of flight showed significant convective activity and a moving squall line, and the forecast predicted significant thunderstorm activity along the planned route of flight. The pilot was concerned about the weather and mentioned that he would be looking for "holes" in the weather to maneuver around via the use of his on-board weather radar. He decided to fly a route further south to avoid the severe weather. Radar data indicates that, after departure, the pilot flew a southerly course that was west of the severe weather before he asked air traffic control for a 150-degree heading that would direct him toward a "hole" in the weather. A controller, who said he also saw a "hole" in the weather, told the pilot to fly a 120-degree heading and proceed direct to a fix along his route of flight. The airplane flew into a line of very heavy to intense thunderstorms during cruise flight at 25,000 feet before the airplane began to lose altitude and reverse course. The airplane then entered a rapid descent, broke up in flight, and subsequently impacted terrain.

Review of recorded precipitation data showed that there was substantial information available to the controller about moderate to extreme weather along the aircraft’s route of flight. While the controller stated that he saw a hole or clear area ahead of the aircraft, this is contradicted by both the recorded data and the statement of a second controller working the D-position at the time of the accident. The first controller did not advise the pilot of the severe weather that was along this new course heading and the pilot entered severe weather and began to lose altitude. The controller queried the pilot about his altitude loss and the pilot mentioned that they had gotten into some "pretty good turbulence." This was the last communication from the pilot before the airplane disappeared from radar.

Review of recorded precipitation data showed that there was substantial information available to the controller about moderate to extreme weather along the aircraft’s route of flight. The controller did not provide advisories to the pilot regarding the adverse weather's immediate safety hazard to the accident flight as required by Federal Aviation Administration Order 7110.65. Examination of the recovered sections of flight control surfaces revealed that all of the fractures examined exhibited signs consistent with overstress failure. There was no evidence of preexisting cracking on any of the fracture surfaces examined and no preaccident anomalies were noted with the engines.

Probable cause

The pilot's failure to avoid severe weather, and the air traffic controller's failure to provide adverse weather avoidance assistance, as required by Federal Aviation Administration directives, both of which led to the airplane's encounter with a severe thunderstorm and the subsequent loss of control and inflight breakup of the airplane.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN10FA028
Event ID
20091026X72148
Case number
CEN10FA028
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: 6559e773ba4bbac080ba4967ad59ae2d1973da58debf7fe276fa4e92a52a52de; retrieved 2026-09-13T20:32:22.553Z.