FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA04GA192 · Cessna U206G

20 Sept 2004 · Essex, MT, United States

USDA, Forest Service, Flathead National Forest Cessna U206G · Accident: in flight encounter with weather en route

From Glacier Park International Airport (FCA) to Schafer USFS Airport (8U2)

Report a problem

Event

NTSB case
SEA04GA192
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
Government
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

Cessna U206G

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
N206SM
Onboard fatalities
Unknown
Route
From Glacier Park International Airport (FCA), Kalispell, MTTo Schafer USFS Airport (8U2), Schafer, 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
Public Aircraft
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 › Became lost/disoriented
  • Pilot in command › Clearance, not maintained
  • Pilot in command › In-flight planning/decision, improper

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The purpose of the public use flight was to transport four United States Forest Service (USFS) employees to a remote back-country airstrip. The flight's departure was delayed 2 hours due to heavy rain showers and a thunderstorm. The planned flight route was to follow a highway through a river valley with high terrain (peaks above 8,000 feet) on both sides until reaching a point where the highway diverged from the river. At that point, the flight was to leave the highway and follow the river. Analysis of available weather data indicated that as the airplane proceeded along the river valley, ridge tops on both sides of the valley became obscured. Bases of the overcast were probably about 7,000 feet msl. Ragged clouds and mist were probably present beneath the overcast due to recent rain showers in the area. Slant visibility was likely diminished. Local pilots reported that in these type weather conditions the numerous drainages that feed into the river valley can be similar in appearance. The pilot made a position call about 15 minutes after takeoff stating that he was over a small town located close to the point where the flight was to leave the highway. This was the last radio communication received from the airplane. Analysis of radar data available for the first 8 minutes of the flight indicated the airplane was not at the position reported by the pilot, but was actually well short of this position. About 15 minutes later, witnesses heard and saw the airplane flying up a drainage located short of the reported position. This drainage ended in a box canyon. Inspection of the accident site indicated that the airplane was in a left climbing turn when it impacted steep terrain near the head of the drainage at an elevation of about 6,600 feet. The airplane nosed over, came to rest inverted, and a fire erupted. Three of the occupants exited the burning wreckage. All communications equipment, survival equipment and foul-weather gear aboard the airplane were destroyed in the fire. One of the three initial survivors died from his injuries the following morning. At that time, the remaining two survivors decided to depart the site for lower elevation due to extreme cold and precipitation. Searchers found the wreckage later that afternoon. The two survivors walked out to the highway 2 days after the accident. No abnormalities were noted during examination of the airplane that would have prevented normal operation. When the pilot took a check ride that allowed him to act as pilot in command of public use flights carrying passengers into the back-country, he reported to the check pilot that he had 100 hours flight time in "typical terrain (over mountains)." USFS standards required 200 hours flight time in typical terrain. However, the standards did not define typical terrain. Examination of the pilot's logbook revealed that it did not include a specific record of back country or mountain flying experience. Review of the past 2 years of logbook entries revealed a total of only 15 entries (14 hours flight time) that included a takeoff or landing at a back-country airport.

Probable cause

The pilot's misidentification of the airplane's location, which resulted in his improper decision to fly into the wrong drainage, and his failure to maintain terrain clearance while executing a turn to reverse course after he realized his navigational error. Contributing factors were the low visibility due to mist, obscuration of the mountainous terrain, and the pilot's lack of experience in back country flying.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA04GA192
Event ID
20040930X01543
Case number
SEA04GA192
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, 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: e112f1775306db3b80000ffe3a0c2a69f19827e744986ce85873255946c0fbf9; retrieved 2026-09-18T14:34:37.341Z.