CEN17FA354 · Cirrus Design Corp SR22
Cirrus Design Corp SR22 · Accident: loss of control in flight while maneuvering
From Northern Colorado Regional Airport (FNL) to Canyonlands Regional Airport (CNY)
Event
- NTSB case
- CEN17FA354
- 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
- 4 · 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
- N462SR
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Northern Colorado Regional Airport (FNL), Fort Collins, COTo Canyonlands Regional Airport (CNY), Moab, UT
- Aircraft age
- About 10 years (built 2007)
- 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
- Maneuvering
- 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
- Loss of control in flight
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Action/decision
- Personnel issues › Psychological
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The non-instrument-rated private pilot and three passengers departed on a night cross-county flight over mountainous terrain. Radar track data showed that the airplane traveled mainly on a southwesterly heading directly towards its destination with a series of altitude changes. About 5 minutes before the accident, the airplane turned to the northwest, a deviation off the destination course, and continued northwest for about 12 miles. After the turn, a passenger sent a text message to a family member stating that they were "taking the long way around, lots of weather, keep you posted." Shortly thereafter, the airplane entered a gradual left turn to the southwest, descending from 11,500 ft to 11,300 ft, then climbing back to 11,400 ft. The last recorded radar return was about 1/4 mile south of the accident site, which was located at an elevation of 10,800 ft. Postaccident examination of the airframe and engine showed severe fragmentation of the airplane consistent with a high-energy impact and did not reveal any preimpact anomalies that would have precluded normal operation.
The flight was likely operating in instrument meteorological conditions (IMC) at the time of the accident, including light to moderate icing conditions. The airplane likely encountered intermittent IMC beginning about 30 minutes after takeoff, and continued into an area of solid IMC about 3 minutes before the accident occurred.
There was no record of the pilot retrieving preflight weather information from an official, access-controlled source, and what weather information, if any, he obtained before or during the flight could not be determined. Based on the weather forecasts and information valid before the airplane departed and while en route, and the equipment available onboard the airplane, there was sufficient weather information available to the pilot before and during the flight to make informed decisions regarding the weather he would likely encounter.
The night instrument conditions present at the time of the accident were conducive to the development of spatial disorientation and the circumstances of the accident. The non-instrument-rated pilot's continued flight into IMC, the airplane's descending turn depicted on radar, and the fragmentation of the wreckage due to high-energy impact are all consistent with the known effects of a loss of control due to spatial disorientation. It is likely that, while maneuvering, the pilot experienced spatial disorientation, which resulted in a loss of control and subsequent descent into terrain.
Probable cause
The non-instrument-rated pilot's inadequate preflight weather planning, his decision to depart into forecast instrument meteorological conditions along the route of flight, and his continued visual flight into instrument meteorological conditions, which resulted in spatial disorientation and a subsequent loss of airplane control.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN17FA354
- Event ID
- 20170916X12649
- Case number
- CEN17FA354
- 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 2017-09-16.
- API snapshot SHA-256: 3323b429e9c50b2cb5242702ca29f7450307ebac8e5fef6684b0561d1dbdb19d; retrieved 2026-09-15T06:16:58.767Z.