FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR11FA241 · Cessna R172K

28 May 2011 · Cold Springs, NV, United States

Cessna R172K · Accident: VFR encounter with IMC en route

From Roseburg Regional Airport (RBG) to Reno Tahoe International Airport (RNO)

Report a problem

Event

NTSB case
WPR11FA241
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
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 R172K

Aircraft type
Cessna 172
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
N9831V
Onboard fatalities
Unknown
Route
From Roseburg Regional Airport (RBG), Roseburg, ORTo Reno Tahoe International Airport (RNO), Reno, 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
En route
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 › Action/decision

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

NTSB narrative

The pilot, who held an instrument rating, was flying the airplane for the owner, who did not hold an instrument rating, from the departure airport, where instrument meteorological conditions (IMC) prevailed, to another airport, where visual meteorological conditions prevailed. Forecast weather conditions along the route of flight called for areas of mountain obscuration and precipitation, including snow. The pilot filed an instrument flight rules (IFR) flight plan, and he was issued an IFR clearance. About 44 minutes into the flight, the pilot canceled the IFR clearance and continued the flight under visual flight rules (VFR). About 16 minutes later, the pilot amended the flight’s destination to an airport that was along the route of flight, but closer than the original destination, and about 19 minutes after that, the air traffic controller told the pilot that radar service was terminated. About 1.5 hours after radar service was terminated, the airplane impacted mountainous terrain at an elevation of about 6,400 feet mean sea level (msl). The wreckage was confined to the impact area, and the damage was consistent with controlled flight into terrain. The accident site was located along the route of flight beyond the amended destination and about 20 miles short of the original destination, indicating that the pilot had over flown the amended destination and may have been attempting to reach the original destination. About 30 minutes before the accident, light rain and mountain top obscuration were reported in the vicinity of the original destination airport. At the time of the accident, the original destination airport was reporting cloud layers with bases about 6,300 and 6,800 feet msl. Given the forecast and reported weather conditions, it is likely that the pilot encountered IMC and was unable to see the terrain prior to the airplane colliding with it.

The toxicology report for the pilot showed positive results for amphetamine, methamphetamine, and trimethoprim, an antibiotic used to treat infections. However, it could not be determined from available samples when the amphetamine and methamphetamine had been ingested, and, therefore, whether they would have impaired the pilot’s performance. Review of the pilot's medical records indicated that he had diabetes, and, one day prior to the accident, he had been treated for a skin infection. It is possible that the pilot was distracted by his medical condition and that this may have impaired his performance and contributed to his decision to continue the VFR flight into deteriorating weather conditions.

Probable cause

The pilot's continued visual flight rules flight into instrument meteorological conditions, which resulted in a controlled collision with terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR11FA241
Event ID
20110531X35220
Case number
WPR11FA241
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2011-05-29.
  • API snapshot SHA-256: c401a865eb21442b97dd6c7a03cb00a05c8115242795b6f4b8f48df95cfb5e05; retrieved 2026-09-13T21:26:39.008Z.