FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA21FA334 · North American SNJ-2

20 Aug 2021 · Wilkes-Barre, PA, United States

North American SNJ-2 · Accident: loss of engine power (total) during initial climb

Report a problem

Event

NTSB case
ERA21FA334
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
1 · 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

North American SNJ-2

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
N52900
Operator
SNJ-2
Onboard fatalities
Unknown
Route
From not recordedTo not recorded
Aircraft age
About 78 years (built 1943)
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 (total)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

No findings designated as a cause are recorded in the NTSB data yet.

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The accident airplane was one in a flight of six other airplanes departing on a practice flight in preparation for an airshow routine. The accident pilot’s wingman stated that they had just taken off, and that the accident pilot did not look over at him to check that his landing gear was up as he normally did. The wingman noted that the accident airplane’s landing gear was retracting, that the airplane began decelerating, and that he heard the accident pilot transmit over the radio that he had an emergency. The accident airplane turned to the left, and as its angle of bank increased past about 20°, the airplane slowed further, the bank continued to increase, and the airplane began descending. The airplane’s smoke system then came on, the airplane impacted the ground, and a post-impact fire ensued. A video provided by a witness on the ground captured popping noises similar to back-firing of the engine before the airplane turned left and pitched down to ground contact. No black smoke was observed emanating from the airplane before the accident. Postaccident examination of the airplane revealed that it was severely fire damaged. No evidence of any preimpact failures or malfunctions of the airframe or engine that would have precluded normal operation were identified. Examination of the propeller revealed signatures consistent with low power at the time of impact. Given this physical evidence, the pilot’s report of an inflight emergency, and the witness video that depicted abnormal engine sounds, it is likely that the engine at least partially lost power during the initial climb, which precipitated the pilot’s break out from the formation. On the day before the accident, the accident pilot arrived at the airport late due to weather. He reported that the engine was “banging” while operating on the left magneto during a magneto check. Troubleshooting by the director of maintenance (DOM) revealed that the engine was “popping and banging” while operating on the left magneto, and during the idle-power P-lead check for proper grounding of the magnetos, when the magneto switch was passed through the left magneto position on the way to the off position, the engine seemed to be shutting down as if the magneto switch had been placed in the off position. The DOM discovered that the left magneto P-lead spring at the end of the P-lead insulator was fully compressed, allowing the internal grounding spring to contact the magneto case. Inspection of the right magneto revealed that its P-lead spring was extended normally. The DOM replaced the left magneto P-lead spring and performed an engine run-up, magneto check, and P-lead check, which revealed no anomalies. Additionally, the pilot did not report any anomalies during the engine run-up before takeoff on the accident flight. Postaccident examination revealed that the left magneto could not be fully rotated due to impact damage. Its points looked serviceable, and the coil, when tested, was within operating limits. The condenser was damaged but tested serviceable. The right magneto would rotate easily, consistent with poor magnetism, would not perform at low rpm, and would not fire on all points until it reached 180 rpm. Review of maintenance records did not reveal any entries related to the installation of the right magneto on the engine; therefore, its service history could not be determined. According to the engine manufacturer’s troubleshooting guidance, there were 11 ignition system-related items that could cause the engine to run rough, and listed the corrective action to be taken as “apply continuity test.” Under the section on “Engine Stops,” it listed “short in the system” as a possible cause, in addition to the master switch or magneto switch being inadvertently cut off. The manual stated, “Check all wiring for security, breaks or chafing” and “Check all systems components.” Based on the lack of anomalies found during the postaccident engine examination, it is possible that the loss of engine power occurred due to an additional undiagnosed fault with the ignition system, which could have been compounded by the poor-performing right magneto; however, the extent of the post-impact fire damage precluded a thorough examination of the ignition system wiring and components. While breaking out from the formation, the accident pilot entered a steep left turn, which may have been an attempt to land on the crosswind runway, but also would have significantly increased the airplane’s stall speed due to the increased load factor imposed by the turn. The pilot’s exceedance of the airplane’s critical angle of attack during this turn resulted in an aerodynamic stall and the loss of control.

Probable cause

A partial loss of engine power for undetermined reasons. Also causal was the pilot’s exceedance of the airplane’s critical angle of attack while maneuvering for a forced landing following the loss of engine power, which resulted in an aerodynamic stall and loss of control.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA21FA334
Event ID
20210820103732
Case number
ERA21FA334
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. 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: 9333d8970212ae1631851a6c3158a5bf73b1519c8e3fb357c9aa6979684c322f; retrieved 2026-09-15T07:33:22.157Z.