# NTSB ERA25LA052: Cessna 172S, N951JA, Chattanooga, TN, November 19, 2024

- Type: NTSB accident investigation
- Classification: Accident · Minor injuries · Class 3 · Limited · Final report
- Date: November 19, 2024, 18:51 local (23:51 UTC)
- Place: Chattanooga, TN
- Coordinates: 35.050623, -85.212524 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=35.0506&lon=-85.2125&mi=10
- Phase of flight: [Initial climb](https://openairdocs.org/ntsb-phases/350) (OpenAirDocs' grouping)
- Defining event: [Initial climb: Loss of engine power (partial)](https://openairdocs.org/ntsb-events/342)
- Highest injury: Minor injuries
- Injuries: 1 minor, 1 uninjured
- Status: Completed, report August 19, 2026
- Report: Approved by Office Director
- Investigation class: Class 3
- NTSB office: Eastern Region Aviation
- Parties: FAA/FSDO, Hartzell Engine Tech
- NTSB case key (mKey): 195525
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA25LA052
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/195525/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=195525
- Page: https://openairdocs.org/ntsb/ERA25LA052

## 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.

## Findings

NTSB's coded findings; those marked are part of the probable cause.

- [Performance/control parameters: angle of attack](https://openairdocs.org/ntsb-findings/01062042): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cessna 172S, 13 cases](https://openairdocs.org/ntsb-findings/01062042/cases.md?model=2072439), [All aircraft, 990 cases](https://openairdocs.org/ntsb-findings/01062042/cases.md)
- [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Instructor/check pilot (probable cause); cases with it: [Cessna 172S, 206 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2072439), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md)
- [Ignition system: spark plugs/igniters](https://openairdocs.org/ntsb-findings/01057421): Aircraft › Aircraft power plant · Damaged/degraded (probable cause); cases with it: [Cessna 172S, 1 case](https://openairdocs.org/ntsb-findings/01057421/cases.md?model=2072439), [All aircraft, 38 cases](https://openairdocs.org/ntsb-findings/01057421/cases.md)

## Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event best describes what happened.

- [Initial climb: Loss of engine power (partial)](https://openairdocs.org/ntsb-events/342) (defining event); cases with it: [Cessna 172S, 10 cases](https://openairdocs.org/ntsb-events/342/sequence.md?model=2072439), [All aircraft, 1,858 cases](https://openairdocs.org/ntsb-events/342/sequence.md)
- [Approach-VFR go-around: Loss of control in flight](https://openairdocs.org/ntsb-events/240); cases with it: [Cessna 172S, 49 cases](https://openairdocs.org/ntsb-events/240/sequence.md?model=2072439), [All aircraft, 5,002 cases](https://openairdocs.org/ntsb-events/240/sequence.md)
- [Approach-VFR go-around: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Cessna 172S, 118 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=2072439), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md)

## Analysis

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 didnot 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.

## Factual narrative

On November 19, 2024, at 1851 eastern standard time, a Cessna 172S, N951JA, sustained substantial damage when it was involved in an accident near Chattanooga, Tennessee. The flight instructor was not injured and the private pilot sustained minor injuries. The flight was conducted as a Title 14 Code of Federal Regulations Part 91 instructional flight. The private pilot was receiving instruction in preparation for his instrument rating practical test. He conducted a preflight inspection and engine run-up, including a check of each magneto, prior to departure and no anomalies were noted. The private pilot said that shortly after takeoff from runway 20 at Lovell Field Airport (CHA), Chattanooga, Tennessee, the engine’s rpm dropped to 2,300 rpm. He declared an emergency with air traffic control (ATC) and advised they were in instrument meteorological conditions (IMC) and needed to return to land. The air traffic controller provided the pilot with radar vectors to land on runway 2, but once he and the flight instructor visually acquired the runway, the airplane was too fast, so they executed a go-around to avoid trees. The private pilot said that as the airplane climbed above the trees, the engine lost total power, and their only option was an off-airport landing to a road. During the landing, the airplane struck trees and came to rest on the side of the road resulting in substantial damage to both wings and the fuselage. There was no postimpact fire. The flight instructor said that when the private pilot declared an emergency the engine instruments were in the “green” and engine rpm was about 2200 to 2300 rpm. Air traffic control began to vector them to runway 33, but they took a wrong turn, and they were then vectored to runway 2; however, they were in IMC which made it hard to see the runway. The instructor said that when they turned on final approach to the runway, they could not see the runway environment until they were halfway down the runway. At that time, the airplane was flying too fast. She took control of the airplane, and added full power to go-around since the engine still “had some power left.” The instructor initiated a climb, but the airplane’s airspeed began to drop as she tried to turn back toward the runway. The instructor said, “this is when the engine quit” and the airplane’s airspeed dropped to 40 knots. The airplane descended nose down into trees and impacted the ground. The airplane was equipped with a Garmin G-1000 primary and multi-function flight displays, which recorded flight and engine performance data. The data revealed the airplane departed runway 20 at 1840:10, at a power setting of 2,500 rpm (maximum engine rpm for this airplane was 2,700 rpm). The cylinder head temperature (CHT) of the No. 4 cylinder began to rapidly increase after takeoff. Around 1841, engine rpm fluctuated between 2,200 to 2,300 rpm as the airplane was being vectored to runway 33. At 1849:20, as the airplane was attempting to land, engine powerdecreased to about 963 rpm. At 1850:00, engine rpm suddenly increased to about 2,135 rpm, the airplane began to climb, and it turned to the northwest. Over the next 46 seconds, engine rpm remained between 2,000 at 2,150 rpm; however, the airplane’s pitch attitude increased and the indicated air speed dropped to about 40 knots before the data ended at 1850:56. Postaccident examination of the engine revealed no evidence of catastrophic failure. The propeller was manually rotated, and compression/valve train continuity were established on each cylinder. Continuity was also established to the accessory section. Both magnetos were properly timed in accordance with the engine data plate. After removal of both magnetos, it was determined the right magneto impulse coupling was binding at the latching end of the pawls and stop-pin where normal force should have released the latching end of the pawl. Additionally, the nut on the magneto rotor shaft was only finger tight with the cotter pin installed. The magneto, which had been recently overhauled, was installed on the engine the same day of the accident flight. According to the installation manual, the nut on the magneto rotor shaft should have been torqued to 120-320 in/lbs. The magneto was retained and shipped to the manufacturer for testing. The body of the impulse coupling was removed, and the spring was found to be distorted. The spring was not engaged with the slot of the hub; however, it was still able to rotate normally. An exemplar spring and hub were mounted on the magneto and attached to the test bench. The magneto was tested up to 2,700 rpm with normal spark between all gaps. No anomalies were noted. The magneto was removed from the test bench and re-fitted with the accident spring and hub. There was no audible impulse action when turned by hand. The magneto was attached to the test bench and was tested up to 2,700 rpm with normal spark and no anomalies noted. The reason for the spring distortion could not be determined, and the binding of the impulse coupling could not be duplicated. Internal timing of the magneto was checked and found within specifications. The spark plugs were removed and displayed various levels of wear. A small piece of metal was found wedged between the center electrode and prongs on the No. 4 cylinder’s bottom plug. The spark plugs were examined at the NTSB Materials Laboratory, and the metal particle wedge in the No. 4 bottom plug was determined to consist primarily of lead. Resistance measurements were also taken on each of the spark plugs to see if there was a short circuit between the two electrodes. The center electrode resistance measurements were all nominally around 1 kohm. This resistance was within the manufacturer’s acceptable resistance range. The center electrode to ground electrode resistance measurements were all above 11 Gohm (the meter’s maximum reading) indicating that there was no electrical path between the electrodes. Only the bottom spark plug forcylinder No. 4 had a lower resistance of approximately 100 Mohm indicating that there was an electrical path between the two electrodes. A review of the engine maintenance log revealed that the spark plugs were last “removed, inspected/cleaned, and re-installed” on October 17, 2024, at the airplane’s last 100-hr inspection, about 87 hrs. prior to the accident. The fuel manifold, respective fuel injector lines, and fuel injector nozzles were removed and found absent of any debris. The fuel injector servo remained installed and undamaged to the bottom of the engine. The fuel injector servo was sent to the manufacturer for testing. The fuel injector servo was flow tested, and the results were within service limits. The unit was disassembled and no mechanical anomalies were observed that would have precluded normal operation. All four of the engine cylinders were removed and displayed a lack of combustion residue within their respective combustion chambers. The tops of all four pistons lacked combustion residue. During the removal of the No. 4 cylinder, the piston pin plug was difficult to remove and heat discoloration was evident on the small end of the connecting rod, piston pin, and piston pin plugs. Similar discoloration of the piston pin and small end of the connecting rod of the No. 2 cylinder was observed. The piston for the No. 4 cylinder displayed signatures of metal erosion and the oil control ring was partially seized. The engine oil filter contained minor non-metallic metal debris. The oil suction screen was absent of debris. According to the airplane’s Before Takeoff Checklist, a functional test of the ignition system is to be performed by switching between the individual magnetos from the “both” position on the ignition switch. The checklist stated to bring the throttle to 1,800 rpm and check each magneto position for a maximum drop of 150 rpm, and a maximum difference of 50 rpm between the left and right magneto. Both pilots said that they tested the magnetos prior to takeoff and both were within limitations. A review of the engine operation manual stated that to conduct a proper check of the magnetos, the pilot should increase engine power to 1,800 rpm, and “Switch from both magnetos to one and note the drop off; return to both until engine regains speed and switch to the other magneto and note the drop off, then return to both. Drop-off must not exceed 175 rpm and must not exceed 50 rpm between magnetos.” Review of the G-1000 engine data revealed that engine power was increased prior to takeoff to about 1,800 rpm; however, the data was unclear if the private pilot or instructor allowed the engine rpm to stabilize during the magneto check to get an accurate measurement.

## Aircraft

- Registration: [N951JA](https://openairdocs.org/aircraft/N951JA), registered now, S/N 172S10496, built 2007 (OpenAirDocs)
- Reported make and model: CESSNA 172S
- Registry model: [Cessna 172S](https://openairdocs.org/model/cessna-172s) (registry code 2072439) (OpenAirDocs)
- Registry engine: [Lycoming IO-360-L2A](https://openairdocs.org/engine/lycoming-io-360-l2a) (registry code 41597, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 172S10496
- Year built: 2007
- Airframe hours: 14523
- Engines: LYCOMING IO-360-L2A 180 horsepower reciprocating
- Damage: Substantial damage
- Flight: Instructional, Part 91
- Airworthiness certificate: Standard, Normal
- Last inspection: 100 hour, October 17, 2024, 87 hours before
- Destination: Same as departure
- Flight plan: IFR
- Airport: CHA, Lovell Fld
- Equipment: Stall warning system, ADS-B, Electronic multifunction display, Electronic primary flight display

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 51; injuries: minor; private; airplane ratings: single-engine land; medical: class 3, without waivers/limitations; last flight review January 23, 2023; seat: left; restraint: 3-point; flight hours: 287.8 total, 279.6 in this make and model, 203.8 as pilot in command, 27.5 in the last 90 days, 5.7 in the last 30 days, 0 in the last 24 hours
- Flight instructor; age 27; injuries: none; private, commercial, flight instructor; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 1, without waivers/limitations; last flight review April 18, 2024; seat: right; restraint: 3-point; flight hours: 811.4 total, 421.4 in this make and model, 710.5 as pilot in command, 201.9 in the last 90 days, 59 in the last 30 days, 3 in the last 24 hours

## Weather

- Conditions: Instrument (IMC), Day
- Wind: 110° at 3 knots
- Visibility: 1.25 statute miles
- Lowest ceiling: 1,400 ft overcast
- Temperature: 64 °F, dew point 63 °F
- Altimeter: 29.82 inHg
- Observed at: KCHA, 1 nm away
- METAR: KCHA 192318Z 11003KT 1 1/4SM -RA BR SCT006 SCT010 OVC014 18/17 A2982 RMK AO2 P0002 T01780167

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 20241119018649A](https://openairdocs.org/incident/20241119018649A), Nov 19, 2024: Cessna 172S, Chattanooga, TN, Substantial damage. Shortly after departure the pilot contacted departure and reported a rough running engine and requested return for landing. When pilot tried to land they…

## Docket (20 files)

The files NTSB released with the investigation on August 19, 2026, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=195525. 25.9 MB in all.

- Pilot/operator aircraft accident report, NTSB form 6120.1 (item 1, PDF, 9 pages, 10.5 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20616427&FileExtension=pdf&FileName=6120_Redacted-Rel.pdf
- Written statement - CFI (item 2, PDF, 2 pages, 199 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20616297&FileExtension=pdf&FileName=Written%20Statement%20-%20CFI_Redacted-Rel.pdf
- Written statement - pilot receiving instruction (item 3, PDF, 3 pages, 2.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20650808&FileExtension=pdf&FileName=Written%20Statement%20-%20Pilot%20Receiving%20Instruction_Redacted-Rel.pdf
- Investigation photos (item 4, PDF, 3 pages, 2 photos, 1.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20698449&FileExtension=pdf&FileName=Investigation%20Photos-Rel.pdf
- Radar plot - accident flight (item 5, PDF, 1 page, 2.6 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20616975&FileExtension=pdf&FileName=ERA25LA052%20Flight%20Plot-Rel.pdf
- FAA air traffic control factual report - excerpt (item 6, PDF, 1 page, 57 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20616023&FileExtension=pdf&FileName=Excerpt%20-%20FAA%20ATC%20Package-Rel.pdf
- FAA - initial engine exam report (item 7, PDF, 2 pages, 226 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20615594&FileExtension=pdf&FileName=Engine%20Inspection%20Report%20-%20FAA_Redacted-Rel.pdf
- NTSB - engine examination report (item 8, PDF, 8 pages, 1.8 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20616149&FileExtension=pdf&FileName=NTSB%20Engine%20Examination%20Report_Redacted-Rel.pdf
- Engine maintenance records - excerpts (item 9, PDF, 3 pages, 2 photos, 293 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20649723&FileExtension=pdf&FileName=Engine%20MX%20Records_Redacted-Rel.pdf
- NTSB materials lab report (item 10, PDF, 9 pages, 1.7 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20617829&FileExtension=pdf&FileName=Materials%20Laboratory%20Factual%20Report%2025-045_Redacted-Rel.pdf
- Cockpit display - recorded flight data - specialist's factual report (item 11, PDF, 10 pages, 2.7 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19064107&FileExtension=pdf&FileName=ERA25LA052%20Cockpit%20Display%20-%20Recorded%20Flight%20Data%20-%20Specialist%27s%20Factual%20Report-Rel.pdf
- Attachment 1 to cockpit display - recorded flight data - specialist's factual report (item 12, CSV, 324 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19059134&FileExtension=csv&FileName=ERA25LA052%20Attachment%201%20to%20Cockpit%20Display%20-%20Recorded%20Flight%20Data%20-%20Specialist%27s%20Factual%20Report-Rel.csv
- NTSB mor- RH magneto examination (item 13, PDF, 1 page, 83 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20616159&FileExtension=pdf&FileName=NTSB%20MOR%20-%20Magneto%20Exam_Redacted-Rel.pdf
- Hartzell - RH magneto summary of examination report (item 14, PDF, 3 pages, 61 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20617002&FileExtension=pdf&FileName=Hartzell%20Aviation%20-%20Summary%20of%20Right%20Magneto%20Exam_Redacted-Rel.pdf
- NTSB mor - fuel servo examination report (item 15, PDF, 2 pages, 1.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20616687&FileExtension=pdf&FileName=NTSB%20MOR%20-%20Fuel%20Control_Redacted-Rel.pdf
- Excerpt from Lycoming O-360 operator's manual (item 16, PDF, 1 page, 107 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20619277&FileExtension=pdf&FileName=Excerpt%20from%20Lycoming%200-360%20Operator%27s%20Manual-Rel.pdf
- Excerpt from Cessna 172S POH (item 17, PDF, 1 page, 113 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20619153&FileExtension=pdf&FileName=Excerpt%20from%20Cessna%20172S%20POH-Rel.pdf
- Statement of party representatives to NTSB investigation (item 18, PDF, 11 pages, 535 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20616764&FileExtension=pdf&FileName=ERA25LA052%20QAA%20Party%20Form_Redacted-Rel.pdf
- Release of aircraft wreckage, NTSB form 6120.15 (item 19, PDF, 1 page, 125 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20622471&FileExtension=pdf&FileName=Signed%20NTSB%20Wreckage%20Retention%20-%20Release%20Form_Redacted-Rel.pdf
- NTSB evidence control forms (item 20, PDF, 4 pages, 348 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20616317&FileExtension=pdf&FileName=NTSB%20Evidence%20Control%20Forms_Redacted-Rel.pdf

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.