The U.S. aircraft register, updated daily
Accidents · NTSB WPR18FA001 · Final report

Cirrus Design CORP SR22 accident near Klamath Falls, Oregon, October 1, 2017

On October 1, 2017 at about 5:43 pm local time, a 2003 Cirrus Design CORP SR22, registered N6083D, was destroyed in an accident during enroute near Klamath Falls, Oregon. It was a personal flight under general aviation rules (Part 91). 2 people were killed. The weather was instrument conditions (cloud, fog or low visibility).

The NTSB's probable cause their words, unchanged

The noninstrument rated pilot's decision to depart on a cross-country flight with en route weather conditions forecasted to be less than visual meteorological conditions and then to continue flight into instrument meteorological conditions, which resulted in controlled flight into terrain.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
October 1, 2017 · about 5:43 pm local time
Place
Klamath Falls, Oregon · map
Type
Accident
Injuries
2 people were killed.
Weather
instrument conditions (cloud, fog or low visibility)
Aircraft
Cirrus Design CORP SR22 NO SERIES, built 2003
Registration
N6083D · no longer on the register · serial 0612
Damage
Destroyed
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The noninstrument-rated private pilot, departed on a cross-country flight over mountainous terrain into an area of instrument meteorological conditions (IMC); IMC conditions had been forecasted earlier that morning. An acquaintance of the pilot, who was also a pilot, stated that he spoke with the accident pilot before the flight about the clouds along his intended route. The accident pilot stated that, if he needed to, he would climb above the clouds and look for a hole through which he could descend to the destination. If he could not find a hole in the clouds, then he would return to the departure airport. About 12 minutes into the flight, and after having reached its maximum altitude of 8,700 ft msl and on a heading of 254°, radar track data revealed that the airplane had started a descending left turn.  Over the next 24 seconds the airplane descends from 8,700 ft msl to 8,100 ft msl at a rate of descent of 1,500 ft per minute (fpm). About 12 seconds later the airplane climbed from 8,100 ft to 9,000 ft at an average rate of 4,500 fpm, followed next by a period of about 12 seconds when the airplane descended from 9,000 ft to 7,100 ft at an average rate of descent of 9,500 fpm and an average ground speed of 40 knots. The last radar return, which was 12 minutes 40 seconds into the flight, showed the airplane at an altitude of 7,100 ft (1,700 ft above ground level), and about 638 ft west of the accident site. An on-duty state trooper in the area heard an airplane flying at treetop level and in the clouds just prior to the accident. The trooper then heard the airplane pass over his position with "the engine screaming," after which it entered a left turn and subsequently impacted terrain. A survey of the accident site revealed a linear debris path and damage to the airplane that was consistent with controlled flight into terrain. Examination of the airframe and engine did not reveal evidence of any mechanical anomalies that would have precluded normal operation. An AIRMET, which was valid for an area near the accident site was issued about 2 hours before the accident, advising of ceilings below 1,000 ft, visibility below 3 statute miles, precipitation, and mist. Additionally, an Area Forecast issued earlier that morning revealed widespread instrument meteorological conditions near the area of the accident site, with terrain and mountains obscured through late morning. It is most likely that the pilot encountered IMC en route and was maneuvering to return to visual conditions when the airplane turned left and collided with terrain.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. VFR encounter with IMC during enroute defining event
  2. Loss of visual reference during enroute
  3. Controlled flight into terrain or object (CFIT) during enroute

The NTSB's findings

  • cause Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
  • cause Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Below VFR minima › Decision related to condition
  • cause Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Below VFR minima › Effect on operation
  • Environmental issues › Physical environment › Terrain › Mountainous/hilly terrain › Contributed to outcome

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 170 hours in all; 16 in this make and model; 23 in the last 90 days; 23 in the last 30 days; 52 as pilot in command
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: fatal

The aircraft

  • Airframe total time: 1,439.7 hours
  • Last inspection: annual inspection, December 13, 2016; 23 hours since
  • Maximum gross weight: 3,400 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Cont Motor IO-550 SERIES (piston); 1,440 hours total

The flight

  • Departed from: LMT Klamath Falls OR at 5:30 pm
  • Destination: MFR Medford OR
  • Flight plan: none

Weather at the time

  • Light: daylight
  • Wind: from 310° at 9 knots, gusting 16
  • Visibility: 10 statute miles
  • Temperature: 52°F (11°C), dew point 30°F (-1°C)
  • Altimeter: 30.13 inHg
  • Observation at 5:53 pm from LMT, 24 miles away

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

11 documents, released by the NTSB on July 25, 2019. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.