FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DEN83LA102 · Cessna 180

24 Apr 1983 · FT. SMITH, MT, United States

Cessna 180 · Accident: loss of engine power en route

From an unrecorded airport to Hellinger Airport (MT02)

Report a problem

Event

NTSB case
DEN83LA102
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
Visual Meteorological Cond

Cessna 180

Aircraft type
Cessna 180
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
N9171T
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo Hellinger Airport (MT02), Hardin, MT
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
Loss of engine power
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

  • Reason for occurrence undetermined

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

AFTER TAKING OFF FROM FT SMITH, THE PLT LEVELED AT 500 FT AGL & FOLLOWED A RIVER TO LOOK AT SOME PROPERTY APRX 5 MI AWAY. WHILE EN ROUTE, THE ENGINE BEGAN TO SPUTTER & RUN IRREGULARILY. HE PERFORMED A SUCCESSFUL PRECAUTIONARY LANDING IN A FIELD WHERE HE MADE A THOROUGH ENGINE RUN-UP & ALL SYSTEMS CHECKED NORMAL. THINKING THAT THE ENGINE MAY HAVE PASSED SOME WATER, HE ELECTED TO TAKEOFF & FLY TO HARDIN, MT. APRX 2 MIN AFTER TAKEOFF, THE ENGINE BEGAN SPUTTERING & RUNNING IRREGULAR AGAIN; HOWEVER, THE PILOT COULD GET NO IMPROVEMENT WHEN HE ATTEMPTED TO RESTORE THE POWER. A FORCED LANDING WAS MADE IN A FIELD BEYOND SOME POWER LINES. WHILE APPLYING HEAVY BRAKES TO STOP BEFORE REACHING A DITCH, THE PLANE NOSED OVER. AN EXAM OF THE ACFT & ENGINE WAS MADE, BUT NO CAUSE FOR THE POWER LOSS WAS FOUND.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record DEN83LA102
Event ID
20001214X42662
Case number
DEN83LA102
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: 64bfa613c4109e4cbbeb968c09e2fb92be3138626491554cb3f9f3ec448bd368; retrieved 2026-09-23T22:21:30.120Z.