ERA12FA376 · Hawker Beechcraft A36
Hawker Beechcraft A36 · Accident: windshear or thunderstorm en route
From St. Petersburg Clearwater International Airport (PIE) to University of Oklahoma Westheimer Airport (OUN)
Event
- NTSB case
- ERA12FA376
- 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
- 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
- Visual Meteorological Cond
Hawker Beechcraft A36
- Aircraft type
- Beechcraft 36
- 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
- N976S
- Operator
- Earl Shirley
- Onboard fatalities
- Unknown
- Route
- From St. Petersburg Clearwater International Airport (PIE), Clearwater, FLTo University of Oklahoma Westheimer Airport (OUN), Norman, OK
- 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
- Windshear or thunderstorm
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft structures
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
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.
Probable cause
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA12FA376
- Event ID
- 20120531X02455
- Case number
- ERA12FA376
- 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, coordinates. 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: b5d2ca93f55375cfb731954facbbebc25fc55f814cfdd311c0db58dad0bffa0d; retrieved 2026-09-13T22:24:41.809Z.