FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN11LA413 · Cessna 172N

18 Jun 2011 · Bedford Park, IL, United States

Aviation Professionals Cessna 172N · Accident: powerplant system/component malfunction/failure en route

From Lansing Municipal Airport (IGQ) to Chicago Midway International Airport (MDW)

Report a problem

Event

NTSB case
CEN11LA413
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
Unknown
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 172N

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
N172NT
Onboard fatalities
Unknown
Route
From Lansing Municipal Airport (IGQ), Lansing, ILTo Chicago Midway International Airport (MDW), Chicago, IL
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
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
Powerplant system/component malfunction/failure
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

  • Aircraft › Aircraft power plant

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

NTSB narrative

The pilot reported that about 5 miles from the destination the engine started to run rough, and about 20 seconds later the engine lost power. His attempts to restore engine power were unsuccessful. The pilot subsequently performed a forced landing to a field. During the landing roll the airplane nosed over on the soft field. A postaccident examination revealed that the No.3 cylinder exhaust valve push rod had buckled and fractured near mid-length. The push rod fracture surfaces showed failure signatures consistent with overload precipitated by a stuck valve. No other engine anomalies were observed.

Probable cause

A loss of engine power due to a fractured push rod precipitated by a stuck exhaust valve.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN11LA413
Event ID
20110623X95521
Case number
CEN11LA413
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: 9959e2c953b39a3d991d15fc503ecaefa6a2a4cef4e6f7386d19b20a6adfc815; retrieved 2026-09-15T16:20:25.553Z.