FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN12FA196 · Beech 35

21 Mar 2012 · Glencoe, MN, United States

Beech 35 · Accident: aircraft structural failure en route

From Crystal Airport (KMIC) to Craig, CO

Report a problem

Event

NTSB case
CEN12FA196
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
Instrument Meteorological Cond

Beech 35

Aircraft type
Beechcraft 35
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
N3871N
Operator
Unknown
Onboard fatalities
Unknown
Route
From Crystal Airport (KMIC), Minneapolis, MNTo Craig, CO
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
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
Aircraft structural failure
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
  • Personnel issues › Experience/knowledge

Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.

NTSB narrative

The non-instrument-rated private pilot was conducting the accident flight under visual flight rules without a flight plan. Witnesses in the area reported hearing the airplane flying from east to west but could not see the airplane due to the low clouds and reduced visibility. Subsequently, the witnesses heard a loud crack and then the impact of the airplane with the ground. Based upon witness statements and reported weather conditions near the accident site, the flight encountered instrument meteorological conditions. The distribution of the wreckage was consistent with an in-flight breakup starting with the separation of the left wing followed by the separation of the empennage. All fracture surfaces were consistent with overload failure. An examination of the remaining systems revealed no anomalies. There was no record of the pilot receiving a preflight weather briefing from a recorded source.

Probable cause

The non-instrument-rated pilot’s continued flight into instrument meteorological conditions, which resulted in the design limits of the airplane being exceeded and an in-flight breakup.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN12FA196
Event ID
20120322X05609
Case number
CEN12FA196
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: 87048ac8ffd96270d2984ff9edb8661e0415c1bde9cdeb73b8d1220fa22bbbe7; retrieved 2026-09-13T22:15:51.937Z.