Hawker Beechcraft A36 accident near Macon, Mississippi, May 31, 2012
On May 31, 2012 at about 9:56 pm local time, a Hawker Beechcraft A36, registered N976S, was substantially damaged in an accident during enroute (cruise) near Macon, Mississippi. It was a personal flight under general aviation rules (Part 91). 1 person was killed. The weather was visual conditions (good weather).
Preview. This page is not yet listed for search engines.
The NTSB's probable cause their words, unchanged
The pilot's decision to continue flight into an area of known thunderstorms, which resulted in an in-flight breakup. Contributing to the accident was the pilot's lack of experience in actual instrument meteorological conditions and his reliance on datalink weather radar imagery for tactical avoidance of convective weather.
Source: NTSB aviation accident database, copy made October 4, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- May 31, 2012 · about 9:56 pm local time
- Place
- Macon, Mississippi · map
- Type
- Accident
- Injuries
- 1 person was killed.
- Weather
- visual conditions (good weather)
- Aircraft
- Hawker Beechcraft A36
- Registration
- N976S · registry record · serial E-3370
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
While on a long cross-country flight on an instrument flight rules flight plan, the pilot attempted to fly through a line of thunderstorms. The airplane was equipped with satellite radar weather (NEXRAD Composite) and a stormscope/strikefinder. Using his equipment and talking with air traffic controllers, the pilot noted a break in the extreme precipitation, which still contained moderate to heavy precipitation, about 115 miles from the airplane's position. As the airplane approached that area, the pilot reported that a thunderstorm cell had filled it in; however, there was still a gap in the line of thunderstorms about 10 miles north. The pilot then attempted to fly to that gap and no further communications were received from the accident airplane. Review of the airplane's radar track was overlaid on a weather radar plot and revealed that the pilot attempted to fly though a Level 5, or heavy, thunderstorm cell. The turbulence from that cell resulted in an in-flight breakup of the airplane due to overstress, and the wreckage was scattered over a mile on the ground. The satellite radar weather information, most likely displayed in the airplane cockpit when the pilot was attempting to fly to a gap in thunderstorm cells, was about 6 to 7 minutes old at the time of the accident and depicted the airplane in an area clear of precipitation. The airplane's stormscope/strikefinder would have provided real-time lightning information; however, it would have had significantly less detail than composite weather radar depictions and thus be less suitable for use in attempting to navigate through a line of thunderstorms and in between thunderstorm cells. Both sources of weather information used were less suitable than onboard weather radar, which would have provided real-time weather radar images in the cockpit. The pilot had obtained his instrument rating less than 2 years before the accident and had accrued about 32 total hours of actual instrument experience. The NTSB recently issued a related Safety Alert, In-Cockpit NEXRAD Mosaic Imagery, viewable at www.ntsb.gov, describing how the actual age of NEXRAD data can differ significantly from the age displayed.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Windshear or thunderstorm during enroute (cruise) defining event
- Inflight upset during enroute (cruise)
- Aircraft structural failure during enroute (cruise)
- Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent
The NTSB's findings
- cause Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
- cause Aircraft › Aircraft structures › (general) › (general) › Capability exceeded
- factor Personnel issues › Experience/knowledge › Experience/qualifications › Total instrument experience › Pilot
- factor Personnel issues › Psychological › Personality/attitude › Confidence/reliance on equip › Pilot
- cause Environmental issues › Conditions/weather/phenomena › Convective weather › Thunderstorm › Decision related to condition
Pilot
- Certificate: private
- Ratings: single-engine land; instrument: airplane
- Flight time: 258 hours in all
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: left
- Injury: fatal
The aircraft
- Airframe total time: 1,337 hours
- Last inspection: annual inspection, June 14, 2011
- Maximum gross weight: 3,650 lb
- Seats: 6
- Landing gear: retractable
- Engine: Cont Motor IO-550 (piston); 0 hours total
- Fire on the ground
The flight
- Departed from: PIE Clearwater FL at 7:15 pm
- Destination: OUN Norman OK
- Flight plan: IFR
Weather at the time
- Light: daylight
- Wind: from 240° at 7 knots, gusting 22
- Visibility: 10 statute miles
- Sky: broken clouds at 2,600 ft; scat at 1,100 ft
- Temperature: 68°F (20°C), dew point 64°F (18°C)
- Altimeter: 29.79 inHg
- Observation at 9:55 pm from STF, 24 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flig | 1 |
About this page
Everything above comes from the NTSB's public accident database: the narrative, probable cause and findings are the NTSB's own words, and the coded tables behind its report (pilot, aircraft, flight, weather, injuries, sequence of events) are written out in plain English. Pilots' ages, home towns and medical details are left out on purpose. The docket at the NTSB holds the report as a PDF and the investigation's photographs and documents. This site never names pilots, passengers or anyone else involved. A preliminary report describes what is known soon after the event and can change; the final report, with the probable cause, usually follows one to two years later and this page is refreshed when it does. Case number ERA12FA376.
