DEN83FA084 · Cessna 182
Cessna 182 · Accident: in flight encounter with weather en route
From Evanston-Uinta County Airport-Burns Field (EVW) to Salt Lake City International Airport (SLC)
Event
- NTSB case
- DEN83FA084
- 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
- 0 · 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
- Instrument Meteorological Cond
Cessna 182
- 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
- N9377X
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Evanston-Uinta County Airport-Burns Field (EVW), Evanston, WYTo Salt Lake City International Airport (SLC), Salt Lake City, UT
- 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
- Tree(s)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Pilot in command › Flight into known adverse weather, continued
- Pilot in command › Judgment, improper
- Pilot in command › Preflight planning/preparation, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE AFCT COLLIDED WITH A TREE AND CRASHED DURING A GO-AROUND. THE WEATHER WAS IMC AND THE PILOT AND PASSENGER WERE SERIOUSLY INJURED. THE PILOT RECEIVED A WEATHER BRIEFING AND WAS TOLD THAT VFR FLT, ON HIS INTENDED ROUTE, WAS NOT RECOMMENDED DUE TO LOW CEILINGS AND SNOW SHOWERS. THE PILOT WAS NOT INSTRUMENT RATED. HE INITIATED THE FLT ANYWAY AND ENCOUNTERED THE WEATHER IN A VALLEY NEAR HUNTSVILLE. HUNTSVILLE IS SURROUNDED BY MOUNTAINS. THE PILOT CIRCLED THE HUNTSVILLE AREA FOR ABOUT 1 HOUR WHILE TALKING TO FSS AND THE SHERIFFS DEPT. THE WEATHER WAS DETERIORATING AND THE PILOTWAS TRYING TO LOCATE THE CAR LIGHTS ON THE LANDING STRIP SET UP BY THE SHERIFF. THE PILOT FOUND THE STRIP AND MADE 3 ATTEMPTS TO LAND. ON THE 3RD ATTEMPT HE TOUCHED DOWN. THE ACFT STARTED SWERVING ACCORDING TO THE PILOT AND HE STARTED A GO-AROUND. THE ACFT WING HIT A LARGE TREE AND CRASHED 99 FT BEYOND THE TREE.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record DEN83FA084
- Event ID
- 20001214X42394
- Case number
- DEN83FA084
- 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 1983-03-24.
- API snapshot SHA-256: bed7d543292665c461453248be8135505e4e3dc5b0b21261243261c4709d1679; retrieved 2026-09-21T17:59:37.895Z.