CHI05FA020 · Beech A36
Beech A36 · Accident: in flight encounter with weather en route
From SFD · Winner, SD to Anderson Municipal Darlington Field (AID)
Event
- NTSB case
- CHI05FA020
- 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
- 3 · 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
Beech 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
- N55448
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From SFD · Winner, SDTo Anderson Municipal Darlington Field (AID), Anderson, IN
- 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
- First occurrenceThe 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
- In flight encounter with weather
- 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
- Pilot in command › Aircraft control, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane piloted by an instrument rated private pilot, was destroyed on impact with terrain and post impact fire. The pilot and two passengers were fatally injured. The pilot established radio communications with the air traffic controller on duty at an Air Route Traffic Control Center's radar position about 2027. The controller gave the pilot the position's current altimeter setting. The air traffic controller observed the flight enter an area of weather. At about 2036, an air traffic controller advised the pilot that radar contact was lost. The pilot did not respond. No further radio communications were established with the flight. A witness, who was a commercial pilot, stated, "Aircraft spun out of clouds, began recovery, hit the ground, [and] burst of flame immediately." The flight's National Track Analysis Program radar data was plotted on Doppler weather radar base reflectivity depictions. That plotted data showed that the airplane entered an area of weather consistent with level three to level four thunderstorm activity. Surface weather observations showed VFR weather was present. An on-scene examination was performed. A gyro and its housing from a flight instrument were examined. That examination revealed rotational scoring. The turn coordinator was found destroyed. The face from the turn coordinator showed the airplane in a right bank turn. A section of right wing tip was found near a ground scar. The navigation light on that wingtip contained a green media. The left wing was found detached from the fuselage. Control cables were traced. All breaks in control cables were consistent with overload. No airframe or engine pre-impact anomalies were detected.
Probable cause
The pilot not maintaing airplane control during cruise flight. Factors present were night and thunderstorm conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI05FA020
- Event ID
- 20041103X01745
- Case number
- CHI05FA020
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2004-10-30.
- API snapshot SHA-256: f104977debcd8ff08e720a40feec79a4b7d243f159d5650736d1b9926f66fdaa; retrieved 2026-09-20T18:14:24.220Z.