FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DEN86LTM01 · Cessna 172

22 Dec 1985 · Brigham City, UT, United States

Cessna 172 · Accident: in flight collision with terrain/water en route

From Malad City Airport (MLD) to Ogden Hinckley Airport (OGD)

Report a problem

Event

NTSB case
DEN86LTM01
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 172

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
N64005
Operator
Unknown
Onboard fatalities
Unknown
Route
From Malad City Airport (MLD), MALAD, IDTo Ogden Hinckley Airport (OGD), Ogden, 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 · descent
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 collision with terrain/water
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 › In-flight planning/decision, improper
  • 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 ACFT CONTACTED MOUNTAINOUS TERRAIN DURING A DESCENT THROUGH FOG. THE PLT STATED THAT ON THE RETURN FLT FROM MALAD, ID, HE BEGAN FOLLOWING A MOUNTAIN RANGE WHICH HE BELIEVED WOULD TAKE HIM BACK TO OGDEN. HOWEVER, THE RANGE GUIDED HIM SOUTHWEST OF THE DESIRED COURSE. THE PLT THEN BEGAN A DESCENT INTO THE FOG OVER WHAT HE THOUGHT SHOULD HAVE BEEN WILLARD BAY, AN OPEN VALLEY, BUT IN REALITY HE WAS IN THE PROMONTORY MOUNTAINS. AT AN ALT OF APRX 5000 FT MSL THE PASSENGER SAW BRUSH BENEATH THE ACFT AND SHORTLY THEREAFTER IMPACT WITH THE TERRAIN OCCURRED.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record DEN86LTM01
Event ID
20001214X38409
Case number
DEN86LTM01
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: 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: 7bb8d76cd3004d6f0a4aac14e8a254ff1c081b9813fd3af928ef5f3ead634a19; retrieved 2026-09-21T17:05:34.624Z.