Accident Beechcraft A36 Bonanza N8261J,
ASN logo
ASN Wikibase Occurrence # 45434
 
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information.

Date:Sunday 8 September 2002
Time:11:35
Type:Silhouette image of generic BE36 model; specific model in this crash may look slightly different    
Beechcraft A36 Bonanza
Owner/operator:George Howard
Registration: N8261J
MSN: E-2807
Year of manufacture:1993
Total airframe hrs:1170 hours
Engine model:Allison 250B17F2
Fatalities:Fatalities: 1 / Occupants: 1
Aircraft damage: Destroyed
Category:Accident
Location:Grand Canyon, AZ -   United States of America
Phase: En route
Nature:Private
Departure airport:Bullhead City, AZ (IFP)
Destination airport:Liberal, KS (LBL)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
The airplane departed from controlled flight after encountering forecast conditions including moderate turbulence and icing during a cross-country instrument flight and collided with the ground in a near vertical spinning descent. The airplane was equipped with a Stormscope, but not weather radar. The pilot received a preflight weather briefing that included advisories for icing conditions, scattered thunderstorms, and moderate to severe turbulence. The briefer advised that radar indicated a large area of echoes extended over the route of flight with light to moderate intensities and that cloud tops were up to 24,000 feet with scattered thunderstorms and a high likelihood of icing conditions between 15,000 and 24,000 feet. The pilot filed his IFR flight plan with a cruising altitude of 17,000 feet. After takeoff and achieving 17,000 feet, the pilot asked the center controller for a clearance to a higher altitude of 19,000 feet, which was approved. Within the next 3 minutes the pilot made a request to deviate to the left and then to climb higher to 21,000 feet, which were all approved. Shortly thereafter, the pilot advised he "really went through some bad turbulence here," and the controller inquired about his heading and altitude. The pilot advised he wanted to climb back to altitude but he was still in IMC conditions. That was the last communication from the flight. According to the controller's memory of the radar display, the airplane was getting into some weather and had deviated north, made a u-turn and had gone down to 19,000 feet, and had started getting back on course when it disappeared. The requests from the pilot to climb to higher altitude was likely made to climb out of icing conditions and an attempt to climb over some of the towering cumulus clouds tops. A limited overlay of weather echoes that would have been available to the controller. The controller provided no weather deviations or support even after the flight encountered some weather, lost altitude, and reported encountering significant turbulence. The weather data showed a shear level was at 19,800 feet, with a 11.1 knot per 1,000 feet change in wind speed. This shear layer had a high probability of severe turbulence. The data also showed a 92 percent probability of rime icing at 20,000 feet.


Probable Cause: the pilot's inadequate in-flight planning/decision and his failure to maintain adequate airspeed which resulted in an encounter with adverse weather conditions and the loss of control due to a stall. Contributing factors were thunderstorm related turbulence, icing conditions, the pilot's disregard of the weather forecast.

Accident investigation:
cover
  
Investigating agency: NTSB
Report number: LAX02FA278
Status: Investigation completed
Duration:
Download report: Final report

Sources:

NTSB: https://www.ntsb.gov/_layouts/ntsb.aviation/brief.aspx?ev_id=20020913X01598&key=1

Location

Revision history:

Date/timeContributorUpdates
28-Oct-2008 00:45 ASN archive Added
21-Dec-2016 19:24 ASN Update Bot Updated [Time, Damage, Category, Investigating agency]
09-Dec-2017 17:47 ASN Update Bot Updated [Departure airport, Destination airport, Source, Narrative]

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org