FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR12LA099 · Cessna 172M

9 Feb 2012 · Cusick, WA, United States

Cessna 172M · Accident: loss of engine power (partial) en route

From Coeur D'Alene Airport - Pappy Boyington Field (COE) to Chewelah Municipal Airport (1S9)

Report a problem

Event

NTSB case
WPR12LA099
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 172M

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
N5100R
Operator
Jim Miller
Onboard fatalities
Unknown
Route
From Coeur D'Alene Airport - Pappy Boyington Field (COE), Coeur d'Alene, IDTo Chewelah Municipal Airport (1S9), Chewelah, WA
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
Defining eventThe 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 (partial)
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

  • Not determined › Not determined

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

NTSB narrative

The pilot reported that, after takeoff, the engine began to run roughly and lose power. He applied carburetor heat, which did not restore power. The pilot's further troubleshooting attempts were unsuccessful, and he initiated a forced landing. The engine subsequently lost power, and, during the landing to a nearby field, the airplane struck several trees. A postaccident examination of the airframe revealed about 8 gallons of fuel were remaining in the right tank. The left fuel tank was breached during the impact, and it was found empty due to the breach. Further examination of the airplane and a subsequent engine run revealed no mechanical malfunctions or failures that would have precluded normal operation.

Probable cause

A total loss of engine power during cruise flight for reasons that could not be determined because postaccident examination did not reveal any anomalies that would have precluded normal operation.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR12LA099
Event ID
20120209X14823
Case number
WPR12LA099
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 4489cf01f274d4f234132c772acefa6941a371486d3490b6335b0323f1f48eda; retrieved 2026-09-15T17:13:03.714Z.