FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA97FA133 · Cessna U206E

9 Jun 1997 · Red Lodge, MT, United States

Cessna U206E · Accident: loss of control in flight en route

From Dawson Community Airport (GDV) to McCall Municipal Airport (MYL)

Report a problem

Event

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

Cessna U206E

Aircraft type
Cessna 206
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
N206EC
Operator
Cheney, Ernest, J. · private individual
Onboard fatalities
Unknown
Route
From Dawson Community Airport (GDV), Glendive, MTTo McCall Municipal Airport (MYL), McCall, ID
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
Loss of control in flight
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 › Flight into known adverse weather, attempted
  • Wing, bracing strut › Overload

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The non instrument-rated pilot obtained two separate weather briefings on the late afternoon and following morning prior to departing on his intended flight from Glendive, MT, to McCall, ID. He was advised by the briefer that 'VFR flight was not recommended' due to a low pressure system in Montana along with obscurations. The flight departed Glendive; and approximately 4 hours later, the pilot radioed Great Falls AFSS looking for a VFR airport available for landing. Witnesses observed seeing the aircraft exit clouds (bases approximately 6,000 feet MSL or 800 feet AGL) and break up, with both wings separating. Weather at the site was described as 'low clouds' and 'overcast' with poor visibility. Both wing struts separated at the strut-to-fuselage attach points, and the right wing was found in two separate pieces just short of the intact left wing. Both wings impacted terrain short of the fuselage ground impact site. The wing spar carry-through channel was observed to have separated just inboard of the right wing-root to fuselage attach point. The fracture surfaces were characteristic of instantaneous overload separations. All horizontal and vertical control surfaces remained with the fuselage except the right elevator.

Probable cause

The pilot-in-command's flight into known adverse weather and the subsequent overload and separation of the right wing-strut fuselage-to-strut attach point. Factors contributing were clouds and obscuration.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA97FA133
Event ID
20001208X08241
Case number
SEA97FA133
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: investigation status. 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: 72f8b525690168701c141a89a94891c868343f94cfe47695fa9a10d9f03cf6ce; retrieved 2026-09-20T22:56:00.999Z.