Event ERA24LA256

Factual narrative

On June 8, 2024, about 1950 eastern daylight time, an experimental amateur-built Zenith 701, N643E, was substantially damaged when it was involved in an accident near Ocala, Florida. The commercial pilot sustained minor injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot reported that the airplane was on short final approach to runway 36, a 7,467-ft-long runway at Ocala International Airport (OCF), Ocala, Florida. He reported that 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 expected” and collided with trees near the end of the runway. The pilot did not describe whether or not he utilized carburetor heat during the landing approach or after initiating the go-around. During an interview with a Federal Aviation Administration (FAA) inspector, an air traffic controller on duty at the time of the accident stated that the airplane departed about 1930 and the pilot stated that he would be “doing pattern work.” The pilot completed two orbits but did not perform any touch-and-go landings. After completing two low approaches, the airplane was cleared to land on runway 36 and turned onto the base leg of the airport traffic pattern. On final approach, at an altitude about 20 ft above the runway, the airplane turned abruptly 45° to the west and appeared out of control. The airplane subsequently began to climb and then turned “hard left and nose-dived” into the trees. The controller did not mention birds during his interview. Airport security video captured the accident airplane on short final approach. Due to automatic panning, the video did not capture the accident sequence, but no birds were observed when the airplane was on short final approach. During an interview with an FAA inspector, the airplane owner stated that the pilot was attempting to build flight experience to meet the requirements of an airline transport pilot certificate. He worked for the owner part-time and asked if he could fly the accident airplane. The owner stated that he agreed, 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. The pilot reported a total flight experience of 490 hours, of which 1 hour was in the accident airplane make and model. The FAA inspector observed the wreckage nose-down in a wooded area. Both wings were bent forward and sustained damaged to their leading edges. The fuselage also sustained substantial damage. The wreckage was transported to a recovery facility, where an independent mechanic started the engine and conducted a test run to full power. The reported wind at OCF at 1951 was from 250° at 8 knots. The reported temperature was 31°C and the dew point was 24°C. The calculated relative humidity at this temperature and dewpoint was 66 percent. Review of the icing probability chart contained within Federal Aviation Administration Special Airworthiness Information Bulletin CE-09-35 revealed the atmospheric conditions at the time of the accident were conducive to icing at “glide [idle] and cruise power." 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. 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).

• — Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot
• — Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Angle of attack-Capability exceeded