FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN22FA023 · Beech P35

31 Oct 2021 · Harrison, NE, United States

Beech P35 · Accident: VFR encounter with IMC en route

From Marshalltown Municipal Airport (KMIW) to Converse County Airport (KDGW)

Report a problem

Event

NTSB case
CEN22FA023
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
2 · all aircraft and ground
Ground fatalities
0
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
Unknown

Beech P35

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
N8625M
Operator
Unknown
Onboard fatalities
Unknown
Route
From Marshalltown Municipal Airport (KMIW), Marshalltown, IATo Converse County Airport (KDGW), Douglas, WY
Aircraft age
About 58 years (built 1963)
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
VFR encounter with IMC
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

  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

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

NTSB narrative

The night before the accident, the instrument-rated pilot received a weather briefing for the first leg of a multi-leg cross country flight and filed an instrument flight rules (IFR) flight plan. The next morning, the pilot and passenger completed the first leg and serviced the airplane with 49.5 gallons of aviation gasoline. The pilot had not received a weather briefing or filed a flight plan for the second leg of the flight but was in contact with air traffic control (ATC) and received visual flight rules (VFR) flight following for the first portion of the flight. The controllers experienced difficulty communicating with the pilot and the radar coverage was intermittent. About 2 hours into the flight, the controller advised that the airplane was still not visible on radar and terminated VFR flight following. Recorded flight track information revealed that the airplane continued west toward the destination airport. About 15 to 30 minutes later, the pilot of another airplane observed the accident airplane headed west. Since he knew there were icing conditions and bad weather ahead, he attempted to radio the pilot but did not receive a response. About an hour later, the airplane’s flight track descended toward rising terrain, where it was briefly at the same elevation as the terrain, then climbed to about 320 ft above ground level (agl). The final flight track point showed the airplane at 250 ft agl and 150 kts groundspeed. The airplane impacted open terrain with a shallow descent angle and the wings relatively level, then came to rest upright about 700 ft later. The end of the debris field was defined by the engine and propeller, which had separated from the airplane during the accident sequence. General fragmentation and the length of the wreckage debris field were indicative of a high-speed impact. Postaccident examination of the airplane did not reveal any preimpact mechanical malfunctions or failures that would have precluded normal operation. The airplane was likely operating in instrument meteorological conditions and in mixed freezing precipitation and snow at the time of the accident. If the pilot had obtained an adequate weather briefing, he likely would have been made aware of the adverse conditions and could have been able to alter his course to avoid the conditions. The conditions at the airport with the closest recorded weather station, directly along his route of flight, could have been a safe alternate airport. Based on the flight track and weather conditions at the time of the accident, it is likely that the pilot was attempting to avoid instrument and icing conditions; he unknowingly descended toward rising terrain, then rapidly climbed to avoid the terrain, which resulted in a loss of control.

Probable cause

The pilot’s decision to continue the flight into instrument and icing conditions, which resulted in loss of control and impact with terrain. Contributing to the accident was the pilot’s failure to obtain a timely weather briefing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN22FA023
Event ID
20211101104188
Case number
CEN22FA023
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, cause areas. 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: cdfc2768c85aa732a744e167aead6b8045823509f640a4f98e2fe4b2dcc2198c; retrieved 2026-09-15T07:36:37.502Z.