CEN18FA168 · Cirrus Design Corp SR22
Cirrus Design Corp SR22 · Accident: VFR encounter with IMC during initial climb
From Centennial Airport (KAPA) to Grand Junction Regional Airport (KGJT)
Event
- NTSB case
- CEN18FA168
- 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
- 1 · 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
- Visual 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
- N507TX
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Centennial Airport (KAPA), Denver, COTo Grand Junction Regional Airport (KGJT), Grand Junction, CO
- Aircraft age
- About 13 years (built 2005)
- 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
- Destroyed
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Conditions/weather/phenomena
- 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 instrument-rated private pilot departed on a visual flight rules cross-country flight just before the end of civil twilight. After departing to the north, the pilot turned onto a left downwind to depart the area toward the south; the controller advised the pilot to stay west of the extended runway centerline, which the pilot acknowledged. However, about 2 minutes after takeoff, the airplane turned east and crossed the extended centerline. After crossing the centerline, the controller asked the pilot to state his intentions, and the pilot replied that he was going to return to the airport. The airplane turned back toward the airport and began tracking west toward the extended centerline; radar contact was lost several minutes later.
The airplane impacted a field about 2.5 miles to the south of the approach end of the runway. The airplane was massively fragmented during the impact and debris was scattered for about 1,200 ft. The damage to the airplane and the ground scars at the accident site were consistent with the airplane impacting in a right wing low, nose low attitude with relatively high energy.
The postaccident examination of the engine and propeller assembly did not reveal any preimpact anomalies that would have precluded normal operation. Signatures were consistent with the engine producing power and the propeller developing thrust at the time of impact. While the massive fragmentation precluded functional testing of the flight controls, there was no damage or failure that suggested preimpact anomalies with the airframe or flight controls.
While visual meteorological conditions prevailed at the airport, statements from two pilots flying instrument approaches to runway 35R suggest that the pilot likely encountered and was flying in the clouds to the south of the airport just before the accident.
A review of radar data and voice communications revealed that the instructions issued by the controller, to the pilot, were reasonable and in accordance with air traffic control procedures. Investigators were not able to establish why the pilot did not comply with air traffic control instructions.
The accident flight was the airplane's first flight after completion of an annual inspection, and the pilot was flying to meet his family for an event in another state. It is likely that the pilot was experiencing self-induced pressure to complete the flight as planned in order to maintain the family's schedule of events, and as a result, chose to depart on the visual flight rules flight over mountainous terrain at night in marginal weather conditions. The pilot's logbook was not recovered, and the recency of his instrument flight experience could not be determined.
Based upon the reported weather conditions, the location and fragmentation of the wreckage, and radar data, it is likely that the pilot experienced spatial disorientation shortly after entering the clouds which resulted in a loss of control and descent into terrain. The reason for the pilot's stated intention to return to the airport after takeoff could not be determined, but it is possible that he became distracted and that distraction contributed to his disorientation and loss of control.
Probable cause
The pilot's loss of control due to spatial disorientation. Contributing to the accident was the pilot's self-induced pressure to fly the airplane at night in marginal weather conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN18FA168
- Event ID
- 20180511X35249
- Case number
- CEN18FA168
- 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, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2018-05-12.
- API snapshot SHA-256: d4279357332f3ec155ad1a4f0721e27488f9bb3240a6629b6c0446d9f216030a; retrieved 2026-09-15T06:40:21.384Z.