WPR18FA001 · Cirrus Design Corp SR22
Cirrus Design Corp SR22 · Accident: VFR encounter with IMC en route
From Crater Lake-Klamath Regional Airport (LMT) to Rogue Valley International-Medford Airport (MFR)
Event
- NTSB case
- WPR18FA001
- 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
Cirrus Design Corp SR22
- Aircraft type
- Cirrus SR22
- 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
- N6083D
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Crater Lake-Klamath Regional Airport (LMT), Klamath Falls, ORTo Rogue Valley International-Medford Airport (MFR), Medford, OR
- Aircraft age
- About 14 years (built 2003)
- 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
- Destroyed
Cause areas
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
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.
Probable cause
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR18FA001
- Event ID
- 20171002X44715
- Case number
- WPR18FA001
- 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. 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: 436bce5d30c3a5f67330ea10b2ac247f19471b1d823c9f153953781a6c83a57c; retrieved 2026-09-15T06:19:23.899Z.