FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA06FA022 · Cessna 425

29 Nov 2005 · Belgrade, MT, United States

Cessna 425 · Accident: loss of control in flight on approach

From Algona Municipal Airport (AXA) to Bozeman Yellowstone International Airport (BZN)

Report a problem

Event

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

Cessna 425

Aircraft type
Cessna 425
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
N701QR
Operator
Gerald A. Shiffer · private individual
Onboard fatalities
Unknown
Route
From Algona Municipal Airport (AXA), Algona, IATo Bozeman Yellowstone International Airport (BZN), Bozeman, MT
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
Approach · IFR initial approach
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
Loss of control in flight
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Stall
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(cfi) › Airspeed, 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 was on the final approach segment of an instrument flight rules (IFR) cross-country flight that originated approximately 3 hours and 45 minutes prior to the accident when radio communications with the aircraft were lost. The aircraft wreckage was located the following day approximately 2.8 miles from the destination airport. The airplane impacted terrain in a vertical descent and flat attitude and came to rest upright on its fuselage and wings. The cockpit and cabin were intact and both wing assemblies remained attached to the fuselage. Evidence of forward velocity and/or leading edge deformation was not observed to the wings or fuselage. Mixed ice was noted along the leading edge of both wings. At the time of the accident, weather conditions were reported as low ceilings and low visibility due to snow and mist. The accident occurred during dark night conditions. Air traffic control (ATC) transcripts indicated that shortly after entering the holding pattern at 11,000 feet the pilot was issued an approach clearance for the ILS. The pilot acknowledged the clearance and approximately two minutes later ATC communications with the pilot were lost. Pilot logbook records showed that the pilot's total flight time was approximately 1,987 hours. In the six-month period preceding the accident, the pilot logged approximately 40 hours total time, 9 hours of actual instrument time and 7 instrument approaches in the accident airplane. The pilot's total night flying experience was approximately 51 hours. The pilot made no entries in his pilot logbook indicating that he had flown at night in the six-month time frame preceding the accident. Pilots flying the ILS approach prior to the accident aircraft reported mixed icing during the descent and final approach. Post accident examination of the aircraft revealed no evidence to indicate a mechanical malfunction or failure.

Probable cause

The pilot's failure to maintain airspeed during the approach which resulted in an inadvertent stall. Factors associated with the accident were dark night conditions, clouds, icing conditions, low visibility and snow.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA06FA022
Event ID
20051207X01948
Case number
SEA06FA022
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 2005-11-30.
  • API snapshot SHA-256: c4ea05c68a32c17cd0275b09f4e6238f699a1bd378b81f1025524b96a08d84e6; retrieved 2026-09-20T17:43:59.924Z.