Date & Time: Oct 26, 2009 at 1143 LT
Type of aircraft:
Beechcraft 100 King Air
Registration:
N729MS
Flight Phase:
Flight
Flight Type:
Private
Survivors:
No
Schedule:
Uvalde - Leesburg
MSN:
BE-2
YOM:
1976
Crew on board:
1
Crew fatalities:
1
Pax on board:
3
Pax fatalities:
3
Other fatalities:
0
Total fatalities:
4
Captain / Total flying hours:
550
Circumstances:
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.
Final Report:
N729MS.pdf118.12 KB