DEN82DA190 · Cessna 310P
Cessna 310P · Accident: in flight encounter with weather en route
From AI · Cody, WY to AI · Redding, CA
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- DEN82DA190
- 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 310P
- Aircraft type
- Cessna 310
- 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
- N5836M
- Operator
- Kubo Sadeo
- Onboard fatalities
- Unknown
- Route Possible conflict
- From AI · Cody, WYTo AI · Redding, CA
- 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
- Substantial
Cause areas
- Pilot in command › Diverted attention
- Pilot in command › In-flight planning/decision, poor
- Pilot in command › Proper altitude, not maintained
- Pilot in command › VFR flight into imc, continued
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT STATED HE BECAME DISORIENTED WHILE FLYING FROM SALT LAKE CITY TO WENDOVER. HE DESCENDED TO 8000 FT TO KEEP CLEAR OF ICE AND HAIL AND COULD NOT RECEIVE A NAVIGATIONAL SIGNAL FROM THE WENDOVER OR BONNEVILLE NAVIGATIONAL FACILITY.WHILE ATTEMPTING TO ESTABLISH HIS POSITION ON HIS SECTIONAL THE AIRCRAFT DESCENDED INTO THE GROUND. INVESTIGATION REVEALED THERE WERE NO MALFUNCTIONS WITH THE EN ROUTE FACILITIES AT BONNEVILLE OR WENDOVER. THE MINIMUM EN ROUTE ALTITUDE TO RECEIVE A SIGNAL BETWEEN SALT LAKE CITY AND WENDOVER IS 9000 FT.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record DEN82DA190
- Event ID
- 20020917X04506
- Case number
- DEN82DA190
- 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-09-13.
- API snapshot SHA-256: 1db55946c546d75c4e2aa5efa9364fc7c58c6de3ecdf2fefa068458f479c233a; retrieved 2026-09-22T02:53:33.263Z.