The U.S. aircraft register, updated daily · Carbon Free Flight by 2050
Accidents · NTSB ERA24LA256 · Final report

Amateur-built 701 accident near Ocala, Florida, June 8, 2024

On June 8, 2024 at about 11:50 pm local time, a 2017 amateur-built 701, registered N643E, was substantially damaged in an accident during approach (VFR go-around) near Ocala, Florida (Ocala International Airport). It was a personal flight under general aviation rules (Part 91). 1 person had minor injuries. The weather was visual conditions (good weather).

Preview. This page is not yet listed for search engines.

The NTSB's probable cause their words, unchanged

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.

Source: NTSB aviation accident database, copy made October 4, 2026. Docket and reports at the NTSB.

What the record shows

Date
June 8, 2024 · about 11:50 pm local time
Place
Ocala, Florida · Ocala International Airport · map
Type
Accident
Injuries
1 person had minor injuries.
Weather
visual conditions (good weather)
Aircraft
Amateur-built 701 NO SERIES, built 2017
Registration
N643E · registry record · serial 7-8942
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Loss of control in flight during approach (VFR go-around) defining event
  2. Aerodynamic stall/spin during approach (VFR go-around)
  3. Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent
  4. Unknown or undetermined during approach (VFR go-around)

The NTSB's findings

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

Pilot

  • Certificate: commercial pilot, private
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 490 hours in all; 1 in this make and model; 120 in the last 90 days; 100 in the last 30 days; 360 as pilot in command
  • Last flight review: December 25, 2023
  • Medical certificate: Class 1 (without waivers/limitations)
  • Seat: left
  • Injury: minor injuries

The aircraft

  • Airframe total time: 65.2 hours
  • Last inspection: condition inspection, January 26, 2024; 4 hours since
  • Maximum gross weight: 1,100 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Continental GPU (piston); 0 hours total

The flight

  • Flight plan: none
  • Runway 36, 7,467 ft by 150 ft

Weather at the time

  • Light: daylight
  • Wind: from 250° at 8 knots
  • Visibility: 10 statute miles
  • Sky: broken clouds at 9,500 ft
  • Temperature: 88°F (31°C), dew point 75°F (24°C)
  • Altimeter: 29.91 inHg
  • Observation at 7:51 pm from OCF, 1 miles away

Weather report (METAR): METAR KOCF 082351Z AUTO 25008KT 10SM BKN095 31/24 A2991

Injuries

FatalSeriousMinorNone
Flig1

About this page

Everything above comes from the NTSB's public accident database: the narrative, probable cause and findings are the NTSB's own words, and the coded tables behind its report (pilot, aircraft, flight, weather, injuries, sequence of events) are written out in plain English. Pilots' ages, home towns and medical details are left out on purpose. The docket at the NTSB holds the report as a PDF and the investigation's photographs and documents. This site never names pilots, passengers or anyone else involved. A preliminary report describes what is known soon after the event and can change; the final report, with the probable cause, usually follows one to two years later and this page is refreshed when it does. Case number ERA24LA256.