WPR17FA045 · Cessna T210K K
Cessna T210K K · Accident: VFR encounter with IMC en route
From Scottsdale Airport (SDL) to Telluride Regional Airport (TEX)
Event
- NTSB case
- WPR17FA045
- 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
Cessna T210K K
- Aircraft type
- Cessna 210
- 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
- N272EF
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Scottsdale Airport (SDL), Scottsdale, AZTo Telluride Regional Airport (TEX), Telluride, CO
- Aircraft age
- About 47 years (built 1970)
- 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
- Personnel issues › Experience/knowledge
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The non-instrument-rated private pilot departed his home airport with three family members on a cross-country visual flight rules (VFR) flight over mountainous terrain. The forecast weather conditions called for instrument meteorological conditions (IMC) and mountain obscuration due to clouds, precipitation, and mist along the route of flight and at the accident site. The co-owner of the airplane, who held an instrument rating, had reviewed the pilot's flight plan and the forecast weather conditions two days before the accident and informed the pilot that he should drive to his destination as the weather would not allow for VFR flight. However, the pilot elected to proceed with the flight contrary to the co-owner's recommendation. The pilot entered the flight route into the Foreflight mobile application but did not receive any weather briefings from flight service or the mobile application before departure.GPS data recovered from an electronic display device installed in the airplane showed that the airplane departed, entered a climb on a northerly heading, and maintained this direction for the remainder of the flight. After the airplane reached a peak altitude of about 8,000 ft above mean sea level (msl), it descended to 7,000 ft msl and then gradually descended to about 6,000 ft msl, where it remained until near the end of the flight. The airplane subsequently impacted the tops of trees on the rising face of a cliff about 6,600 ft msl. The orientation and length of the wreckage path were consistent with a controlled flight into terrain impact. Track data from the GPS showed that the airplane maintained a straight course after its departure all the way to the mountain rim, which had a published elevation between 6,700 feet msl and 8,000 feet msl. Postaccident examination of the airplane revealed no evidence of any preimpact mechanical malfunctions or failures.
A medical study revealed that each of the 4 fatally injured occupants sustained severe traumatic injuries that would have been rapidly fatal. Furthermore, the study showed there was no evidence to suggest that faster identification of the accident or earlier medical attention would have changed the outcome.
Although the autopilot switch was found in the "ON" position at the accident site, the autopilot was likely not engaged as the airplane's ground track and altitude varied, consistent with the pilot hand flying the airplane.
A weather study revealed that the airplane departed in visual meteorological conditions (VMC) and likely entered a combination of VMC and IMC after it climbed above 7,000 ft. Minutes later, the airplane encountered IMC and did not return to VMC for the remainder of the flight. The pilot's descent from 8,000 ft to 7,000 ft and then to 6,000 ft, occurred after the airplane entered IMC and indicates that he may have been attempting to return to VMC by descending, but was unsuccessful. Upon encountering IMC, the pilot could have turned around and returned to VMC, but he elected to continue and descend about 750 feet below the lowest peak terrain elevation in the area. The airplane's altitude increased rapidly by about 500 ft just seconds before the airplane impacted terrain suggesting that the pilot may have been alerted by the onboard terrain awareness warning system, which had been successfully tested by the co-owner, or observed the terrain and maneuvered to avoid the impact.
Probable cause
The non-instrument-rated pilot's improper decisions to begin and to continue a flight under visual flight rules into instrument meteorological conditions, which resulted in controlled flight into terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR17FA045
- Event ID
- 20170103X14851
- Case number
- WPR17FA045
- 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: dd511b325cb8090d2099c97aa5fd769d57aa6d29e98d8c62bd304c841b45d65b; retrieved 2026-09-14T22:05:09.345Z.