Loss of control in flight: Porto Risen 915iSV, N2442, fatal accident occurred on July 28, 2023, near Dawson Community Airport (GDV/KGDV), Glendive, Montana

• Location: Glendive, Montana
• Accident Number: WPR23FA286 
• Date & Time: July 28, 2023, 14:10 Local 
• Registration: N2442 Aircraft: RISEN 915 iS 
• Aircraft Damage: Destroyed 
• Defining Event: Loss of control in flight 
• Injuries: 1 Fatal Flight Conducted Under: Part 91: General aviation - Personal 

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

https://data.ntsb.gov/Docket?ProjectID=192733

On July 28, 2023, about 1410 mountain daylight time, an experimental amateur-built Risen 915 iS, N2442, was destroyed when it was involved in an accident near Glendive, Montana. The pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

The pilot was conducting a personal cross-country flight in his experimental, amateur-built airplane, and the accident occurred on day nine of the flight.

The airport manager at the departure airport reported that he assisted the pilot with fueling the airplane with about 15 gallons of fuel. He reported that the engine sounded like it was at full power during takeoff; however, the airplane appeared to climb slower than he expected to about 300-400 ft above ground level (agl). The main landing gear were up but the nose gear appeared to be partially extended and had not completely retracted. He watched the airplane maintain a low altitude at a low airspeed until he observed a “wing drop,” and the airplane subsequently made two turns in a “flat spin” with about a 45-60° nose-down attitude as it descended behind terrain.

Postaccident examination revealed no anomalies with the airframe or engine that would have precluded normal operation. Damage signatures and witness accounts indicated that the engine was producing power at the time of the accident. The debris path was consistent with a steep impact angle.

Evidence suggests that the pilot failed to maintain airspeed during the climb, which resulted in an exceedance of the airplane’s critical angle of attack and a subsequent aerodynamic stall/spin. The pilot had texted the aircraft kit manufacturer that he was having problems with the engine overheating; however, had made modifications to the cooling system that appeared to be successful, according to his texts with the owner of a similar airplane. The airplane’s emergency parachute was found deployed at the accident site. Since the parachute was unfurled, it is likely that the parachute deployment was the result of ground contact.

Evidence suggests that the pilot failed to maintain airspeed during the climb, which resulted in an exceedance of the airplane’s critical angle of attack and a subsequent aerodynamic stall/spin. The nose landing gear did not retract fully after takeoff. Although this may have created a distraction for the pilot that resulted in a loss of airspeed while he was troubleshooting the nose landing gear retraction, the investigation was not able to determine the reason for the pilot’s loss of control.

- Probable Cause: The pilot’s failure to maintain airspeed, which resulted in an exceedance of the airplane’s critical angle of attack and an aerodynamic stall/spin.

Loss of control in flight: Steen Skybolt, N202GM, fatal accident occurred on June 8, 2023, near Rio Vista Municipal Airport (O88), Rio Vista, California

• Location: Rio Vista, California 
• Accident Number: WPR23FA219 
• Date & Time: June 8, 2023, 11:24 Local 
• Registration: N202GM 
• Aircraft: Steen Skybolt 
• Aircraft Damage: Substantial 
• Defining Event: Loss of control in flight 
• Injuries: 2 Fatal 
• Flight Conducted Under: Part 91: General aviation - Personal

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

https://data.ntsb.gov/Docket?ProjectID=192338

On June 08, 2023, about 1124 Pacific daylight time, an experimental, amateur-built Steen Skybolt, N202GM, was substantially damaged when it was involved in an accident in Rio Vista, California. The two pilots were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

The two pilots, both of whom were owners of the airplane, were returning to their home airport. Radar track information correlated to the accident airplane was consistent with the airplane departing and continuing southwest toward the destination airport before it turned south toward the accident airport. The airplane joined the left downwind leg of the traffic pattern (right traffic was specified for this runway), and after turning onto a base leg, made a sharp left turn and spiraled toward terrain, consistent with an aerodynamic stall. 

A witness reported hearing one of the pilots transmit "engine out" or "simulated engine-out"; however, the airport’s common traffic advisory frequency was not recorded, and the content of this transmission could not be confirmed. The witness also stated that the airplane crossed over the airport to join the traffic pattern and that the engine sounded normal.

Examination of the engine revealed continuity of the valve and drive train and compression in each of the cylinders. Removal of the cylinders revealed light scratches and corrosion of the combustion chambers and barrels. The intake and exhaust valves were intact and undamaged; the No. 3 exhaust valve was consistent in appearance with exposure to high temperatures. Severe spalling was noted on the faces of the camshaft intake lifters and several exhaust lifters; the camshaft lobes did not appear rounded. Although visual examination of the oil filter media did not reveal any metallic debris, microscopic inspection revealed metal particles, and there were several small pieces of metal in the oil suction screen. It is unlikely that any of these findings would result in a total loss of engine power. There was evidence of fuel in the fuel system.

A video recorded about five months before the accident was recovered from an iPad owned by one of the pilots. The video indicated that the airplane had recently exhibited problems with the trim system leading to the airplane oscillating and “throwing the elevator up and down.” A modification was made to the trim system sometime after the pilots purchased the airplane about seven months before the accident; however, there was no record of this modification in the available maintenance records. At the accident site, the right trim tab was sheared off at the piano hinge and came to rest under the elevator, yet remained connected to the bellcranks and was continuous to the fuselage bellcrank. When attempting to move to nose-down trim, the control cable could not move to that position because the cable would bind on the sleeve and not move over the attach fitting. Whether the modified trim system caused a problem inflight and what effect it may have had on the control surface and airplane’s controllability could not be determined.

The circumstances of the pilots’ decision to land at the accident airport could not be determined; however, based on the available information, it is likely that they exceeded the airplane’s critical angle of attack while maneuvering for landing, which resulted in an aerodynamic stall and loss of control at an altitude too low for recovery.

- Probable Cause: The pilots’ exceedance of the airplane's critical angle of attack while maneuvering to land, which resulted in an aerodynamic stall and subsequent loss of control.

Cessna 414, N414BA, fatal accident occurred on June 8, 2025, near San Diego, California

• Location: San Diego, CA 
• Accident Number: WPR25FA169 
• Date & Time: June 8, 2025, 12:30 Local 
• Registration: N414BA 
• Aircraft: Cessna 414 
• Injuries: 6 Fatal 
• Flight Conducted Under: Part 91: General aviation - Business

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

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

On June 08, 2025, at 1230 Pacific daylight time, a Cessna 414A, N414BA, was substantially damaged when it was involved in an accident in San Diego, California. The pilot and five passengers were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations (CFR) Part 91 business flight.

The day before the accident, the pilot and passengers flew from Phoenix, Arizona, to San Diego. The accident flight was intended to return to Phoenix.

The exact radio communication times could not be confirmed for the accident flight. The pilot received an instrument flight rules (IFR) clearance and was issued the BRDR7 (Border 7) departure. The published BRDR7 Standard Instrument Departure (SID) with a takeoff from runway 27 consisted of a “climb on heading 278° until PYG [Poggi VORTAC] 19 DME, then left turn on heading 123° to intercept PGY VPRTAC R-260 and R-069 to BROWS INT.”

After departing from runway 27, the pilot made a radio communication to SOCAL departure that he was at 1,600 ft, and shortly thereafter, the controller instructed him to make a left, 180° turn. The airplane began a gradual turn, and after climbing to about 2,000 ft, it made a steep descent to 200 ft. The controller issued the pilot a low altitude alert and instructed him to climb to 4,000 ft immediately to which the pilot replied by repeating the instructions. The controller then asked if he needed any assistance and queried him as to the nature of the problem. The pilot stated that he was “struggling” to try to maintain the airplane on a heading and climb. In response, the controller told him of the closest airport that was one mile away and asked him if he could see it. The pilot responded that he did not see the airport and made a series of erratic maneuvers before making several mayday calls (see figure 1 below).

A video captured the airplane descending before climbing back into the cloud layer, where it subsequently disappeared from view (see figure 2 below).

A police helicopter was ten miles east of the accident site when the flight crew received a request to search for any signs of an airplane impacting the water. In a post-accident interview, the helicopter pilot stated that he estimated the cloud bases at roughly 800 feet in numerous areas, with the highest layer near 1,600 ft (although a majority of the clouds were lower). Upon reaching the search area, he located an oil slick approximately two miles offshore.

The accident airplane’s regular pilot, who was also a friend of the accident pilot, stated that he had flown about 50 hours with the accident pilot in the airplane. He stated that two days prior to the accident, the accident pilot flew solo up to Springerville, Arizona. The friend then boarded the airplane and acted as a safety pilot for the accident pilot as he conducted four approaches in simulated instrument meteorological conditions. He recalled that the pilot used a Garmin 430 and iPad with ForeFlight for navigation and was accustomed to hand-flying the airplane, which had no autopilot or glass cockpit. He noted that the pilot had expressed some nervousness about the busy southern California airspace, but appeared to be proficient during their review of the San Diego departure procedure.

Cirrus SR22T GTS G3 carbon, N5656M, fatal accident occurred on July 7, 2025, near Raleigh Executive Jetport (KTTA), Sanford, North Carolina

This post is outdated, for the one with the NTSB prelim, check 

https://adamreport.blogspot.com/2025/07/cirrus-sr22t-gts-g3-carbon-n5656m-fatal.html

This is preliminary information, subject to change, and may contain errors. Any errors in this report will be corrected when the final report has been completed.

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

- History of Flight:

On July 7, 2025, at about 1330 local time, a privately-registered Cirrus SR22T GTS G3 carbon, N5656M, was destroyed when it impacted terrain while on approach to land at Raleigh Executive Jetport (KTTA), Sanford, North Carolina. The private pilot and three passengers sustained fatal injuries. The aircraft was registered to, and being operated by the pilot on a cross-country personal flight, which originated from Merritt Island Airport (COI/KCOI), Merritt Island, Florida, at about 1103 LT.

According to air traffic control communications, shortly after takeoff, the pilot reported that he was going to lose radio frequency and radio contact. The pilot repeated the message several times, and stated that it was probably caused by an "electrical problem". The airplane continued to fly over the coast and towards the destination airport.

According to radio communications from the TTA tower, the local controller reported that the Cirrus was 3 miles south of the airport and on approach to runway 03 with no communication and a potential engine failure. The controller asked other aircraft in the vicinity if they could see it. Later, the Cirrus was discovered south of the airport.

According to the NTSB, when the aircraft was about 5-6 miles from the airport, the pilot advised a local fixed-base operator about a loss of communications and navigational equipment, shortly after they advised the fixed-base operator that they had engine issues.

- Pilot Info:
The pilot, aged 35, held a private pilot certificate (with a most recent issue date of January 22, 2024) with a rating for airplane single engine land. His third class FAA medical was issued on November 2023.

According to the NTSB, the pilot's logbooks were located, but they did not contain all information (which is normal).

- Aircraft Info:
The accident aircraft, MSN 0341, was manufactured in 2012. It was powered by a Continental TSIO-550-K engine.

According to a sale listing of the aircraft, it did not have any previous damage history.

The aircraft was registered to the accident pilot on January 17, 2024.

- Wreckage and Impact Information:

The airplane impacted an open field about 1 mile south of the airport. The initial impact was identified by a small area of grass that had been pushed down and proceeded to the main wreckage. Several broken pieces from the engine, engine cowling, and front section were located in the small path leading to the main wreckage. Also located was the engine itself, which was impact damaged and separated from the airframe. The main wreckage consisted of the fuselage, both wings, and tail, which were confined to the same area. The fuselage sustained extensive impact damage. There was no post crash fire. Both wings remained attached to the airframe, and both exhibited damage to the leading edge portions. The outer right wing was impact damaged and separated. The main landing gear remained attached to the bottom of the fuselage. The tail section sustained impact damage and was separated from the airframe.

The Cirrus Airframe Parachute System (CAPS) was not deployed.

- Additional Information:

NONE

- Weather:

METAR KTTA 071655Z AUTO 24006KT 10SM CLR 32/23 A3003 RMK AO2 T03170225

METAR KTTA 071715Z AUTO 23007KT 10SM CLR 32/23 A3003 RMK AO2 T03190225

METAR KTTA 071725Z AUTO 25007KT 10SM CLR 32/22 A3003 RMK AO2 T03200224

METAR KTTA 071735Z AUTO 26006KT 10SM CLR 32/23 A3002 RMK AO2 T03210225

METAR KTTA 071755Z AUTO 22005KT 10SM SCT043 33/22 A3003 RMK AO2 T03250221 10325 20229

Miscellaneous/other: Capella Aircraft FW1C50, N556CF, accident occurred on December 15, 2024, at Gimlin Airport (18MO), Ozark, Missouri

• Location: Ozark, Missouri 
• Accident Number: CEN25LA062 
• Date & Time: December 15, 2024, 11:20 Local 
• Registration: N556CF 
• Aircraft: CAPELLA AIRCRAFT CORP FW1C50 
• Aircraft Damage: Substantial 
• Defining Event: Miscellaneous/other 
• Injuries: 1 Minor 
• Flight Conducted Under: Part 91: General aviation - Personal 

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

https://data.ntsb.gov/Docket?ProjectID=199442

The pilot reported that he was unfamiliar with the single seat amateur-built airplane and his intent was to perform high speed taxi testing of the airplane. He stated that he made a highspeed taxi to the south on runway 18 and then proceeded to make another high-speed taxi in the opposite direction on runway 36. During the high-speed taxi on runway 36, wind from the southeast picked up the left wing, the airplane inadvertently became airborne, and the airplane drifted to the right. The airplane was heading toward trees and the pilot applied full throttle to clear the trees but was unable to maintain control of the airplane. The airplane struck the ground, and the nose and right main landing gear separated. The right wing incurred substantial damage. The pilot reported that there were no mechanical malfunctions or failures of the airplane that would have precluded normal operations.

- Probable Cause: The pilot’s failure to maintain aircraft control during high-speed taxi.

Fuel exhaustion: Bell 206B JetRanger II, N5QV, accident on March 21, 2025, at Atlanta-DeKalb-Peachtree Airport (PDK/KPDK), Chamblee, Georgia

• Location: Chamblee, Georgia
• Accident Number: ERA25LA156 
• Date & Time: March 21, 2025, 15:53 Local 
• Registration: N5QV 
• Aircraft: Bell 206 
• Aircraft Damage: Substantial
• Defining Event: Fuel exhaustion 
• Injuries: 1 Serious, 1 Minor 
• Flight Conducted Under: Part 91: General aviation - Aerial observation

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

https://data.ntsb.gov/Docket?ProjectID=199910

The pilot of the electronic news gathering helicopter reported that he departed the airport on a preplanned flight to obtain video footage at four locations. After filming the four locations, but before returning to the airport, the pilot was contacted via radio about filming a fifth location due to breaking news. While over the fifth location, the cockpit fuel pump caution light illuminated, and the pilot noticed a low fuel level but elected to return to the airport rather than land at a nearby city helipad. While over the airport ramp area at 100 to 150 ft above ground level, the engine “hiccupped” and then lost all power. The pilot attempted an autorotation, but the helicopter landed hard on the ramp area. The pilot added that there were no preimpact mechanical malfunctions with the helicopter. Examination of the wreckage by a Federal Aviation Administration inspector revealed substantial damage to the fuselage. The inspector also noted that the fuel tanks were absent of fuel and the cockpit fuel gauge needle was below “E.”

- Probable Cause: The pilot’s inadequate fuel planning, which resulted in a total loss of engine power during approach due to fuel exhaustion.

Low altitude operation/event: Enstrom 280FX Shark, N402TA, accident occurred on March 15, 2025, near Waterford, California

• Location: Waterford, California 
• Accident Number: WPR25LA112 
• Date & Time: March 15, 2025, 11:00 Local 
• Registration: N402TA 
• Aircraft: Enstrom 280FX 
• Aircraft Damage: Destroyed 
• Defining Event: Low altitude operation/event 
• Injuries: 1 Serious, 1 Minor 
• Flight Conducted Under: Part 91: General aviation - Personal

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

https://data.ntsb.gov/Docket?ProjectID=199873

A witness video showed the helicopter flying very low over a lake before it impacted the water. During postaccident interviews with news outlets, the pilot stated he and a passenger were flying the helicopter low over clear water, when his “depth perception got a little off”, and he drove the helicopter into the water. The helicopter fuselage, tail boom, and main rotor blades were substantially damaged. The pilot did not complete a NTSB Form 6120.1 Accident/Incident Report.

- Probable Cause: The pilot’s failure to maintain clearance from water while operating at a low altitude.