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.

NTSB Preliminary: Cessna 172S Skyhawk SP, N387AF, fatal accident occurred on June 23, 2026, near Willard, Utah

  • Location: Willard, UT 
  • Accident Number: WPR26FA232 
  • Date & Time: June 23, 2026, 22:47 Local 
  • Registration: N387AF 
  • Aircraft: Cessna 172 
  • Injuries: 1 Fatal
  • Flight Conducted Under: Part 91: General aviation - Personal

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

https://registry.faa.gov/aircraftinquiry/Search/NNumberResult?NNumberTxt=N387AF

On June 23, 2026, at about 2247 mountain daylight time, a Cessna 172S, N387AF, was destroyed when it was involved in an accident near Willard, Utah. The pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

The instrument-rated private pilot was conducting a solo night cross-country flight as part of a commercial flight training program. The pilot and his instructor had conducted a dual night cross-country flight following a similar route as the accident flight about 12 days prior.

On the evening of the accident flight, a flight instructor reviewed the pilot’s plan and dispatched the airplane. He observed the pilot using Foreflight electronic flight bag (EFB) software to plan his route and obtain an online briefing for the visual flight rules (VFR) solo night cross-country flight from Salt Lake City, Utah (SLC) to Idaho Falls, Idaho (IDA). According to the route the pilot entered in Foreflight, he planned to depart SLC and perform a climbing left turn to an enroute altitude of 8,500 ft mean sea level (msl). The pilot planned to use the Mountain Road VFR transition northbound through SLC Class B airspace, as indicated on the Salt Lake City Terminal Area Chart. The transition procedure required a clearance from air traffic control (ATC) and specified navigating between several charted VFR waypoints over the eastern edge of the city, and along the west edge of the mountain range. Upon completion of the transition, the pilot’s planned route included a left turn to the northwest from the Ogden Canyon VFR waypoint to the Power Station VFR waypoint, where he would then turn northbound, and follow prominent interstate highways enroute to Idaho Falls (see figure 1). The pilot also planned and received a Foreflight briefing for a return flight that same night.

Preliminary ADS-B data from the FAA showed that the airplane departed SLC from runway 17 at about 2225 local time, turned left, and began following the Mountain Road VFR transition northbound, consistent with the pilot’s planned route (see figure 1). While flying the transition, the pilot communicated with a Salt Lake City Approach air traffic controller; when asked if he wanted to receive VFR flight following services from Salt Lake Center, he responded that he did. At about the same time he passed the Weber Canyon VFR waypoint, ATC provided the pilot a discrete transponder code, which the pilot entered. From that waypoint, the airplane continued north and overflew the mountain foothills, rather than turning left to navigate to the McDay-Dee Hospital VFR waypoint as indicated in the planned flight. Upon exiting the Class B airspace, ATC advised the pilot to maintain his own navigation at an appropriate VFR altitude, which the pilot acknowledged and repeated back. No further communication was recorded from the pilot.

Upon reaching the Ogden Canyon VFR waypoint, the airplane did not make the planned left turn toward the Power Station VFR waypoint. Instead, it continued northbound, maintaining about 8,800 - 9,000 ft msl (ADS-B geometric altitude) until it impacted mountainous terrain southeast of Willard Peak at 2247:40 (see figure 2).

The wreckage was located in an area of steep, rocky, upsloping mountainous terrain at an elevation of about 9,130 ft msl. The slope consisted of loose shale-like rock and rock outcroppings. The airplane came to rest on the south face of the mountain, about 375 ft from (and about 130 ft in elevation below) the ridgeline. All components of the airframe and several fragmented engine accessories were present in the vicinity of the primary wreckage. The engine was located down-slope from the primary wreckage.

Fragments of the engine and its related accessories were found within the primary impact point area, which was located about 45 ft west of the main wreckage, which consisted of the fuselage and empennage. Additional engine-related fragments and components were found throughout the debris field. Ground scarring was limited to the immediate vicinity of the primary impact point. An additional impact point was identified about 35 ft east of the primary impact point, which contained fragmented pieces of wingtip material and the right wingtip position light.

The fuselage exhibited extensive fore-aft crushing along the longitudinal axis. The firewall and forward fuselage structure were crushed aft to the rear seat position. Both main landing gear were separated from the fuselage. The horizontal stabilizer was impact damaged; the vertical stabilizer was impact damaged near its top and missing its beacon light. The wings were separated from the fuselage, located uphill of the main wreckage and the primary point of impact. The forward spar carry-through structure remained attached to the left wing. Crushing, twisting, and bending were noted throughout both wings, and both fuel tanks were ruptured. 

The propeller was located within the debris field about 30 ft northwest of the primary impact point, between the wings and the fuselage. The engine crankshaft flange was separated from the crankshaft and remained attached to the propeller hub by the attachment bolts. Both propeller blades were curled aft with substantial twisting, leading edge gouges, chordwise scratches, and scratching throughout the cambered faces. 

A line of disturbed ground was observed between the main wreckage and the engine, which was damaged by impact forces and located about 350 ft downslope from the main wreckage. 

At the time of the accident, the moon was 28° above the horizon, at an azimuth of 210°, and 72% illuminated. Some smoke and haze from regional forest fires was present. Visual meteorological conditions and visibility greater than 10 miles were reported along the accident airplane’s route of flight. The pilot of another airplane, who was also flying the Mountain Road transition about 10 nautical miles behind the accident airplane, reported that the flight conditions were VFR, the horizon and mountainous terrain were dark and mostly indiscernible, the wind was light, and the ride northbound was smooth.

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