DEN83FTE02 · Cessna 172G
Sun Flying Service Cessna 172G · Accident: in flight encounter with weather en route
From Evanston-Uinta County Airport-Burns Field (EVW) to Sumers Airpark (GWS)
Event
- NTSB case
- DEN83FTE02
- 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
- 0
- 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
Cessna 172G
- Aircraft type
- Cessna 172
- 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
- N5803R
- Operator
- Sun Flying Service
- Onboard fatalities
- Unknown
- Route
- From Evanston-Uinta County Airport-Burns Field (EVW), Evanston, WYTo Sumers Airpark (GWS), Glenwood Springs, CO
- Aircraft age
- Not recorded
- 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
- First occurrenceThe 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
- In flight encounter with weather
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Visual flight rules (VFR) flight into instrument meteorological conditions (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
- Pilot in command › Spatial disorientation
- Pilot in command › VFR flight into imc, inadvertent
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
WHILE ON A FLT FROM EVANSTON, WY TO GLENWOOD, CO, THE PLT ENCOUNTERED "CLOUD TO GROUND" CONDITINS & DIVERTED TOWARD GRAND JUNCTION, CO. HE STATED THAT DUE TO A NAV PROBLEM, HE RADIOED GRAND JUNCTION TOWER TO VERIFY HIS POSITION. GRAND JUNCTION HAD NO RADAR & WAS HAVING DIFFICULTY TRYING TO GET A FIX ON THE ACFT. THEREFORE, THEY CONTACTED DENVER CENTER (DEN CTR). DEN CTR ESTABLISHED RADAR CONTACT AT 1849 MDT. THE TOWER INFORMED THE PLT OF HIS POSITION APRX 40 MI NORTHWEST & PROVIDED A FREQ TO CONTACT DEN CTR. HOWEVER, A SHORT TIME LATER, THE PLT REPORTED HE WAS UNABLE TO CONTACT DEN CTR. SHORTLY AFTER THAT, HE STATED HE WAS LOSING GROUND CONTACT. FOR THE NEXT 35 MIN, TOWER & CTR MADE EVERY POSSIBLE EFFORT TO HELP ORIENT THE PILOT & VECTOR HIM TO GRAND JUNCTION. THE PLT WAS UNABLE TO MAINTAIN A HEADING OR AN ASSIGNED ALTITUDE. SUBSEQUENTLY, THE PLANE CRASHED IN MOUNTAINOUS TERRAIN. DURING AN INVESTIGATION, THE NAV RECEIVER WAS FOUND ON 117.4 MHZ, THE GRAND JUNCTION VOR FREQ WAS 112.4 MHZ.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record DEN83FTE02
- Event ID
- 20020917X04544
- Case number
- DEN83FTE02
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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 1982-10-27.
- API snapshot SHA-256: b98504adb6736df2403451137eff471fa56b60940c3c594b246a6891e747e487; retrieved 2026-09-21T07:36:13.634Z.