FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN16FA042 · Cessna 182G

16 Nov 2015 · Sandia Park, NM, United States

Cessna 182G · Accident: VFR encounter with IMC en route

From Kickapoo Downtown Airport (KCWC) to Double Eagle II Airport (KAEG)

Report a problem

Event

NTSB case
CEN16FA042
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 182G

Aircraft type
Cessna 182
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
N2440R
Operator
Unknown
Onboard fatalities
Unknown
Route
From Kickapoo Downtown Airport (KCWC), Wichita Falls, TXTo Double Eagle II Airport (KAEG), Albuquerque, NM
Aircraft age
About 51 years (built 1964)
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 · cruise
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 › Action/decision
  • 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 pilot did not receive a weather briefing nor file a flight plan prior to departing on a VFR cross-country flight. Radar data showed that the airplane proceeded west on course after departure. As the airplane neared a north/south-oriented mountain range, it deviated from the direct course to the destination, turning to the southwest and then to the north. Overlaying the airplane's flight path on a weather radar image showed that the airplane began the deviation as it approached an area of precipitation. Additionally, photographs taken by a passenger during the flight indicated that the airplane was flying above a solid overcast. As the airplane flew north parallel to the eastern slope of the mountain range, the pilot contacted the destination airport's air traffic control tower and reported that he was descending out of 13,000 ft, that he was between cloud layers, and that he wanted to perform an instrument landing system approach to the airport . He reported being 5 miles east of the airport; however, radar data indicated that the airplane was about 25 miles east and on the other side of the mountain range from the destination airport. The pilot then said the situation was "pretty hairy . . . I can see the ground . . . I'm just trying to maintain visibility right now," and, a few minutes later, "we are really having a tough time trying to get out of this [*mess]." Radio contact was lost shortly thereafter. Radar data indicated an erratic flight path and a varying groundspeed during the last 4 minutes of the flight. Radar contact was lost, and the airplane impacted heavily wooded mountainous terrain in a near vertical attitude. Examination of the wreckage revealed no evidence of any anomalies that would have precluded normal operation of the airplane.

In addition to the precipitation indicated by the weather radar imagery, satellite imagery showed cloud cover over the accident area with tops about 28,000 ft. The weather imagery, the pilot's statements, the erratic flight path, and the airplane's impact attitude are consistent with the airplane entering instrument meteorological conditions and the pilot developing spatial disorientation and losing control.

Toxicological testing revealed 0.326 (ug.mL, ug/g) sertraline, a prescription antidepressant, in the pilot's heart blood and desmethylsertraline, a metabolite of sertraline, in the pilot's liver and heart blood. The pilot's medical records indicated that he was being treated for depression with sertraline, and, several months before the accident, the pilot's health care provider noted that the pilot's depression was well controlled.. Therefore, it is unlikely that effects from the pilot's depression or use of sertraline contributed to the accident.

Probable cause

The pilot's continued visual flight into instrument meteorological conditions, which resulted in spatial disorientation and a loss of control.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN16FA042
Event ID
20151117X72052
Case number
CEN16FA042
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, coordinates. 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: 2e1b65d1da258d719c286fc6d5bf03f028fcd50d3809007e96e6749832734d09; retrieved 2026-09-14T21:34:20.295Z.