Thursday, July 16, 2026

Beechcraft 95-B55 Baron, N202DK, fatal accident occurred on July 9, 2026, near Waterloo, Illinois

This is preliminary information, subject to change, and may contain errors. Any errors in this writing will be corrected when/if the NTSB preliminary report is released.

https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=N202DK

- History of Flight:
On July 9, 2026, at about 2248 local time, a Beechcraft 95-B55 Baron, N202DK, registered to Auto Key Masters and Locksmith LLC out of Watts, Oklahoma, was destroyed when it was involved in an accident near Waterloo, Illinois. The two non-instrument rated private pilots were fatally injured. The personal flight originated from St. Louis Regional Airport (ALN/KALN), 
St. Louis, Illinois, at 2226, and was destined to Smith Field Airport (SLG/KSLG), Siloam Springs, Arkansas.

According to preliminary flight-tracking history, on July 9, at 1438, the airplane departed Sallisaw Municipal Airport (JSV/KJSV), Sallisaw, Oklahoma, on a flight to SLG. The airplane landed at 1500, and departed at 1644 on a flight to ALN. The airplane landed in Saint Louis at 1827. The purpose of the flight was to watch a St. Louis Cardinals game.

According to Automatic dependent surveillance-broadcast (ADS-B) data, the airplane departed runway 11 at St. Louis and proceeded to enter a climbing right hand turn to an altitude of 5,100 ft. At 2245, the airplane started a descent from that altitude. At 2246, the airplane entered a right hand turn with a reported descent rate of 1400 feet per minute (fpm). At 2246:38, the airplane stopped the turn and was now flying at 4,400 ft. At 2247:39, the airplane entered a left hand turn to the south. At 2247:53, the airplane was seen on a 2500 fpm descent. The airplane descended to about 4,000 ft before it began a very steep climb with a reported rate of 7360 fpm. At 2248:15, the airplane reached the crest of that climb at 5,100 ft before it began another rapid descent that continued until the end of the track. At one point, the reported descent rate was 11260 fpm. The last ADS-B data point was recorded at 2248:40, the airplane was at 2,000 ft, 157 knots groundspeed, and 3000 fpm descent rate.

Figure 1: ADS-B exchange track ran through Flysto

Figure 2: Airplane entering left hand turn towards end of track

Figure 3: Crest of climb

Figure 4: Descent after the climb

Figure 5: End of track

Figure 6: Flightaware track with weather overlay

- Pilot Information:
The pilot, aged 48, held a private pilot certificate with an airplane single engine land and multi engine land ratings. His third class FAA medical was issued on 9/2024. The pilot did not hold an instrument rating.

The pilot's son, aged 22, held a private pilot certificate with an airplane single engine land rating. His third class FAA medical was issued on 9/2024. The pilot did not hold an instrument rating.

- Airplane Information:
The accident airplane, serial number TC-2152, was manufactured in 1978. It was a six-seat twin-engine monoplane with a retractable tricycle landing gear configuration. The airplane was powered by two 260 HP Continental IO-470L reciprocating engines, each engine drove a three-bladed McCauley propeller.

According to a sale listing for the accident aircraft, it was equipped with a Garmin GNS430W GPS and Century IV autopilot.

- Weather Information:
According to weather imagery from the time of the accident, severe conditions were present in the region and directly in the airplane's flight track. A convective SIGMET was active at the time for the region. Two nearby airports were reporting possible thunderstorms as well.

According to the National Weather Service (NWS) Area Forecast Discussion for St Louis Missouri, issued at 0621 PM CDT (1821 LT) Thu Jul 9 2026: 

"The main concern will be scattered showers and thunderstorms developing at various times through the upcoming period. However, confidence in these affecting any one TAF site is fairly low. This evening`s thunderstorms are likely to occur south of the St Louis metro, but may impact parts of central Missouri with JEF the most likely to be impacted. Otherwise we expect primarily mid level cloud decks well within the VFR range. Additional thunderstorms are possible tomorrow afternoon area wide, but confidence remains low on where or when."

314
FXUS63 KLSX 092321
AFDLSX

Area Forecast Discussion
National Weather Service St Louis MO
621 PM CDT Thu Jul 9 2026

.KEY MESSAGES...

- A flash flood watch is in effect through Friday night in
  southeast Missouri and southwest Illinois, with multiple
  rounds of showers and thunderstorms expected.

- Some storms this evening and again Friday afternoon/evening
  may be strong to severe with damaging winds the primary
  threat each day.

- Dry weather along with above normal temperatures are forecast
  Sunday through the middle of next week.

&&

.SHORT TERM /THROUGH FRIDAY NIGHT/...
Issued at 237 PM CDT Thu Jul 9 2026

GOES-19 visible satellite imagery shows 3, maybe 4 MCVs across
the region all moving eastward. One is near K3LF and the other
near KUIN. Both of these features has recently led to convective
initiation just east/southeast of each of these in west central
and south-central Illinois. One or two of these storms may be
on the stronger side with damaging winds the primary threat.
More convective development is expected by early this evening as
the low-level jet strengthens. Moisture convergence associated
with the low-level jet will also increase, and this combined
with an uptick in midlevel ascent downstream of the upstream
MCVs (one near OK-KS border and another possible MCV near KSTJ)
should lead to more widespread showers and thunderstorms. This
activity is expected to focus mainly across southeast Missouri.
Concern for flash flooding is increasing, as training is
expected through the early overnight hours in an environment
that is supportive of high rainfall rates (deep warm cloud
depths, anomalous precipitable water values). New cells should
develop on the west/northwest flank of the activity through the
early overnight hours as the low-level jet veers from the
southwest to the west. Past events with these setups tend to
have a narrow west/northwest to east/southeast axis of very
heavy rainfall on the west/southwest edge of the precipitation
shield. That may indeed occur again tonight, and if so, may
heavily impact a portion of a few counties in southeast
Missouri. The LPMM of the HREF has a narrow axis of 3-4" whereas
the REFS has almost double those totals. If training occurs
long enough, I would not rule out the higher-end potential of
the REFS LPMM. Due to this threat for significant rainfall
amounts and flash flood potential, a flash flood watch is now in
effect beginning this afternoon through Friday night across
southeast Missouri and a small part of southwest Illinois.

The heavy rain threat overnight tonight should end around dawn with
the stronger low-level moisture convergence shifting to the
east/southeast more toward the lower Ohio Valley. Mostly dry
conditions are then forecast through the remainder of the morning
hours across the area. Attention will then look to the west again.
Another MCV(s?) is likely to be moving across eastern Kansas by
midday. The exact track/timing of this feature is not certain,
nor is the environment ahead of it due to the morning showers
and thunderstorms. The effective front may be to our south,
though at least some sunshine should allow for instability to
climb ahead of the approaching MCV. Scattered showers and
thunderstorms are forecast across the area, though there may be
a bit more focus from central-southeast Missouri during the late
afternoon/evening time frame. Similar to today, damaging winds
should be the primary threat. Locally heavy rainfall will also
be possible as there will be little/no change in the environment
so efficient warm rain processes are expected. Areas that get
hit hardest tonight would be the main concern as soils may be
very saturated and any additional (even brief) heavy rainfall
could cause renewed hydrological issues.

The low-level jet increases again Friday night, though it does not
look as strong as tonight. Therefore, I think there will be another
uptick in the coverage of showers and thunderstorms, but the overall
threat for flash flooding likely will stay mostly confined to areas
that are hardest hit tonight as alluded to in the paragraph above.

&&

.LONG TERM /SATURDAY THROUGH THURSDAY/...
Issued at 237 PM CDT Thu Jul 9 2026

(Saturday - Saturday Night)

Uncertainty on Saturday increases, in part due to the 2-3 rounds of
showers and thunderstorms anticipated before this time period.
Deterministic guidance though does show a midlevel shortwave trough
moving south/southwest almost beneath the amplifying mid/upper level
ridge to the west. Showers and thunderstorms are again possible
Saturday/Saturday night, mainly across southeast
Missouri/southwest Illinois, which should be closer to the
effective frontal boundary. If confidence increases in the
threat for showers and thunderstorms on Saturday, the existing
flash flood watch may need to be extended in time.


(Sunday - Next Thursday)

Not a lot has changed over the past 24 hours, with a historic record-
breaking mid/upper level ridge expected across the northern
Plains/Upper Midwest. Our area will be within deep northeasterly
flow aloft, so dry weather is expected. The low-level thermal ridge
is also forecast to stay well to our north, so 850-hPa temperatures
are actually pretty close normal (+16 to +20C). Nighttime lows are
forecast to be near seasonal averages, with daytime highs likely a
bit above normal due to plenty of sunshine expected each day.
Relative humidity (dewpoint) values also should tick down early next
week, aided by continued deep northeasterly flow. This means heat
index values should not be too much higher than the ambient air
temperature, and the chances of heat advisory duration criteria
(100+ for 4+ days) seem very small attm.

&&

.AVIATION /00Z TAFS THROUGH 06Z SATURDAY/...
Issued at 618 PM CDT Thu Jul 9 2026

The main concern will be scattered showers and thunderstorms
developing at various times through the upcoming period.
However, confidence in these affecting any one TAF site is
fairly low. This evening`s thunderstorms are likely to occur
south of the St Louis metro, but may impact parts of central
Missouri with JEF the most likely to be impacted. Otherwise we
expect primarily mid level cloud decks well within the VFR
range. Additional thunderstorms are possible tomorrow afternoon
area wide, but confidence remains low on where or when.

&&

.LSX WATCHES/WARNINGS/ADVISORIES...
MO...Flood Watch through Saturday morning for MOZ072>075-084-085-
     099.
IL...Flood Watch through Saturday morning for ILZ079.

&&

$$

SHORT TERM...Gosselin
LONG TERM...Gosselin
AVIATION...Kimble

- Additional Information:
According to the NTSB Safety Alert SA-023, Pilots: Manage Risks to Ensure Safety: Good decision-making and risk management practices can help prevent accidents:

The Problem:

Although few pilots knowingly accept severe risks, accidents can also result when several risks of marginal severity are not identified or are ineffectively managed by the pilot and compound into a dangerous situation. Accidents also result when the pilot does not accurately perceive situations that involve high levels of risk.

Ineffective risk management or poor aeronautical decision-making can be associated with almost any type of fatal accident across all general aviation (GA) sectors.

What can pilots do?

  • Develop good decision-making practices that will allow you to identify personal attitudes that are hazardous to safe flying, apply behavior modification techniques, recognize and cope with stress, and effectively use all resources. Understand the safety hazards associated with human fatigue and strive to eliminate fatigue contributors in your life. 
  • Understand that effective risk management takes practice. It is a decision-making process by which you can systematically identify hazards, assess the degree of risk, and determine the best course of action. 
  • Be honest with yourself and your passengers about your skill level and proficiency. Refuse to allow external pressures, such as the desire to save time or money or the fear of disappointing passengers, to influence you to attempt or continue a flight in conditions in which you are not comfortable. 
  • Be honest with yourself and the FAA about your medical condition. If you have a medical condition or are taking any medication, do not fly until your fitness for flight has been thoroughly evaluated.
- Additional Figures:

Groundspeed for entire track

Vertical rate for last portion of track

Wednesday, July 15, 2026

Cirrus SR22, N127DC, accident occurred on July 2, 2026, near Lafayette, Tennessee

  • Location: Lafayette, TN 
  • Accident Number: ERA26LA257 
  • Date & Time: July 2, 2026, 10:32 Local 
  • Registration: N127DC 
  • Aircraft: CIRRUS DESIGN CORP SR22 
  • Injuries: 2 None 
  • Flight Conducted Under: Part 91: General aviation - Personal
https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/203308/pdf

https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=N127DC

On July 2, 2026, at 1032 central daylight time, a Cirrus Design Corp SR22, N127DC, was substantially damaged when it was involved in an accident near Lafayette, Tennessee. The pilot and passenger sustained no injuries. The airplane was operated as a Title 14 Code of Federal Regulation Part 91 personal flight. 

The pilot reported that following the completion of an annual inspection, he was returning a ferry pilot to Owensboro/Davis County Regional Airport (OWB), Owensboro, Kentucky. About 20 minutes into the flight, while at an altitude of 6,500 feet mean sea level, the engine completely lost power. The pilot initially attempted to divert to the nearest airport, which was about 12 miles away, but then determined they would be unable to reach the airport. The pilot then made a distress call to air traffic control and decided to activate the airplane’s whole airframe parachute system at an altitude of 1,975 feet. The parachute successfully deployed and the airplane came to rest in a tree within an urban neighborhood. The airplane sustained substantial damage to the empennage, fuselage, and wings. 

The airplane was recovered and retained for further examination.

Beechcraft S35 Bonanza, N6040F, accident occurred on June 25, 2026, near Dome, Arizona

  • Location: Dome, AZ 
  • Accident Number: WPR26LA236 
  • Date & Time: June 25, 2026, 11:25 Local 
  • Registration: N6040F 
  • Aircraft: Beech S35 
  • Injuries: 4 None 
  • Flight Conducted Under: Part 91: General aviation - Personal

https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/203282/pdf

https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=N6040F

On June 25, 2026, about 1125 mountain standard time, a Beech S35, N6040F, sustained substantial damage when it was involved in an accident near Dome, Arizona. The pilot and three passengers were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. 

The pilot reported that he departed Eagle Roost Airport (27AZ), Aguila, Arizona, for a crosscountry flight to Yuma Marine Corps Air Station/Yuma International Airport (YNK), Yuma, Arizona. According to the pilot, about 15 nm northeast of YNK the engine began to run rough, so he enriched the mixture to smooth out the engine. The pilot then decided to perform a precautionary landing and landed the airplane on a dirt road with the landing gear retracted. Shortly after touchdown, the airplane veered right off the road and came to rest upright in a ditch. Subsequently, the right wing was substantially damaged. 

The airplane was recovered to a secure facility for further examination.

Bailey-Moyes Dragonfly, N3849A, fatal accident occurred on June 22, 2026, near Clover Valley Airport (3WI5), Whitewater, Wisconsin

  • Location: Whitewater, WI 
  • Accident Number: CEN26LA231 
  • Date & Time: June 22, 2026, 19:15 Local 
  • Registration: N3849A 
  • Aircraft: BAILEY-MOYES DRAGONFLY 
  • Injuries: 1 Fatal, 1 None 
  • Flight Conducted Under: Part 91: General aviation - Glider tow

https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/203218/pdf

https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=N3849A

On June 22, 2026, about 1915 central daylight time, a Bailey-Moyes Dragonfly, N3849A, was involved in an accident near Whitewater, Wisconsin. The pilot of the Dragonfly was not injured. The pilot of the hang glider in tow was fatally injured. The tow operation was conducted under the provisions of Title 14 Code of Federal Regulations Part 91 as a glider tow flight. 

The Dragonfly, a tow plane with a hang glider in tow, took off and had reached an altitude of about 30 ft above the ground when the pilot of the tow plane felt something through the tow cable. When he looked back, he saw the hang glider pilot hanging from the base bar. The hang glider pilot fell to the ground and was fatally injured. The pilot of the tow plane released the glider, returned to the airport, and landed without further incident. The hang glider came to rest on airport property near the fallen pilot. 

An inspector from the Federal Aviation Administration examined the harness and carabiner used to attach the glider pilot and no obvious defects were found. The harness and carabiner were retained for further examination.

Piper PA-28-140 Cherokee, N3995K, accident occurred on July 5, 2026, near Salome, Arizona

  • Location: Salome, AZ 
  • Accident Number: WPR26LA245 
  • Date & Time: July 5, 2026, 08:25 Local 
  • Registration: N3995K 
  • Aircraft: Piper PA-28-140 
  • Injuries: 2 None 
  • Flight Conducted Under: Part 91: General aviation - Personal

https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/203329/pdf

https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=N3995K

On July 5, 2026, at about 0825 Pacific daylight time, a Piper PA-28-140, N3995K, was substantially damaged when it was involved in an accident near Salome, Arizona. The pilot and passenger were uninjured. The airplane was operating as a Title 14 Code of Federal Regulations Part 91 personal flight. 

According to the passenger, who was a rated pilot and mechanic, the purpose of the flight was to conduct an engine break-in flight following a recent engine overhaul. Before the flight, the pilot and passenger completed a preflight inspection and engine ground run, during which no anomalies were noted. The magneto checks were within specifications, with an approximate 100-rpm drop, and the passenger did not observe any abnormal engine temperature or oil pressure indications. The passenger reported that he had previously conducted ground runs on the engine following the overhaul, and they were normal. 

The airplane departed from runway 17 at Western Sky Airpark (OAZ2), Salome, Arizona. The passenger described the takeoff as normal and stated that the engine was producing about 2,400 rpm, with the throttle full forward and the mixture full rich. At about 800 to 900 ft above ground level, the pilot turned the airplane to the right and began reducing the throttle from full power. The passenger estimated the throttle reduction at about 200 rpm, though he did not recall the exact rpm amount. 

Immediately after the throttle was reduced, the engine lost all power. The passenger reported there were no indications of an impending engine failure, including no unusual vibration, smoke, sounds, or abnormal gauge readings. The pilot then searched for a forced landing area. The passenger estimated that about 20 to 30 seconds later the airplane impacted terrain. The airplane sustained substantial damage to the wings, fuselage, tail, and empennage. 

The wreckage was recovered to a secure location for further examination.

Tuesday, July 14, 2026

NTSB Preliminary: Piper PA-24-250 Comanche, N6403P, fatal accident occurred on June 20, 2026, near Geauga County Airport (7G8), Middlefield, Ohio

  • Location: Middlefield, OH 
  • Accident Number: WPR26FA224 
  • Date & Time: June 20, 2026, 15:35 Local 
  • Registration: N6403P 
  • Aircraft: Piper PA-24-250 
  • Injuries: 3 
  • Fatal Flight Conducted Under: Part 91: General aviation - Personal

https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/203204/pdf

https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=N6403P

On June 20, 2026, about 1535 eastern daylight time, a Piper PA-24-250, N6403P, was substantially damaged when it was involved in an accident near Middlefield, Ohio. The pilot and two passengers sustained fatal injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. 

A surveillance camera showed the airplane taxiing from an airport ramp at Youngstown/Warren Regional Airport (YNG), Youngstown/Warren, Ohio at 1520. Witnesses reported that the airplane’s intended destination was Geauga County Airport (7G8), Middlefield, Ohio, which was about 21 nm northwest of YNG (see figure 1).

Preliminary ADS-B data revealed that the airplane departed runway 23 at YNG about 1524 and maneuvered to the northwest. The airplane then climbed to a cruise altitude of about 2,300 ft mean sea level (msl). About 5 nm west of 7G8, the airplane turned to the west and initiated a descent from about 2,700 ft msl for a straight in approach for runway 29 at 7G8. About two miles from the departure end of runway 29, about 1,520 ft msl, the airplane started a descending right turn (see figure 2). The flight track data ceased about 1 nm east of runway 29, at an altitude of 1,345 ft msl, and at a groundspeed of approximately 63 knots.\

A review of preliminary air traffic control (ATC) audio revealed that the airplane was receiving visual flight rules (VFR) flight following services from ATC. Shortly after the airplane established cruise flight, ATC issued the pilot an advisory for an area of depicted moderate weather 4 miles northwest of YNG, extending about 7 miles northwest, moving to the southeast. The pilot received further instructions to deviate as necessary to avoid weather and subsequently responded to the controller that they could see through the precipitation, which appeared to be light. About 9 miles east of 7G8, ATC advised the location of their destination airport. The pilot responded that they did not have the airport environment in sight and requested to cancel flight following. Radar services were then terminated at 1529, and the pilot was advised to set his transponder to 1200 and change to the advisory frequency. At 1535, about 1,400 ft msl, the airplane dropped off radar coverage. No further communication with the airplane was noted after this time.

A witness reported that the she saw the airplane cross above the tree line into her property from east to west in a straight and level attitude. Shortly after, she noted that the right wing dipped, while descending slightly, then she observed the airplane briefly return to a level roll attitude. She stated that the airplane made a sharp right turn followed by a steep, nose down descent into a field. 

The airplane was located 1 nautical mile east of 7G8 in an area of open cow pasture at an elevation of about 1,130 ft msl. The debris path was 50 ft long by 40 ft wide and was oriented on a northeast heading. All major components of the airplane were found within the debris path.

The first identified point of contact (FIPC) was a ground scar with blue transfer mark, consistent with impact of the right tip tank, which was found separated about 30 ft northwest of the FIPC. A larger ground scar, consistent with impact of the engine was located about 23 feet northeast of the FIPC. The main wreckage was about 50 feet from the FPIC and consisted of the fuselage, wings, empennage and engine (see figure 3). 

The fuselage exhibited impact damage from the firewall to the lower cabin. All windows, including the windscreen, were separated from the airframe. Flight control cable continuity for the rudder, elevator, and ailerons was confirmed from the cockpit to each of the respective flight control surfaces. 

The left wing was partially attached to the fuselage with chordwise wrinkles and crush damage from midspan to the wing tip. The damage extended from the left wing leading edge to the trailing edge. The flap and aileron both remained attached to the wing at their respective hinges.

The right wing remained partially attached to the fuselage and had been torn chordwise about midspan. Chordwise wrinkles and crush damage were observed along the midspan of the wing which extended from the leading edge to the trailing edge. The flap and aileron both remained attached to the wing by their respective hinges.

The empennage remained mostly intact with the vertical stabilizer attached to the tailcone and the rudder remained attached to the vertical stabilizer by its hinges. No damage was observed to the vertical stabilizer or the rudder. The stabilator remained attached to the tailcone bulkhead at its hinges.

The engine remained attached to the fuselage. All components and accessories remained secured to their respective mounting pads, with exception of the right magneto, carburetor, and airbox, which were all found within the engine compartment. The three-blade, aluminum, constant speed propeller remained attached to the crankshaft propeller flange. Two blades appeared intact and undamaged. The third blade was dislodged in the hub and bent aft. 

The airplane and engine were recovered to a secured facility for further examination. 

NTSB Preliminary: Comp Air CA6-WB, N82BT, fatal accident occurred on June 20, 2026, near Nicholasville, Kentucky

  • Location: Nicholasville, KY 
  • Accident Number: WPR26FA223 
  • Date & Time: June 20, 2026, 08:46 Local 
  • Registration: N82BT 
  • Aircraft: Comp Air CA6-WB 
  • Injuries: 2 Fatal 
  • Flight Conducted Under: Part 91: General aviation - Personal

https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/203202/pdf

https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=N82BT

On June 20, 2026, about 0846 eastern daylight time, an experimental amateur-built Comp Air CA6-WB, N82BT, was destroyed when it was involved in an accident near Nicholasville, Kentucky. The pilot and passenger were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. 

Recorded ADS-B data provided by the Federal Aviation Administration (FAA) showed that the airplane departed from Lexington, Kentucky (LEX), runway 27 at about 0840:00, made a climbing left turn toward the southeast and ascended to an altitude of about 4,500 ft mean sea level (msl). At 0844:57, the data showed that the airplane began a descent, and its groundspeed steadily increased, until ADS-B contact was lost, about 1 nautical mile north of the accident location at 0845:23. 

Review of radio communications between the pilot, Lexington Tower and Terminal Radar Approach Control revealed that about 1 minute after departure, the pilot established radio communications with Terminal Radar Approach Control and requested flight-following services. At 0845:23, the controller stated radar contact was lost, and despite multiple attempts, no response from the pilot was received.

A flight log recovered from the accident site identified Gwinnett County Airport–Briscoe Field (LZU), Lawrenceville, Georgia, as the intended destination for the flight segment, with subsequent waypoints continuing to Fernandina Beach Municipal Airport (FHB), Fernandina Beach, Florida.

According to witness video and audio captured by a doorbell camera near the accident site, the airplane was observed flying at a low altitude while emitting a grinding noise, followed by a popping sound. Witnesses reported that the fuselage then descended inverted after separating from both wings. The airplane continued in an inverted, near-vertical descent until the airplane went out of visual range. Several witnesses described the airplane as “spinning” about its lateral axis in the vertical descent.

Examination of the accident site revealed that the airplane impacted level pasture terrain at a horse farm approximately 8 nautical miles south of LEX at an elevation of about 890 ft mean sea level. The first identified point of contact (FIPC) was the engine, which was found inverted, partially embedded within terrain, and partially separated from the fuselage. The fuselage came to rest on its left side approximately 2 ft east of the engine.

The debris path extended approximately 1,700 ft, on a heading of about 090° magnetic from the main wreckage. Throughout the wreckage debris path, various components of the airplane, including portions of the flight control surfaces and propeller fragments were observed. 

The wreckage was recovered to a secure location for further examination.