Thursday, June 05, 2025

Aerokopter AK 1-3 Sanka, N163AK, fatal accident occurred on May 17, 2025, near Prineville Municipal Airport (S39), Prineville, Oregon

  • Location: Prineville, OR 
  • Accident Number: WPR25FA156 
  • Date & Time: May 17, 2025, 11:34 Local 
  • Registration: N163AK 
  • Aircraft: DB AEROCOPTER LTD AK1-3 
  • Injuries: 1 Fatal, 1 Serious 
  • Flight Conducted Under: Part 91: General aviation - Instructional

https://registry.faa.gov/aircraftinquiry/Search/NNumberResult?NNumbertxt=N163AK

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

On May 17, 2025, about 1134 pacific daylight time, a DB Aerocopter Ltd., AK1-3, N163AK, sustained substantial damage when it was involved in an accident near Prineville, Oregon. The private pilot undergoing instruction was fatally injured, and the flight instructor sustained serious injuries. The helicopter was operated as a Title 14 Code of Federal Regulations part 91 instructional flight.


The helicopter was not equipped with an ADS-B transponder, and radar coverage was not available in the area, however the initial departure along with segments of the accident sequence were captured by multiple security cameras in the vicinity of the airport.


A camera operated by Prineville Municipal Airport (S39), Prineville, Oregon, indicated that the helicopter took off from runway 29, about 1036. For the next hour it performed a series of takeoffs, landings and low hover maneuvers while remaining in the right traffic pattern for runway 29, with the last takeoff occurring at 1123.


A north-facing camera located at a business about 1,800 ft northeast of runway 29 midfield, captured the helicopter passing from left to right at 1134. It then began a rapid descent while in a slight nose-down attitude. The nose then pitched up, and the helicopter struck the ground, accompanied by a large dust cloud (figure 1). White fragments could then be seen being ejected from the initial impact point in an arcing trajectory to the east.

A witness, who was travelling west in her automobile along a road north of the airport observed the helicopter pass in front of her from right to left. She said the helicopter was travelling slower than she would have expected, and it then rapidly began to descend, striking the ground in a field to her left. She stated that the helicopter was not trailing smoke or vapor prior to the accident, and this observation was corroborated by the video footage.


The helicopter came to rest in a field, about 4,000 ft north of the approach end of runway 29, in an area that corresponded to the midfield downwind segment of the right traffic pattern.


The first identified point of impact was comprised of longitudinal slash marks in the soil, followed by a ground disruption that contained fragments of the tail rotor blades. Debris continued on a heading of about 120°, to a 15-ft-long, and 6-ft-wide soil disruption that matched to the general outline of the helicopter. The disruption contained the complete main skid assembly, which had been compressed such that the skids were level with the upper frame.


The debris field, which contained fragments of windshield and cabin contents, continued on the same heading to the main cabin about 60 ft downrange. At the time of examination, the helicopter was sitting upright, but according to first responders it was lying on its right side upon their arrival. The cabin was generally intact, with the main transmission and engine remaining attached to the airframe. Two main rotor blades were still attached to the head of the transmission mast, with the third located about 20 ft south.


The tail rotor gearbox assembly was located a further 170 ft downrange, with three sections of the tail tailcone located a further 100 ft northeast. The furthest component in the debris field was the tailrotor driveshaft, which was found 410 ft beyond the initial impact point. (figure 2)


Weather at the time of the accident included light rain with wind from 280° at 7 knots, gusting to 14 knots.

Van's RV-10, N626PB, fatal accident occurred on May 3, 2025, near Simi Valley, California


  • Location: Simi Valley, CA
  • Accident Number: WPR25FA147
  • Date & Time: May 3, 2025, 13:50 Local
  • Registration: N626PB
  • Aircraft: PAUL BERKOVITZ VANS RV-10
  • Injuries: 2 Fatal
  • Flight Conducted Under: Part 91: General aviation - Personal

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

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

On May 3, 2025, about 1350 Pacific daylight time, an experimental amateur-built Van’s RV-10, N626PB, was destroyed when it was involved in an accident near Simi Valley, California. The pilot and passenger were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.


The airplane departed General Wm J. Fox Airfield (WJF), Lancaster, California about 1319, on an instrument flight rules flight plan with an intended destination of Camarillo Airport (CMA), Camarillo, California. Recorded communication between the pilot and Southern California Approach Control revealed that about 1335, the pilot was instructed by the controller to proceed direct SESPE (initial approach fix for the RNAV-Z runway 26 instrument approach) and join final. At about 1343, the controller instructed the pilot to descend to 4,000 ft mean sea level (msl) and to contact Point Mugu Approach. 


Preliminary ADS-B data showed that at 1343:50 the airplane crossed SESPE at an altitude of about 5,000 ft msl, before a left turn to a southerly heading was made. The airplane continued a southerly heading while descending to 4,195 ft msl at 1345:33. Shortly after, multiple heading deviations to the right and left were observed throughout the following 1 minute, 5 seconds. At 1346:49, the data showed the airplane began a right turn, while about 1-mile north of JUREX (the RNAV-Z runway 26 intermediate fix) at an altitude of 3,750 ft msl. The airplane continued a right descending turn when ADS-B contact was lost at 1347:02. ADS-B contact was reestablished at 1347:21, with the airplane flying on a northerly heading at an altitude of 2,175 ft msl. The data showed the airplane began a left turn about 4 seconds later, at an altitude of 2,525 ft msl. Throughout the turn, the airplane climbed to a maximum altitude of 2,770 ft msl at 1347:37 before ADS-B contact was lost 6 seconds later. ADS-B contact was reestablished at 1347:53, at an altitude of 1,720 ft msl on a south-southeasterly heading. The last recorded ADS-B data point was at 1347:53, at an altitude of 1,720 ft msl, about .72 miles southwest of the accident site.


One pilot-rated witness to the accident, reported that he was at his home near the accident site and observed that the cloud layer was about 300 ft above ground level (agl.) Cell phone video footage provided by another witness located near the accident site, showed the airplane descending below the cloud layer and subsequently climbing back into the clouds. About 6 seconds later, the video showed the airplane rapidly descending from the clouds in a nose down attitude. Surveillance video footage from the southernmost residence struck by the airplane showed the area of initial impact followed by a subsequent explosion, and a post-crash fire ensued. 


The first identifiable point of impact was a set of palm trees located in front of the southernmost residence struck by the airplane. The wreckage debris field was about 221 ft long by 150 ft wide, oriented on a heading of 240° magnetic at an accident site elevation of about 1,070 ft.  


About 17 ft from the initial point of impact, an east-west spanning stone block wall, located between two residential structures was damaged. The left wing struck a residential structure on the northern side of the wall, while the right wing struck another residential structure on the south side of the wall. Within the debris from the wall, the empennage, left and right wing spars, and carry-through spar were located. About 4 ft west of the wall, a 7 ft diameter area of disturbed dirt and vegetation was observed, which contained various fragments of engine oil sump and propeller blades. The fuselage came to rest about 17 ft west of the area of disturbed dirt. The engine was located about 10 ft beyond the fuselage. All major structural components of the airplane were located throughout the wreckage debris path.  


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

Grumman TBM-3 Avenger, N420GP, accident occurred on May 15, 2025, at Terre Haute-Hulman Field (HUF/KHUF), Terre Haute, Indiana

  • Location: Terre Haute, IN 
  • Accident Number: CEN25LA181 
  • Date & Time: May 15, 2025, 13:39 Local 
  • Registration: N420GP 
  • Aircraft: Grumman TBM-3
  • Injuries: 1 Serious, 1 Minor 
  • Flight Conducted Under: Part 91: General aviation - Positioning

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

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

Tri-State Warbird Museum

On May 15, 2025, about 1339 eastern daylight time, a Grumman TBM-3 airplane, N420GP, was substantially damaged when it was involved in an accident near Terre Haute, Indiana. The pilot sustained serious injuries, and the pilot-rated passenger sustained minor injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 positioning flight.


The pilot reported that while on final approach to the runway, he attempted to increase engine power, but the engine did not respond. He began troubleshooting by switching fuel tanks and completing the emergency checklist item; however, engine power was not restored. The pilot executed a forced landing, and the airplane touched down on the airport perimeter road. The airplane then impacted a drainage ditch, struck the airport perimeter fence, and came to rest inverted. The airplane sustained substantial damage to both wings, fuselage and empennage.


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

Piper PA-46-350P Malibu Mirage, N253MA, accident on May 11, 2025 at Indy South Greenwood Airport (HFY/KHFY), Greenwood, Indiana

 

  • Location: Greenwood, IN 
  • Accident Number: CEN25LA175 
  • Date & Time: May 11, 2025, 12:31 Local 
  • Registration: N253MA 
  • Aircraft: Piper PA 46-350P 
  • Injuries: 2 Serious 
  • Flight Conducted Under: Part 91: General aviation - Personal 

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

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

Hoosier Doc LLC

On May 11, 2025, about 1231 central daylight time, a Piper PA46-350P, N253MA, sustained substantial damage when it was involved in an accident near Greenwood, Indiana. The pilot and passenger received serious injuries. The airplane was operated as a Title 14 Code of Federal Regulations (CFR) Part 91 personal flight.


The pilot reported that the airplane had been converted from the original piston engine to a Pratt & Whitney PT6A-35 turbo-propeller engine installation. The pilot reported that the engine started normally, but when he advanced the throttle lever to taxi, the power did not increase. He allowed the engine to run for a time and made another attempt to taxi and the engine responded normally. 


The pilot stated that the pre-takeoff engine and propeller checks were normal, and he proceeded to takeoff on runway 1 at the Indy South Greenwood Airport (HFY). The airplane accelerated to 80 knots, and the pilot rotated the airplane to takeoff. He reported that when the airplane was about 100 ft agl, the engine lost all power, and he instinctively advanced the throttle lever with no resulting increase in power. The airplane impacted a taxiway on the west side of the runway and slid to a stop, striking an embankment during the impact sequence. The airplane received substantial damage to the fuselage.

Cirrus SF50 Vision Jet G2+, N56GY, accident on March 24, 2025, at Kissimmee Gateway Airport (ISM/KISM), Kissemmee, Florida

 

  • Location: Kissimmee, FL
  • Accident Number: ERA25LA155
  • Date & Time: March 24, 2025, 08:04 Local
  • Registration: N56GY
  • Aircraft: CIRRUS DESIGN CORP SF50
  • Injuries: 1 None
  • Flight Conducted Under: Part 91: General aviation - Executive/Corporate

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

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

Galati Yacht Sales LLC

On March 24, 2025 about 0804 eastern daylight time, a Cirrus Design Corporation SF50, N56GY, was substantially damaged when it was involved in an accident at Kissimmee Gateway Airport (ISM), Orlando, Florida. The commercial pilot was not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 executive/corporate flight.


The pilot stated that he performed a standard preflight, utilizing the Federal Aviation Administration (FAA) Approved Airplane Flight Manual external checklist with no discrepancies reported, but he did not check the fuel tanks for contamination, believing that task would be accomplished by Cirrus personnel. One Crew Alerting System (CAS) message associated with engine start volts low was noted before engine start, but the engine started normally, and the message extinguished after engine start. The flight departed from runway 24 about 0725, and after takeoff was flying with the autopilot and autothrottle engaged. According to data downloaded from the recoverable data module (RDM) along with pilot provided information, while climbing at flight level (FL) 198, about 0737:23 the message FADEC NO DISPATCH Caution displayed. He went thru that checklist while continuing to climb and reported the message continued following checklist completion, but continuance of the flight was allowed. About 2 minutes 19 seconds later while flying at FL234, the red FADEC CTRL DEGRADED Warning illuminated. He pulled up that checklist and worked through it but the message continued. He contacted the controller and requested a vector to return to ISM, but did not declare an emergency at that time. He reported performing the FADEC Reset via the multi-function (MFD) display and recalled a warning that the engine power may not be reliable. In going thru that checklist, the engine did not respond to thrust lever change, so he then declared an emergency with the controller. While descending he attempted to slow the airplane using the manual mode of the autothrottle by setting a target speed of 180 knots indicated airspeed (KIAS), but the airplane did not slow, nor did the thrust lever move as expected. At that time the flight was in close proximity to ISM while the thrust remained at + or – 30% so he requested delaying vectors as the flight was fast and close to ISM. He then pushed the thrust lever full forward and the thrust increased to 42%, then brough it back to flight idle and the thrust decreased to 1%, which did not change with further thrust lever advancement. The pilot added that having the thrust go from 30% to 1% added a new level of complexity to the situation.


The pilot considered either deploying the Cirrus Airframe Parachute System (CAPS) or gliding to ISM and noted the later was possible. At that point while on the base leg of the airport traffic for runway 6 at ISM, he extended the flaps to 50% and proceeded to the runway lowering the landing gear and flaps to 100% at the last minute. The flight touched down fast 2/3’s down the 5,001 ft long runway and he was unable to stop using normal brakes. The flight rolled off the end of the runway onto grass and collided with an airport boundary fence. He shut down the engine, which occurred at 0804, and evacuated the airplane.


A review of the maintenance records revealed that on March 18, 2025, when turning on power a “FADEC No Dispatch and FADEC CTRL Degraded” CAS Messages were displayed. A download of the FADEC was performed and the information was provided to the engine manufacturer. Because the airplane was on a list for replacement of the fuel control unit (FCU) by a Service Bulletin, the FCU was removed and a modified FCU was installed on March 20, 2025. Following the replacement of the FCU maintenance personnel performed acceleration and stability checks with no discrepancies noted. The maintenance was signed off on March 21, 2025, and the accident flight was the 1st flight since the modified FCU was installed.


Following postaccident examination of the airframe and engine, the engine was removed and sent to the manufacturers facility for further examination and testing.

Cessna 172S Skyhawk SP, N923EP, accident occurred on March 1, 2025, at New Smyrna Beach Municipal Airport (EVB/KEVB), New Smyrna Beach, Florida

 


  • Location: New Smyrna Beach, FL 
  • Accident Number: ERA25LA132 
  • Date & Time: March 1, 2025, 11:38 Local 
  • Registration: N923EP 
  • Aircraft: Textron Aviation 172 
  • Injuries: 2 None 
  • Flight Conducted Under: Part 91: General aviation - Instructional

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

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

Epic Aviation Inc

On March 1, 2025, about 1138 eastern standard time, a Cessna 172S, N923EP, was substantially damaged when it was involved in an accident near New Smyrna Beach, Florida. The flight instructor and student pilot were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 instructional flight.


The flight instructor stated that the accident flight was the student’s first flight in an airplane. Prior to departure from New Smyrna Beach Municipal Airport (EVB), New Smyrna Beach, Florida, the left fuel tank was fueled, bringing the total fuel onboard to 51.6 gallons. No discrepancies were noted during the preflight inspection or engine run-up prior to departure. The flight instructor performed a departure briefing, and after holding short of the runway briefly, was cleared for takeoff.


During the takeoff roll with the mixture control full rich and full throttle applied, the engine rpm was more than 2,300, which increased to 2,400 rpm after getting airborne. When the airplane was about 180 ft above the runway the engine rpm dropped and the engine lost power completely. The flight instructor took control of the airplane and executed an emergency landing, turning “everything fuel related off.” He pitched down to maintain airspeed, declared a mayday with the air traffic control tower and touched down on the beginning of the threshold for runway 2, then rolled onto grass. To avoid nosing over the flight instructor tried not to brake excessively and maneuvered the airplane toward a fence to avoid vehicles on a road that was off-airport. The airplane collided with the fence and nosed over.


A review of the operator-provided download of on-board avionics revealed that takeoff power was applied at 1137:41, and the rpm remained above 2,400 until 1138:04, when the rpm and fuel flow began to decrease. The engine rpm continued to decrease to 0.


The airplane was recovered and retained for further examination.

Cessna 172N Skyhawk, N75775, accident occurred on May 4, 2025, near Vance Brand Airport (LMO/KLMO), Longmont, Coloardo

  • Location: Longmont, CO 
  • Accident Number: CEN25LA168 
  • Date & Time: May 4, 2025, 12:00 Local 
  • Registration: N75775 
  • Aircraft: Cessna 172N 
  • Injuries: 1 None 
  • Flight Conducted Under: Part 91: General aviation - Instructional
https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=N103DG


D&R AVIATION LLC

Western Air Flight Academy

On May 4, 2025, about 1200 mountain daylight time, a Cessna 172N airplane, N75775, was substantially damaged when it was involved in an accident near Longmont, Colorado. The pilot was not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 instructional flight.


The pilot stated that he was on final approach when he noticed that the engine was not responding to his throttle control changes. The engine speed was about 2,000 rpm when he attempted a go-around. However, the engine power did not increase as he applied full throttle, and the airplane would not climb due to the low power setting. He noted that the engine subsequently lost power completely and he executed a forced landing to a field. During the landing, the airplane struck a fence and nosed over. The airframe sustained substantial damage to the right wing, vertical stabilizer, and rudder.


A post-accident examination conducted by a Federal Aviation Administration inspector determined that the throttle cable was disconnected from the carburetor. Both the throttle cable and the carburetor control arm moved freely and there was no evidence of damage to either component. The connecting hardware – bolt and nut – were not observed at the time of the examination.


Airplane maintenance records revealed that a 100-hour inspection was completed three weeks before the accident, and the engine carburetor was replaced at that time. The airplane had accumulated about 9.9 hours flight time since that maintenance.