FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA06FA115 · Cessna TU206G

8 Jun 2006 · Mullan, ID, United States

Cessna TU206G · Accident: in flight encounter with weather while maneuvering

From Coeur D'Alene Airport - Pappy Boyington Field (COE) to Missoula Montana Airport (MSO)

Report a problem

Event

NTSB case
SEA06FA115
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
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
Charter & commuter
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 TU206G

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
N5136X
Operator
Unknown
Onboard fatalities
Unknown
Route
From Coeur D'Alene Airport - Pappy Boyington Field (COE), Coeur d'Alene, IDTo Missoula Montana Airport (MSO), Missoula, 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 135: Air Taxi & Commuter
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
Maneuvering
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
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
Visual flight rules (VFR) flight into instrument meteorological conditions (IMC); Tree(s)
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

  • Pilot in command › Clearance, not maintained
  • Pilot in command › VFR flight into imc, performed

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 flew into terrain while maneuvering after encountering weather. Before the first leg of the two-leg on-demand air taxi flight began, the pilot had checked the weather with the FSS for the entire route of flight. The specialist reported mountain obscuration and reduced visibility with rain and fog/overcast. The worst of the weather was reported for the second leg of the flight through the mountain pass with the fog/overcast reported as indefinite at 100 feet. After departure from the originating airport, the pilot requested an updated weather briefing. The weather report was similar and had not changed significantly. The flight landed at the first destination without incident. While on the ground, the pilot once again contacted the FSS to get an updated briefing for the final leg of the flight. The specialist reported that VFR flight was still not recommended and that there were AIRMETs for mountainous terrain obscured and occasional IFR conditions. An automated surface observing system (ASOS) is located at the mountain pass through which the flight was intending to fly. The ASOS at the time was reporting IFR with visibility 1/4 mile in fog, and ceiling broken at 100 feet, and overcast at 600 feet. The destination airport was reporting moderate to heavy showers which were slowly moving in. The specialist recommended to the pilot that he should wait at the airport as the forecast was showing an improving trend throughout the day. A witness traveling westbound on the interstate that runs east/west through the mountain pass, reported that she observed an aircraft traveling eastbound directly over the interstate. She estimated that the aircraft was just below the ceiling, which was a solid layer about 500 feet agl. She stated that from about 1 mile east to 1 mile west of the top of the pass, the clouds were directly on the road. As she descended lower in the valley, the cloud bases were no higher than about 500 feet agl. On site investigation of the wreckage indicated that the aircraft collided with several trees and subsequently the steeply rising terrain in an easterly direction on the south side of the interstate and about 150 feet above the roadway surface. At the approximate time of the accident, the ASOS located about 3 miles east of the accident site was reporting an indefinite ceiling at 100 feet, and a visibility of zero.

Probable cause

The pilot's VFR flight into IMC and his subsequent failure to maintain terrain clearance. The pilot's inadequate inflight planning/decision, mountain obscuration, trees and high terrain were factors.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA06FA115
Event ID
20060613X00732
Case number
SEA06FA115
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: 6ddbdcb6b315c588a4b80b2c64d10229158fba507fd1712400e27aa464b6ed98; retrieved 2026-09-18T12:56:54.710Z.