FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA24LA256 · Zenith 701

8 Jun 2024 · Ocala, FL, United States

Zenith 701 · Accident: loss of control in flight on approach

Report a problem

Event

NTSB case
ERA24LA256
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
0 · 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 701

Aircraft type
Zenith 701
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
N643E
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo not recorded
Aircraft age
About 7 years (built 2017)
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
Approach · VFR go-around
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 control in flight
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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot was flying the experimental amateur-built airplane in the airport traffic pattern. After completing two low approaches to the runway, the pilot was approaching the runway for a third time and had been cleared by the air traffic controller to land. The pilot reported that while on short final approach, he encountered a large number of birds and elected to perform a go-around to the left of the runway; however, the airplane did not climb as the pilot expected and collided with trees short of the runway. The air traffic controller described that while the accident airplane was on final approach, at an altitude about 20 ft above the runway, it abruptly turned 45° left and appeared “out of control.” The airplane subsequently began to climb before it turned hard left and descended in a nose down attitude into the trees.

The pilot had accrued 490 total hours of flight experience, of which 1 hour was in the accident airplane make and model. The owner of the airplane stated that the pilot was attempting to build flight experience to meet the requirements of an airline transport pilot certificate. The owner agreed to let him fly the airplane, but required the pilot to fly with a flight instructor due to his lack of experience in the airplane make and model. The pilot did not follow the owner’s instructions and was flying solo at the time of the accident.

After the accident, the engine was test-run to full power at a recovery facility. Given that the engine was able to be successfully run after the accident, it is unlikely that there was a mechanical failure or malfunction before the accident that would have precluded its normal operation. The temperature and dewpoint conditions at the time of the accident were conducive to the formation of carburetor icing at cruise or idle engine power settings, and the pilot did not describe his use of carburetor heat during the landing approach or go-around attempt. It could not be determined whether or not carburetor icing impacted the engine’s production of power.

The air traffic controller’s description of the airplane’s abrupt left turn, that it appeared “out of control,” and that it descended in a steep nose down attitude suggest that the airplane had encountered an aerodynamic stall during the go-around attempt. The relatively low-energy impact signatures observed on the wreckage were also consistent with this description. Based on the available information, it is likely that the pilot failed to maintain control of the airplane during a go-around attempt, which resulted in an exceedance of the airplane’s critical angle of attack and an aerodynamic stall/spin. Whether a partial loss of engine power preceded this loss of control could not be determined.

Probable cause

The pilot’s failure to maintain aircraft control and his exceedance of the airplane’s critical angle of attack, which resulted in an aerodynamic stall and spin during an attempted go-around.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA24LA256
Event ID
20240612194448
Case number
ERA24LA256
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, 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: eba33273b4bedc012c2c452aa47d5aa3e1a613577021f44098f12d455ecc9e9c; retrieved 2026-09-16T18:52:59.461Z.