FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI95LA023 · Cessna 172F

22 Oct 1994 · Cross Plains, WI, United States

Cessna 172F · Accident: loss of engine power en route

From Waukesha County Airport (UES) to Waukesha County Airport (UES)

Report a problem

Event

NTSB case
CHI95LA023
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 172F

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
N7969U
Operator
Unknown
Onboard fatalities
Unknown
Route
From Waukesha County Airport (UES), Waukesha, WITo Waukesha County Airport (UES)
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

  • Pilot in command › Carburetor heat, not used

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

NTSB narrative

THE PILOT STATED THAT HE WAS CRUISING AT 5,000 MSL AND REDUCED THE ENGINE RPM TO BETWEEN 1,000 AND 1,200 DURING A DESCENT TO 2,000 MSL. WHEN HE ATTEMPTED TO LEVEL OFF WITH POWER THE ENGINE DID NOT RESPOND. HE MADE A FORCED LANDING IN A ROUGH/UNEVEN FIELD. HE TOLD AN INSPECTOR FROM THE FAA THAT HE PUMPED THE THROTTLE AND MOVED THE MIXTURE TO RICH, BUT HE DID NOT USE THE CARBURETOR HEAT. A WEATHER REPORTING STATION TEN MILES EAST OF THE ACCIDENT SITE WAS REPORTING A TEMPERATURE OF 60 DEGREES (F) AND A DEW POINT OF 51 DEGREES (F), AT THE TIME OF THE ACCIDENT. CONDITIONS WERE CONDUCIVE TO CARBURETOR ICING.

Probable cause

the pilot's failure to use carburetor heat. Factors were carburetor icing conditions and rough/uneven terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI95LA023
Event ID
20001206X02415
Case number
CHI95LA023
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: db6c237b8e545477a39457c061819e4c26c1fbfdd9c7b04be20f0713119b579a; retrieved 2026-09-23T00:30:33.033Z.