FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN12LA077 · Cessna 152

22 Nov 2011 · Princeton, MN, United States

Ascend Aviation Cessna 152 · Accident: loss of engine power (partial) on approach

From Princeton Municipal Airport (PNM) to Princeton Municipal Airport (PNM)

Report a problem

Event

NTSB case
CEN12LA077
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 152

Aircraft type
Cessna 152
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
N6436P
Onboard fatalities
Unknown
Route
From Princeton Municipal Airport (PNM), Princeton, MNTo Princeton Municipal Airport (PNM), Princeton, MN
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
Approach · VFR pattern base
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)
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
  • Personnel issues › Task performance

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

NTSB narrative

The student pilot conducted two takeoffs and landings without incident. During initial climb after the third takeoff, he heard a loud “pop,” and the airplane started to vibrate severely and lose engine power. He executed a forced landing to a nearby field. The airplane landed hard and nosed over during the landing roll. The examination of the airplane revealed that the lower spark plug from the No. 2 cylinder and its associated threaded insert were missing. The threads in the top portion of the spark plug hole were stripped, and only the bottom three threads remained. No other engine anomalies were observed. The engine maintenance logbook indicated that, 7 days prior to the accident, the Nos. 1 and 2 cylinders had new threaded inserts installed in the lower spark plug holes.

Probable cause

The inadequate installation of the threaded insert in the No. 2 cylinder spark plug hole by maintenance personnel, which resulted in a loss of engine power during initial climb.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN12LA077
Event ID
20111122X85008
Case number
CEN12LA077
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: bc2ca749175fbf2c941e126861adaa389df941861243b0d7924badeec1bd8b09; retrieved 2026-09-15T16:57:30.539Z.