FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA23FA254 · Zenith 601XL

3 Jun 2023 · Albertville, AL, United States

Zenith 601XL · Accident while maneuvering

Report a problem

Event

NTSB case
ERA23FA254
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
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
Visual Meteorological Cond

Zenith 601XL

Aircraft type
Zenith 601
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
N601YP
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo not recorded
Aircraft age
Built the same year (2023)
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
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
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

  • 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 troubleshooting oil pressure and airspeed indications issues with his electronic flight instrumentation and engine monitoring system, the pilot departed in the experimental amateur-built airplane on its third test flight. Data recovered from the airplane’s onboard electronic instruments showed that the airplane departed the airport traffic pattern and flew for about 30 minutes, performing several heading changes and climbing to 4,000 ft mean sea level (msl) before descending to level off at 2,050 ft msl. There was nothing unusual about the airplane’s flight profile and the maneuvers up to that point appeared to be normal. Witnesses to the final moments of the flight reported the airplane was flying slow at a low power setting. One witness reported the airplane stalled or pitched up and down, then stalled again before it rolled to the left and right and then descended behind the trees. Another witness reported the engine power increased to full power before the nose of the airplane pitched down. The pilot did not recover from the descent and the airplane impacted trees and terrain about 3 miles away from the airport.

The recorded data for the final moments of the flight revealed a sequence of events that was generally consistent with the witness observations, and there were no apparent anomalies with the airplane’s engine preceding or during the final descent. Postaccident examination of the airframe, systems, and engine did not reveal evidence of any preimpact mechanical malfunctions or failures that would have precluded normal operation. Discrepancies observed in the recorded data, such as recorded changes to the roll angle and a relative lack of change of the airplane’s heading and ground track, as well as differences between the airplane’s indicated/true airspeeds and the recorded GPS groundspeeds suggested that the troubleshooting efforts the pilot was performing to the airplane’s electronic instruments may not have resulted in the system being fully functional and able to record reliable parametric data.

Medical examination revealed the pilot was at increased risk of cardiovascular disease. No significant cardiovascular disease was identified during the pilot’s autopsy; however, the autopsy was limited by injuries that prevented examination of the pilot’s coronary arteries. Toxicology testing of specimens from the pilot was consistent with medication-treated diabetes, without severe high blood sugar at the time of the accident. While this condition was associated with some increased risk of impairment or incapacitation, there was no specific forensic evidence that a medical event contributed to the accident.

Based on the available evidence, the reason for the airplane’s descent and impact with terrain could not be determined.

Probable cause

A descent and impact with terrain for reasons that could not be determined.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA23FA254
Event ID
20230604192298
Case number
ERA23FA254
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: 6e19778362637b5595347f79ee6d9537c7674910559f8fec71bc1cfc06a060ca; retrieved 2026-09-15T08:00:52.457Z.