WPR12FA091 · Cessna T206H
Cessna T206H · Accident: VFR encounter with IMC during initial climb
From Show Low Regional Airport (SOW) to Boulder City Municipal Airport (KBVU)
Event
- NTSB case
- WPR12FA091
- 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
- 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 T206H
- 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
- N445GH
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Show Low Regional Airport (SOW), Show Low, AZTo Boulder City Municipal Airport (KBVU), Boulder City, NV
- 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
- Initial climb
- 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
- Personnel issues › Psychological
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.
NTSB narrative
The private pilot departed before dawn in the single-engine airplane with three passengers. One passenger reported that after an uneventful departure, the airplane made an unexpected right turn, with no comment from the pilot. A ground witness observed the airplane in an unusual attitude shortly after takeoff. The airplane then flew out of her view, and a few seconds later, she observed an explosion beyond the runway. The debris field and associated ground scars were adjacent and perpendicular to the runway. The airplane damage and debris distribution were consistent with a high-speed, right-wing-low descent into the ground. All sections of the airplane were located at the accident site, and no anomalies were noted with the airframe or engine that would have precluded normal operation. The damage to the propeller and turbocharger was consistent with the engine producing power at the time of impact.
The airport's automated weather observation system was reporting 8-mile visibility, but with low broken cloud ceilings about the time the pilot would have been performing his preflight inspection. A rapid degradation in weather conditions occurred over the 10-minute-period following the accident, including freezing dense fog and low overcast cloud ceilings. The airport was located on the outskirts of a town, and the route of flight following the initial turn was toward a sparsely populated area. The moon was below the horizon at the time of the accident.
The pilot did not possess an instrument rating, which coupled with the lighting and weather conditions, could have made him vulnerable to spatial disorientation. The airplane's impact trajectory was consistent with the pilot experiencing this phenomenon. Additionally, an instrument-rated pilot departed from the same runway shortly after the accident unaware that it had occurred. He reported that before departure, he could see haze beginning to form close to the ground but could still see clear skies in his direction of travel and presumed that visual meteorological conditions existed. However, during the initial climb, he inadvertently entered a fog layer, and became disoriented.
The pilot had been taking prescription medication for anxiety, the use of which he did not report in any application for a Federal Aviation Administration medical certificate. Although use of such medication may impair the mental and/or physical ability required for flight, it was not possible to conclusively determine what role, if any, the medication played in the accident.
Probable cause
The pilot’s encounter with low clouds/low visibility conditions during the initial climb, which resulted in spatial disorientation and loss of airplane control.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR12FA091
- Event ID
- 20120204X03117
- Case number
- WPR12FA091
- 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. 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: 882c2bb89a9883ac0e5e080d72601ec117213864f92b2c81f7d3d8ead7b0ef4f; retrieved 2026-09-13T22:09:47.735Z.