NTSB CAROL · Event
Event ERA23LA351
Registry · N114DZ
FAA Aircraft Registry record.
Make / Model
NANCHANG CHINA CJ-6A
Year of manufacture
1967 · 56 years old at event
Engine
AMA/EXPR UNKNOWN ENG
Seats / Engines
2 seats · 1 engine
Last airworthiness date
19980527
ADS-B equipped
Yes — Mode-S A03B72
Registrant of record
GALUPPO RONALD RICHARD JR
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
A total loss of engine power while enroute for reasons that could not be determined.
Factual narrative
On August 26, 2023, at 1738 eastern daylight time, a Nanchang CJ-6A, N114DZ, was substantially damaged when it was involved in an accident near Merrickville, New York. The airline transport pilot and pilot-rated passenger sustained serious injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The airplane departed Dewitt Field/Old Town Municipal Airport (OLD), Old Town, Maine, at 1518 with a destination of State College Regional Airport (UNV), State College, Pennsylvania, which was about 473 miles southwest. While enroute, the pilot realized that due to weather and air traffic control (ATC) deviations, he would not have the required fuel reserves to continue the flight to UNV. He decided to divert to Greater Binghamton Airport/Edwin A Link Field (BGM), Binghamton, New York, which was 117 nautical miles northeast of UNV. Subsequently, about 40 nautical miles from BGM, the engine sustained a total loss of power. The pilot reported completing the engine failure in flight emergency procedure. He reported that the airplane had about 1 hour of fuel remaining on board at the time of the loss of power. He switched the magneto from right to left multiple times and both were only effective for a few seconds each before the engine lost power again. The pilot-rated passenger reported that, while the pilot began to address the engine failure, he called ATC and declared an emergency. ATC gave the pilot a radar vector to the closest airport, but the pilot determined that they would not be able to glide that distance and began to look for a place to make a forced landing. With no suitable fields in the vicinity, the pilot reported that, “I felt the safest course of action was to ditch into trees.” The airplane impacted multiple trees and came to rest on its right side. The impact resulted in substantial damage to both wings, the fuselage, and left horizontal stabilizer. A witness who lived near the accident site was outside her home when she saw a “small green airplane descending.” She stated that, “There was no sound whatsoever coming from the plane, he quickly lost altitude and descended into the tree line.” She also reported that, about 200 yards from the accident site, there was a “slight smell of fuel,” which she followed to find the site. A video was recorded by another witness near the accident site that recorded the sound of the airplane’s engine cutting in and out before ultimately going silent. Postaccident examination of the wreckage found that the flight control stick moved freely by hand with no binding. The throttle control was full open, the mixture control was 3/4 toward the full rich position, the carburetor heat was on, and the fuel selector was on. There were no residual fuel vapors in either of the wing fuel tanks; however, the smell of fuel was present at the site. The front spark plugs were removed and about 2 quarts of fuel ran out of the spark plug hole of one cylinder. Compression and suction were confirmed on all cylinders when the crankshaft was rotated by hand using the propeller. Valvetrain continuity was confirmed on all but one cylinder, which exhibited impact damage to the push rods, when the crankshaft was rotated by hand using the propeller. Both magnetos were removed and produced spark on all leads when rotated using an electric drill. The fuel screen was removed and exhibited no debris; there was slight corrosion inside the fuel screen housing. The oil filter was removed and cut open; the filter pleats contained a small number of metallic fragments. The cylinders were not labeled and were marked arbitrarily; there was a hole on the No. 1 cylinder intake tube with a piece missing; this piece was not found during the examination. Review of maintenance records indicated that the airplane’s fuel capacity was increased in 2014 to 64 gallons total, with 2 gallons of unusable fuel. The pilot reported that they had departed on the flight with 62 gallons of 100 low-lead (100LL) aviation fuel on board. Fuel records showed that the pilot purchased 28.9 gallons of 100LL two days before the accident flight. The pilot reported that he used a fuel consumption rate of 16 gallons per hour while flight planning and that he did not operate the airplane for more than 3 hours. This would result in the airplane having an endurance of about 3.8 hours; the accident occurred about 2.6 hours into the flight. The pilot reported that, during a cross-country flight, he chose to divert to a closer airport due to weather and air traffic control delays. About 40 nautical miles from the diversion airport, the engine lost total power. The pilot attempted to restart the engine, but was unsuccessful in restoring power and chose to conduct a forced landing into trees. The airplane impacted the trees and sustained substantial damage to both wings, the fuselage, and the left horizontal stabilizer. A video recorded by a witness near the accident site captured the sound of the engine cutting in and out before ultimately going silent, which was consistent with an additional witness report. Based upon fueling records and the pilot’s report of his fuel planning and the airplane’s fuel consumption rate, the airplane should have had about one hour of fuel remaining at the time of the loss of power. Due to the airplane damage, the total fuel quantity on board could not be established; however, the smell of fuel was present at the accident site. Examination of the engine found that a small piece of the intake duct work of a cylinder was missing. While having this piece missing could have resulted in under-performance of the engine or a partial loss of power, it is unlikely this would have resulted in a total loss of engine power. There were no other preaccident mechanical malfunctions or failures found with the airplane that would have precluded normal operation and the reason for the loss of power could not be determined. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).
- — Aircraft-Aircraft power plant-Engine (reciprocating)-(general)-Unknown/Not determined
Verbatim from NTSB's published report. Source file
NTSB_2023_ERA23LA351.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (engine failure, maintenance). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- Embry-Riddle Scholarly Commons 2026 · Journal article (IJAAA)
From Reactive to Predictive: A hybrid Trust-Mediated Adoption Framework for Data-Driven Maintenance in Distributed-Authority Aviation Environments
Modern aviation maintenance operates within increasingly data-intensive technological environments, yet the operational integration of predictive maintenance into routine decision-making remains incon…
- Semantic Scholar 2025 · Article (Applied Sciences)
Decision-Making Framework for Aviation Safety in Predictive Maintenance Strategies
The implementation of predictive maintenance (PM) in aviation presents unique challenges due to strict safety requirements, complex operational environments, and regulatory constraints.
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
Low-Resource Automatic Speech Recognition Domain Adaptation – A Case-Study in Aviation Maintenance
With timeliness and efficiency being critical in the aviation maintenance industry, the need has been growing for smart technological solutions that optimize and streamline the different underlying ta…
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
A New Trajectory in UAV Safety: Leveraging Reinforcement Learning for Distance Maintenance Under Wind Variations
In the field of aviation, safety is a critical cornerstone, and the operation of Unmanned Aerial Vehicle (UAV) systems is deeply connected with this principle.
- Embry-Riddle Scholarly Commons 2024 · Journal article (IJAAA)
Just Culture in Aviation: A Metaphorical Study on Aircraft Maintenance Students
Just Culture, a sub-dimension of safety culture, has been a prominent and debated topic in aviation safety in recent years.
- Embry-Riddle Scholarly Commons 2024 · Journal article (IJAAA)
Performance PRISM: A Comprehensive Framework For Performance Measurement In Aircraft Maintenance
Aircraft maintenance is governed by rigorous safety requirements and high operational complexity, demanding robust performance measurement frameworks to ensure optimal maintenance practices.
Browse the full corpus — academia portal ↗