ERA25LA052 · Cessna 172S
Cessna 172S · Accident: loss of engine power (partial) during initial climb
Event
- NTSB case
- ERA25LA052
- 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
- Instrument Meteorological Cond
Cessna 172S
- 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
- N951JA
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 17 years (built 2007)
- 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
- Initial climb
- 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 oper/perf/capability
- Aircraft › Aircraft power plant
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot was receiving instruction from the flight instructor in preparation for the pilot’s instrument practical test. Shortly after departing on the flight, and while in instrument meteorological conditions (IMC), the pilot noted that the engine’s rpm decreased to 2,300, so he declared an emergency and requested to return to the departure airport. The air traffic controller provided the pilot with radar vectors to land, but once he and the flight instructor visually acquired the runway, the airplane was near its mid-point and the airplane was flying too fast to land. Because the engine was still producing power, the flight instructor took control of the airplane and performed a go-around. After the flight instructor initiated a climb the airplane’s airspeed began to decrease as she tried to turn back toward the runway. During this maneuvering, the pilot and flight instructor stated that the engine lost power completely and the airplane’s airspeed decreased to 40 knots. The airplane then descended nose down into trees and impacted the ground. Review of data recorded by the airplane’s primary and multifunction flight displays revealed that although the pilots perceived a progressive loss of engine power after takeoff, the airplane’s engine continued to produce power throughout most of the flight and during the attempted go-around. Specifically, the recorded data showed that the engine rpm remained generally between 2,200 and 2,300 rpm (the maximum rpm for this engine was 2,700) following the initial reported power loss, and that the engine power had increased to about 2,135 rpm during the go-around attempt. Oil pressure, fuel flow, and other engine parameters were generally consistent with the recorded engine power output. Postaccident examination of the engine revealed several discrepancies, including anomalies associated with the recently overhauled right magneto, a lead-fouled No. 4 spark plug, (a small piece of metal was found wedged between the center electrode and prongs), and evidence of heat distress and wear in the No. 4 cylinder. Follow-on testing of the magneto and fuel servo did not reveal any evidence of any conditions that would have prevented normal engine operation, and there was no evidence of a catastrophic engine failure. These findings, along with the recorded data, suggest that while engine performance was degraded, there was not a complete loss of engine power as reported by both pilots. The flight data also showed that following the go-around, the airplane entered a climbing left turn while the airspeed steadily decreased. Over the final seconds of recorded data, the engine rpm remained near 2,150 rpm while the airplane's pitch attitude increased and the airspeed decayed to approximately 40 knots. Based on the available evidence, the partial loss of engine power initially observed by the pilots was the result of the lead fouled spark plug. The pilot subsequently conducted a precautionary landing approach in IMC that did not place the airplane in a position where it could land safely. The reduction in engine performance due to the fouled spark plug most likely increased the challenge of executing the subsequent go-around, but the recorded data indicated that a loss of control and subsequent aerodynamic stall resulted primarily from the decaying airspeed and increasing pitch attitude rather than a total loss of engine power.
Probable cause
A partial loss of engine power due to a fouled spark plug in engine’s the No. 4 cylinder. Contributing was the flight instructor’s failure to maintain aircraft control during an attempted go-around following an unsuccessful landing approach in IMC, which resulted in an aerodynamic stall and impact with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA25LA052
- Event ID
- 20241120195525
- Case number
- ERA25LA052
- 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, coordinates, cause areas. 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: 516a301e800cd365f7d45b7139fb8b13f5a495134345db89f27437773d68838d; retrieved 2026-09-16T19:29:23.008Z.