Tuesday, September 09, 2025

Lancair NLA-275-FR-C Super Barracuda, N345LA, fatal accident occurred on August 18, 2025, near Bradley, Arkansas

  • Location: Bradley, AR 
  • Accident Number: CEN25FA321 
  • Date & Time: August 18, 2025, 21:33 Local 
  • Registration: N345LA 
  • Aircraft: Lancair NLA-275-FR-C 
  • Injuries: 1 Fatal 
  • Flight Conducted Under: Part 91: General aviation - Personal

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

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

On August 18, 2025, about 2133 central daylight time, a Lancair NLA-275-FR-C airplane, N345LA, was destroyed when it was involved in an accident near Bradley, Arkansas. The pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

A preliminary review of ADS-B data showed the airplane departed Lakeway Airpark, Lakeway, Texas, about 2011. The airplane then proceeded on a predominant northeast course. At 2018, the airplane reached an altitude of about 10,000 ft mean sea level (msl). After about 50 minutes, the airplane began a climb to an altitude of about 12,175 ft msl. After about 18 minutes, the airplane climbed to maximum altitude of about 14,125 ft msl, followed by a descent to about 12,375 ft msl.

The airplane then began a climb from 12,375 ft msl to 12,675 ft msl, followed by a descent. About 2132 and at 11,800 ft msl, the airplane began a rapid right spiraling descent. Near the end of the descent, the data indicated that the airplane made a momentary level off and climb before a descending left turn into terrain (see figure 1).

The main wreckage of the airplane was located in wooded terrain. The initial impact point was a pine tree about 200 ft from the main wreckage. The path from the initial impact point to the main wreckage was on a true heading of 066°. The debris field from the initial impact point to the main wreckage contained fragments of the right wing.

The main wreckage was oriented with the airframe upright and the engine was inverted with a final heading of 180°. The airplane was destroyed by the impact sequence and the postimpact fire.

The wreckage was recovered from the accident site and was transported to a secure location for future examination. 

Cessna 340A RAM VI, N888MT, fatal accident occurred on August 27, 2025, near Midwest National Air Center Airport (GPH/KGPH), Mosby, Missouri

  • Location: Kearney, MO 
  • Accident Number: CEN25FA346 
  • Date & Time: August 27, 2025, 11:58 Local 
  • Registration: N888MT 
  • Aircraft: Cessna 340
  • Injuries: 2 Fatal 
  • Flight Conducted Under: Part 91: General aviation - Personal

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

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

On August 27, 2025, about 1158 central daylight time, a Cessna 340A, N888MT, was substantially damaged when it was involved in an accident near Kearney, Missouri. The pilot and passenger were fatally injured. The airplane operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

ADS-B data showed that the airplane departed the Washington Regional Airport (KFYG), Washington, Missouri, about 1057, and cruised at 4,500 ft mean sea level towards the Midwest National Air Center Airport (KGPH), Mosby, Missouri. About 25 miles from the airport, the airplane descended and entered the traffic pattern for a left base turn. The airplane’s altitude was lower than normal for a standard traffic pattern and continued to descend.

An eyewitness who lived near the accident site reported that the airplane appeared to be low and slow. The airplane’s left wing dipped down momentarily, returned wings level, then the left wing dipped again, and the airplane rolled left until it collided with terrain.

The airplane impacted an uncultivated soybean field about 0.6 miles from the approach end of runway 18. The initial impact point consisted of ground scars consistent with the left wing and airplane nose. A divot in the ground made by the right engine contained the right propeller assembly which had fractured at the crankshaft. The debris field was about 95 ft long, orientated along a 225° magnetic heading. The main wreckage consisted of the remainder of the airplane, to include the fuselage, empennage, tail section, both wings, both engines, and the left propeller. The main wreckage was aligned on a 120° magnetic heading. A postimpact fire had consumed a large portion of the fuselage.

On-scene examination of the airplane found that the landing gear was down, and the flaps were retracted. Flight control continuity was established from the cockpit to the flight controls. The cockpit instrumentation and electronic displays were largely destroyed in the fire.

The wreckage was retained for further examination.

Cessna 310Q, N7664Q, fatal accident occurred on August 23, 2025, near Milledgeville, Georgia

  • Location: Milledgeville, GA 
  • Accident Number: ERA25FA310 
  • Date & Time: August 23, 2025, 18:25 Local 
  • Registration: N7664Q 
  • Aircraft: Cessna 310Q 
  • Injuries: 1 Fatal 
  • Flight Conducted Under: Part 91: General aviation - Personal

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

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

On August 23, 2025, about 1825 eastern daylight time, a Cessna 310Q, N7664Q was destroyed when it was involved in an accident near Milledgeville, Georgia. The commercial pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations personal flight.

According to a witness, the pilot, who was based in Hilton Head, South Carolina, had flown to Fairfield County Airport (FDW), Winnsboro, South Carolina to obtain an instrument flight rules (equipment) recertification. Once completed, the pilot departed runway 4 at FDW about 1723 on an instrument flight rules (IFR) flight plan to Baldwin County Regional Airport (MLJ), Milledgeville, Georgia, about 130 nautical miles to the south-southwest.

Preliminary air traffic control communications and ADS-B data provided by the Federal Aviation Administration showed that after departure the pilot made a right turn and flew east for about 6 miles then made a left 360° turn to the southwest while climbing to an en route cruising altitude of about 10,000 ft mean sea level (msl). Altitudes, ground speeds and headings were consistent throughout the en route portion of the flight. As the airplane approached the initial approach fix (IBUDY) for the RNAV GPS 10 arrival to MLJ, the pilot was in communications with the Atlanta radar approach controller.

The pilot was issued a descent to 4,000 ft, provided the MLJ altimeter, and asked to verify that he was in receipt of the weather. The pilot responded with confirmation and was subsequently cleared for the RNAV Runway 10 Approach; the controller instructed the pilot to pass over IBUDY at or above 3,000 ft, which was acknowledged. There were no further transmissions from the pilot. About 10 seconds after the last communications and 6 miles east IBUDY, the airplane entered a left turn towards the south and descended. The controller advised the pilot “Low altitude alert, six four Quebec, check your altitude immediately.” The airplane continued on a track of about 120° and descended until flight track data was lost at 1821, about 6 nm west of the approach end of runway 10 at MLJ. During the descent, the airplane’s ground speed increased from 140 kts to 179 kts.

Reported weather conditions around the time of the accident showed overcast conditions around 2,200 to 2,500 ft with clouds extending to 10,000 ft. There was no precipitation activity in the area. There was a 10 to 15 knot tailwind during the last portion of the flight and the  freezing level was above 15,000 ft with no reported PIREPs in the region.

The airplane initially impacted the tops of 78-ft pine trees, then level terrain before coming to rest at an elevation of 462 ft. The wreckage path was oriented on a magnetic heading of 151° and the debris field was 135 ft wide and 660 ft long. The airplane wreckage was highly fragmented. There was no evidence of a post impact fire observed at the accident site and no evidence of an inflight fire was observed on the airplane wreckage. Tree and ground impact evidence was consistent with a slight airplane nose down wings level attitude.

Subsequent examination of the wreckage revealed that all major components of the airplane were accounted for. Elevator, rudder, and aileron flight control continuity were confirmed from the control surfaces through the cockpit controls; the control cables were traced through tensile overload breaks in the cables that exhibited a “broomstraw” appearance. The elevator trim position was measured through the actuator and corresponded to a trim setting about 5° nose up. The flap handle was in the up (retracted) position.

The fuel system components that were undamaged contained fluid with the smell and consistency of aviation fuel that was absent of contamination.

The landing gear selector was in the up (retracted) position and the landing gear actuators indicated that all 3-landing gear were retracted at the time of impact.

The instrument panel analog gauges and electronic primary flight instruments were all severely damaged by impact forces and their readings could not be observed; there was no non-volatile memory available for download.

Both engines separated from their respective wing mounts during the accident sequence. They were discovered on the last 1/3 of the wreckage path and were impact damaged. The spark plugs remained in their respective locations and the magnetos were impact-separated and located along the wreckage path.

Both propeller assemblies separated from their respective engines and were located within the wreckage path. Both 3-bladed metal propellers showed chordwise scraping on several of the blades with leading edge gouging and bends. One blade on each of the hubs, was separated and discovered within the wreckage field. The remaining propeller blades remained attached to their respective hubs.

The wreckage was retained for further examination.

Cessna 210D Centurion, N3806Y, fatal accident occurred on August 27, 2025, near Kearney Municipal Airport (EAR/KEAR), Kearney, Nebraska

  • Location: Kearney, NE 
  • Accident Number: CEN25FA348 
  • Date & Time: August 27, 2025, 20:57 Local 
  • Registration: N3806Y 
  • Aircraft: Cessna 210D 
  • Injuries: 2 Fatal 
  • Flight Conducted Under: Part 91: General aviation - Personal

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

https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?NNumberTxt=N3806Y

On August 27, 2025, about 20:57 central daylight time, a Cessna 210D, N3806Y was destroyed when it was involved in an accident near Kearney, Nebraska. Both pilots were fatally injured. The flight was operated under the provisions of Title 14 Code of Federal Regulations Part 91 as a personal flight.

The airplane was the subject of an alert notice (ALNOT) when radar coverage was lost with the airplane, and it was reported overdue at its destination airport. The airplane was discovered in a corn field on the morning of August 28, 2025, about 5 nautical miles north of Kearney Regional Airport (EAR), Kearney, Nebraska.

The airplane departed Bakko Aviation Airport (MN71), Glenwood, Minnesota about 18:45 and was enroute to Onion Crest Airpark (43NE), Riverdale, Nebraska. The flight diverted to EAR due to low ceilings and the lack of an instrument approach into 43NE. Minneapolis Air Route Traffic Control Center provided air traffic control services and cleared N3806Y for the RNAV (GPS) Runway 18 approach into EAR then switched N3806Y to EAR common traffic advisory frequency,123.0. Minneapolis ARTCC had no further communication with N3806Y.

The airplane impacted an upsloping mature corn field on a heading of about 225°. Cornstalks were cut at 45° angles just prior to the initial impact site. The debris field from initial impact to where the main wreckage came to rest was 154 ft long and 23 ft at the widest point.

The right wing tip was at the beginning of the debris field followed by the nose gear, right wing strut, left wing tip, a portion of the right horizontal stabilizer, left door, right door, left wing, propeller (still attached at the hub), and right landing gear. At the end of the debris field was the main wreckage with a detached right wing lying next to it. The main wreckage came to rest on a heading of about 330°.

The airplane was retained for further examination.

Airbus A319-112, C-GSJB, incident occurred on August 14, 2025, at Nashville International Airport (BNA/KBNA), Nashville, Tennessee

  • Location: Nashville, TN 
  • Incident Number: DCA25LA291 
  • Date & Time: August 14, 2025, 17:24 Local 
  • Registration: C-GSJB 
  • Aircraft: Airbus A319 Injuries: 90 None 
  • Flight Conducted Under: Part 129: Foreign

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

On August 14, 2025, about 1724 central daylight time (CDT), Air Canada Rouge flight ROU1717, an Airbus A319 airplane, registration C-GSJB, touched down short of runway 20L while landing at the Nashville International airport (BNA), Nashville, TN. There were no injuries to the ninety-three occupants onboard. A postincident inspection revealed that the airplane sustained minor damage. The regularly scheduled international passenger flight was operating under the provisions of Title 14 Code of Federal Regulations Part 129 from Lester B Pearson International airport (CYYZ), Toronto, Ontario, Canada to BNA,

As part of the investigative process, the NTSB invited qualified parties to participate in the investigation, including the Federal Aviation Administration (FAA). In accordance with the provisions of Annex 13 to the Convention on International Civil Aviation, an Accredited Representative from the Transportation Safety Board of Canada (TSB), the State of Registry for the airplane, with Air Canada as their technical advisor. And an Accredited Representative from the Bureau of Enquiry and Analysis for Civil Aviation Safety (BEA), the State of Design, with Airbus and European Union Aviation Safety Agency (EASA) as their technical advisors. 

The parties were organized into specialized investigative groups, each led by an NTSB group chair. These groups focused on the areas of Operations, Air Traffic Control (ATC), Meteorology, Cockpit Voice Recorder and Flight Data Recorder

HISTORY OF FLIGHT

The flight crew consisted of a Line Indoctrination Training Captain, seated in the right seat, and serving as the pilot monitoring (PM), and a captain candidate, seated in the left seat, serving as the pilot flying (PF).

The crew reported that ATC initially instructed them to expect a visual approach to runway 20L. However, due to rain over the airport, ATC later amended the clearance to the RNAV (GPS) Y 20L approach (see figure 1). The flight was cleared to the initial approach fix (IAF) WAYLN, then given radar vectors and subsequently cleared for the approach.

The airplane was configured for landing at approximately 1,100 feet and met the operator’s stabilized approach criteria at both 1,000 and 500 feet; however, the stable call at 500 feet was missed by the PM. At the decision altitude (DA), the autopilot was disconnected. Around 200 feet above ground level (AGL), the crew encountered heavy rain, and the PF requested activation of the windshield wipers.

Shortly after, the PF stated he had “lost the runway” but still believed the runway environment was visible. He asked whether a go-around should be initiated. The PM, who could see the runway environment—albeit distorted by rain—and believed the aircraft was on the glide path, responded that they were good to continue.

At 20 to 30 feet radio altitude, the crew retarded the thrust levers to idle. About the same time, the PF was startled to see the runway threshold lights directly ahead of the aircraft’s nose. The crew perceived that the airplane touched down on the blast pad, a paved surface preceding the runway threshold. The remainder of the landing rollout and taxi were uneventful.

Airport video surveillance captured the incident sequence and showed the airplane as it touched down short of the runway. Following the initial touchdown, the airplane rolled onto the pavement and impacted a runway threshold light.

A post-incident inspection by airport personnel revealed that the left main landing gear contacted an airport service road approximately 420 feet short of the runway threshold.

The right main landing gear touched down approximately 52 feet short of the paved surface, which was about 430 feet short of the runway threshold (see figure 2). 

A post flight inspection by maintenance personnel revealed mud on the airplane’s empennage and minor damage to one of the airplane’s tires.

The investigation continues.

Airbus A330-941, N422DZ, turbulence encounter accident occurred on July 30, 2025, near Creston, Wyoming

  • Location: Creston, WY 
  • Accident Number: DCA25LA276 
  • Date & Time: July 30, 2025, 17:23 Local 
  • Registration: N422DZ 
  • Aircraft: Airbus A330 
  • Injuries: 2 Serious, 5 Minor, 234 None 
  • Flight Conducted Under: Part 121: Air carrier - Scheduled

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

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

On July 30, 2025, at 1723 mountain daylight time, Delta Air Lines flight 56, an Airbus A330-941, encountered severe turbulence while in cruise flight at an altitude of 37,000 ft near Creston, Wyoming. After determining that injuries had occurred, the flight crew diverted to Minneapolis-St Paul International airport (MSP), Minneapolis, Minnesota. After landing, 24 of the 246 passengers were evaluated by emergency medical technicians, with 18 transported to local hospitals for additional assessment; information regarding their conditions is currently unavailable.  Of the 10 cabin crew members, 2 sustained serious injuries, 5 sustained minor injuries, and 3 were uninjured. None of the 3 flight crew members were injured. The airplane sustained minor damage to interior components. The airplane was operating under the provisions of Title 14 Code of Federal Regulations (CFR) Part 121 as a scheduled international passenger flight from Salt Lake City International Airport (KSLC), Salt Lake City, Utah, to Amsterdam Airport Schiphol (EHAM) in Haarlemmermeer, Netherlands.

According to the flight crew, prior to departure they had discussed the conditions along the route, noting that they could expect some weather during the climb, and that turbulence was predicted over the mountains east of SLC. They anticipated deviating after crossing the mountains. The departure was relatively smooth, until they reached the Wasatch Mountains, where they experienced some turbulence. As they passed through flight level (FL) 300, the ride had smoothed out enough to allow the cabin crew to begin service. At FL350, where they remained for about 5 minutes due to traffic, they noted that the turbulence predicted on their electronic flight bag weather application was “in the green” and they had observed only light cirrus clouds. About this time the captain turned off the seatbelt sign. As the climb continued to FL370, they noticed some weather buildups and requested a right deviation from air traffic control (ATC). ATC suggested a left turn to a heading of 350°. The crew assessed that heading would keep them above the cloud deck, upwind of weather buildups, and they had not heard any adverse ride reports. After scanning the horizon and the weather radar, noting that the only returns of concern were 40-50 miles away, they accepted the left turn.

After completing the turn, the airplane encountered an overspeed event (exceeding the maximum operating speed by about 15-20 knots), along with an updraft that carried it to FL380 over the course of about 20 seconds, during which the autopilot disengaged. Shortly thereafter, the airplane descended ‘rapidly’ to FL355, and a climb/descent cycle repeated about three times over a two- to three-minute period, which resulted in the airplane re-entering a cloud layer. The first officer who was the pilot flying (PF), initiated the All Attitude Upset Recovery Strategy procedure at least once during this time, before having recovered and re-engaged the autopilot

A review of preliminary flight data recorder information revealed that the upset lasted approximately 2.5 minutes. During this time, the vertical acceleration oscillated, reaching a maximum positive peak of about 1.75 g and a minimum negative peak of about -0.5 g. The pitch angle also oscillated, ranging from a low of about 5° nose down to a high of about 10° nose up. Roll angle variations included a maximum of about 40° left wing down and about 5° right wing down. Computed airspeed fluctuated as well, with peaks ranging from about 230 knots to about 290 knots. 

A convective Significant Meteorological Information (SIGMET) was in effect for the time and area of the accident. It warned of thunderstorms moving from the southwest at 10 knots, with cloud tops above FL450. Figure 1 shows the airplane’s ground track and radar imagery from the National Weather Service at the time of the accident.

After the event, the captain divided cockpit duties. The PF continued to fly and manage ATC communications, while the captain coordinated with the cabin crew and dispatch. The relief first officer, who had been in the crew rest bunk, walked through the cabin to assess injuries and gather information. A passenger who was a physician assistant aided the cabin crew with triage. After the relief first officer returned to the flight deck, the crew planned for a diversion and declared an emergency with ATC. They elected to divert to MSP to avoid weather and reviewed overweight landing performance data and suitable runways. After landing, they noticed that the right main landing gear brakes were hot and notified ground personnel. They taxied to the gate and were met by airport rescue firefighting, medical, and maintenance personnel.

As part of the investigative process, the NTSB invited the qualified parties to participate in the investigation. These included the Federal Aviation Administration, Delta Air Lines, the Air Line Pilots Association, and the Professional Airline Flight Controllers Association. In accordance with the provisions of Annex 13 to the Convention on International Civil Aviation, an Accredited Representative from the Bureau d'Enquêtes et d'Analyses of France, the State of Manufacture for the airplane, was appointed to support the investigation with Airbus and the European Union Aviation Safety Agency as their technical advisors.

The flight data and cockpit voice recorder data were sent to the NTSB Vehicle Recorder Laboratory in Washington, D.C. The following NTSB specialists were assigned to investigate the accident: Cockpit Voice Recorder, Flight Data Recorder, Meteorology, Air Traffic Control, and Operational Factors. 

The investigation is ongoing.

De Havilland Canada DHC-6-300 Twin Otter, N189GC, accident occurred on August 9, 2025, at Grand Canyon Bar Ten Airstrip (1Z1), Whitmore, Arizona

  • Location: Whitmore, AZ 
  • Accident Number: WPR25LA248 
  • Date & Time: August 9, 2025, 12:40 Local 
  • Registration: N189GC 
  • Aircraft: De Havilland DHC-6-300 
  • Injuries: 6 Minor, 10 None 
  • Flight Conducted Under: Part 135: Air taxi & commuter - Non-scheduled

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

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

On August 9, 2025, about 1240 Pacific daylight time, a De Havilland DHC-6-300, N189GC, was substantially damaged when it was involved in an accident near Whitmore, Arizona. Six passengers sustained minor injuries, and the captain, first officer and remaining eight passengers were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 135 on-demand air taxi flight.

The flight departed from Boulder City Municipal Airport (BVU), Boulder City, Nevada, to transport the passengers to Grand Canyon Bar Ten Airstrip (1Z1), Whitmore, Arizona, where they were scheduled to begin a river tour. The airplane was the second in a group of four, that were due to arrive at about the same general time. The first airplane to depart was a Cessna 208 (Caravan), with the remaining three airplanes all similarly equipped DHC-6-300’s.

1Z1 is a remote airstrip, located at an elevation of 4,100 ft mean sea level (msl), within a 2 ½ mile wide valley, surrounded by steep rising terrain. It had a single, 4,600 ft long by 40 ft wide north/south oriented runway, 4,000 ft of which was composed of a 33 ft-wide asphalt chip seal surface. The airstrip did not have a weather reporting station, and the crew checked area weather before departure, which indicated gusting winds out of the west. The pre-flight preparations, boarding, and enroute cruise segment of the flight were uneventful, with the first officer flying the airplane. During the final stages of cruise flight, the crew checked the weather at Grand Canyon West airport (1G4) (38 miles southwest of 1Z1), which indicated wind from 270° at 13 knots, gusting to 22 knots. The crew consulted with the Caravan pilot, who had just departed the area after dropping off passengers, and he stated the wind conditions were strong, variable, and gusting, but favoring runway 16.

The crew discussed the arrival and landing procedures and decided that based on prevailing wind conditions and terrain clearance should they need to perform a go-around, runway 16 was the most prudent choice. They then configured the airplane for descent, with the captain assuming the role of pilot flying.

The captain reported that the final approach was stable, on speed, on centerline, and although gusting winds were causing changes in airspeed, they were not enough to require large changes in engine power. Due to the westerly winds, the captain was maintaining a crab angle while the airplane was on final, and as they got closer to the runway, she could see the windsocks were “pegged” and indicating winds directly out of the west.

The captain reported that shortly after touchdown, which was between 500 and 1,000 ft beyond the threshold, she was able to maintain directional control with right aileron and left rudder control input, and the airplane tracked down the runway centerline while she retarded the engine power levers to the zero-thrust position. As they approached the runway midpoint, the captain described a sensation that felt as if the airplane was being “pushed”. She maintained full left rudder input and began to release the right aileron control pressure. The airplane then departed the runway surface to the right and entered the dirt edge of the paved surface. She was still able to maintain the runway heading but could not direct the airplane back onto the paved surface.

The gravel area became bumpier, and as they approached a ditch, the captain applied aft control yoke to raise the nose, and prevent the nose gear from digging in. Ground disruptions and runway markings were consistent with the airplane swerving left as the terrain rose. The left wingtip then struck the runway, and the airplane then began a sharp right turn, about the time the captain reported applying brakes and retarding the engine controls further.

The airplane then struck a deep ditch, just beyond, and to the right of the departure end of the runway, where it came to rest upright. The crew secured the airplane while evacuating the passengers. The airplane sustained substantial damage to the left wing, and entire forward fuselage structure during the accident sequence.

de Havilland Canada DHC-6 Twin Otter 300, N344CS, accident occurred on August 11, 2025, at San Clemente Island Naval Auxiliary Landing Field (NUC/KNUC), San Clemente Island, California

  • Location: San Celmente, CA 
  • Accident Number: WPR25LA250 
  • Date & Time: August 11, 2025, 11:30 Local 
  • Registration: N344CS 
  • Aircraft: De Havilland DHC-6-300 
  • Injuries: 18 None 
  • Flight Conducted Under: Part 135: Air taxi & commuter - Non-scheduled
https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/200764/pdf

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

On August 11, 2025, at 1130 Pacific daylight time, a De Havilland DHC-6-300, N344CS, was substantially damaged when it was involved in an accident at San Clemente Island, California. The 2 pilots and 16 passengers were not injured. The airplane was operated as a Code of Federal Regulations Title 14 Part 135 on-demand air taxi flight.

According to the operator, the flight was uneventful until approximately 10 seconds prior to touchdown. About 15-20 ft above ground level and an airspeed of about 95 knots, the airplane began to yaw hard to the left and pitched nose down. The left wing struck the runway and the first officer, who was the pilot flying, banked to the right and the airplane touched down hard onto the runway. Upon touchdown, the captain took control of the airplane and tried to maintain directional control by using nosewheel steering, however, the airplane turned left and exited the runway surface. The airplane came to rest upright, the flight crew shut the engines down, and the occupants egressed from the airplane. About 1/3 of the outboard portion of the left wing and about 1/2 of the left aileron had separated.

Postaccident examination of the airplane revealed the No. 1 (left) engine propeller beta ring was fragmented, with multiple pieces of the beta ring contained within the engine cowling. The airplane and the recovered beta ring fragments were retained for further examination.

Jabiru J230-D, N784J, accident occurred on August 2, 2025, near Oak Island, North Carolina

  • Location: Oak Island, NC
  • Accident Number: ERA25LA289 
  • Date & Time: August 2, 2025, 19:25 Local 
  • Registration: N784J 
  • Aircraft: JABIRU AIRCRAFT PTY LTD J230- D 
  • Injuries: 1 Minor 
  • Flight Conducted Under: Part 91: General aviation - Personal

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

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

On August 2, 2025, about 1925 eastern daylight time, a Jabiru Aircraft Pty Ltd J-230-D, N784J, was substantially damaged when it was involved in an accident near Oak Island, North Carolina. The private pilot received minor injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

According to the pilot, the airplane had recently undergone lengthy maintenance, and this was the second flight after completion of the repairs. The pilot reported that there were no anomalies noted during the preflight inspection and that the airplane operated normally during startup, taxi, engine runup, and takeoff. During the climb out, the pilot reported the airplane developed momentary “blips” in reduction of engine power that would last less than a second. The pilot stated that he had experienced these momentary drops in power before, but they had always stopped after leveling off the airplane. The pilot leveled off the airplane; however, the momentary power drops continued, and the pilot decided to return to the airport. While over the water, the pilot turned onto the final approach leg to the runway, and the engine began to lose power. The pilot attempted to restore engine power by adjusting throttle settings, turning on the fuel pump, as well as the carburetor heat; however, the engine continued to lose power. The pilot reported that while at 1,400 ft mean sea level and still over the water, he realized he would not reach the airport and that the nearby beach was too crowded with people to make a safe emergency landing. The pilot elected to ditch the airplane into the water near the beach. While lining up for the forced ditching, the engine completely lost power, and the propeller stopped rotating. During the forced ditching, the airplane’s main landing gear impacted the water first, and shortly after, the airplane nosed over into the water. After impact, the airplane began to sink, and the pilot was extricated through the broken windshield by nearby first responders. A postaccident examination of the wreckage revealed the airplane sustained substantial damage to the fuselage and both wings. 

The wreckage was retained for further examination.