FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN23FA144 · Zenith STOL CH701

29 Mar 2023 · Oxford, MS, United States

Zenith STOL CH701 · Accident while maneuvering

From New Albany Union County Airport (M72) to New Albany Union County Airport (M72)

Report a problem

Event

NTSB case
CEN23FA144
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

Zenith STOL CH701

Aircraft type
Zenith STOL CH701
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
N43414
Operator
Unknown
Onboard fatalities
Unknown
Route
From New Albany Union County Airport (M72), New Albany, MSTo New Albany Union County Airport (M72), New Albany, MS
Aircraft age
About 18 years (built 2005)
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
Maneuvering · low-altitude flying
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
Unknown or undetermined
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Tree(s)
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

  • Not determined › Not determined

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

NTSB narrative

After takeoff, the pilot proceeded south and then southwest. About 16 miles from the airport, the pilot reversed course and proceeded toward the north and then the northeast, in the general direction of the departure airport. The airplane subsequently entered a right turn toward the south; however, the position data ended about 11 seconds later. The airplane subsequently impacted trees and terrain about one-third mile south of the final data point. A review of the available flight track data, as well as the wreckage disposition, did not reveal any evidence of an in-flight loss of control. An on-scene airframe examination did not reveal any evidence of an in-flight structural failure or preimpact flight control anomaly. A postrecovery engine examination did not reveal any anomalies consistent with an inability to produce rated power. However, testing of the ignition modules revealed that they both misfired when operating in a narrow range about 4,000 rpm. While the observed anomaly could have resulted in rough engine operation at that specific engine speed, it likely would not have resulted in a loss of engine power. An autopsy revealed the pilot had severe narrowing of a single coronary artery. His coronary artery disease conveyed increased risk of a sudden impairing or incapacitating cardiac event such as unstable arrhythmia or heart attack. There was no autopsy evidence that such an event occurred, but such an event leaves no reliable autopsy evidence if it occurs immediately before death. The limited available information about the circumstances of the crash adds little clarity about the likelihood of a medical event. Thus, whether the pilot’s coronary artery disease contributed to the accident cannot be determined. Toxicology testing revealed that ethanol was detected at a low level in cavity blood, a specimen type in which n-propanol was also detected. Ethanol was not detected in vitreous fluid, which is generally the specimen type best protected against postmortem ethanol formation. These results indicate that some or all the small amount of detected ethanol may have been from postmortem production, and that ethanol effects did not likely contribute to the accident. In light of the lack of any significant anomalies with respect to the airplane examinations, and an inability to attribute the event to the pilot’s coronary artery disease and an in-flight medical event, the investigation was unable to determine the specific reason for the impact with the trees and terrain.

Probable cause

An in-flight collision with trees and terrain for undetermined reasons.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN23FA144
Event ID
20230331106982
Case number
CEN23FA144
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: 8c7a33276d0ea41551f7fa0c6dccce432df680d2408aa8226d415f422cd3d5a2; retrieved 2026-09-15T07:58:13.703Z.