Thursday, June 05, 2025

Loss of engine power (total): Commander Aircraft 114TC, N6042E, fatal accident occurred on May 21, 2023, near Naked Lady Ranch Airport (64FA), Palm City, Florida

  • Location: Palm City, Florida 
  • Accident Number: ERA23FA239 
  • Date & Time: May 21, 2023, 15:30 Local 
  • Registration: N6042E 
  • Aircraft: COMMANDER AIRCRAFT CO 114TC 
  • Aircraft Damage: Destroyed 
  • Defining Event: Loss of engine power (total) 
  • Injuries: 1 Fatal 
  • Flight Conducted Under: Part 91: General aviation - Personal
On May 21, 2023, about 1530 eastern daylight time, a Commander 114TC airplane, N6042E, was destroyed when it was involved in an accident near Palm City, Florida. The pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

An eyewitness observed the accident airplane flying at low altitude before the engine made an unusual noise and stopped producing power, after which the airplane entered a descending turn to the ground. The airplane was mostly consumed by a post-impact fire. The wreckage was located about 700 yards north of an airport runway, and it could not be determined if the airplane was departing or arriving at that airport when the accident occurred. Examination of the engine revealed normal compression, ignition, and fuel system function. Although the airplane’s fuel quantity at the time of the accident could not be determined due to fire damage, no blockages or anomalies were found with the remaining components of the fuel system. Examination of the wreckage confirmed flight control continuity and found no evidence of preimpact mechanical failure.

Toxicological results indicated that the pilot had used a cannabis product; however, without delta-9-THC or the psychoactive metabolite of delta-9-THC detected in blood, it is unlikely that the pilot was experiencing significant impairing acute psychoactive effects of cannabis at the time of the accident.

Although the circumstances of the accident are consistent with a loss of engine power, the reason for the loss of power could not be determined, as postaccident examination did not reveal any evidence of a mechanical malfunction or anomaly. The descending turn before impact as described by the witness was consistent with an aerodynamic stall and loss of control, likely as a result of the pilot’s failure to maintain airspeed following the loss of engine power. 

- Probable Cause: A loss of engine power for undetermined reasons, and the pilot’s subsequent loss of control, which resulted in impact with terrain.

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

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

Powerplant sys/comp malf/fail: Beechcraft V35 Bonanza, N272S, fatal accident occurred on May 21, 2023, near Rougemont, North Carolina






  • Location: Rougemont, North Carolina 
  • Accident Number: ERA23FA238 
  • Date & Time: May 21, 2023, 11:15 Local 
  • Registration: N272S Aircraft: Beech V35 
  • Aircraft Damage: Destroyed 
  • Defining Event: Powerplant sys/comp malf/fail 
  • Injuries: 1 Fatal 
  • Flight Conducted Under: Part 91: General aviation - Personal

On May 21, 2023, at 1115 eastern daylight time, a Beech V35 airplane, N272S, was destroyed when it was involved in an accident near Rougemont, North Carolina. The pilot was fatally injured. The flight was operated as Title 14 Code of Federal Regulations Part 91 personal flight.

The pilot was on a long cross-country flight when the airplane’s engine lost power completely. The airplane subsequently impacted terrain in a group of pine trees; a postimpact fire ensued. The cockpit and engine sustained extensive thermal damage. Examination of the engine revealed that the crankcase was breached adjacent to the Nos. 3 and 4 cylinders. Disassembly of the engine revealed damage consistent with oil starvation. Due to the extent of the postimpact fire damage, the source of the oil starvation could not be identified. The maintenance records for the engine were presumed to be onboard the airplane and destroyed by fire.

Postmortem toxicology testing by the FAA Forensic Sciences laboratory detected Delta-9- tetrahydrocannabinol (delta-9 THC) and metabolites in the pilot’s heart blood and urine. Delta9-THC is the primary psychoactive chemical in cannabis, including marijuana, hashish, and other cannabis products. Marijuana is a federal Schedule I controlled substance, and the FAA considers its use by pilots unacceptable, regardless of state laws. The postmortem concentrations of the marijuana metabolites indicate that the pilot had used a cannabis product and may have been experiencing associated impairing effects at the time of the accident. However, the precise timing of his last cannabis use, and whether significant impairment was present, could not be determined from the toxicological evidence alone.

- Probable Cause: A total loss of engine power due to oil starvation. The source of the oil starvation could not be determined.

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

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

Controlled flight into terr/obj (CFIT): Piper J3C-65 Cub, N21811, fatal accident occurred on August 16, 2024, near Mooresburg, Tennessee



  • Location: Mooresburg, Tennessee
  • Accident Number: ERA24LA346 
  • Date & Time: August 16, 2024, 07:15 Local 
  • Registration: N21811 Aircraft: Piper J3 
  • Aircraft Damage: Substantial 
  • Defining Event: Controlled flight into terr/obj (CFIT) 
  • Injuries: 1 Fatal
  •  Flight Conducted Under: Part 91: General aviation - Personal 

The pilot departed from a private airstrip and overflew his property. The airplane subsequently impacted a barn adjacent to the airstrip. The airplane sustained substantial damage, and the fuselage was mostly consumed by the postimpact fire that ensued. The pilot was fatally injured. An autopsy of the pilot was performed by the William L. Jenkins Forensic Center, Johnson City, Tennessee. The autopsy report listed the cause of death as blunt force injuries and the manner of death as suicide.

- Probable Cause: The pilot’s intentional flight into a building as an act of suicide.

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

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

Boeing 737-823 (WL), N885NN, accident occurred on March 13, 2025, at Denver International Airport (DEN/KDEN), Denver, Colorado

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.

Aviation Accident Preliminary Report - National Transportation Safety Board

Investigator In Charge (IIC): Lovell, John

Additional Participating Entities:

  • Sam Farmiga; GE/CFM
  • Matt Rigsby; FAA AVP110
  • Kaushik Narayan Ramesh; American Airlines
  • Jay Dorothy; APA Doug Housley; TWU-IAM
  • Andrew Rhinehart; APFA
  • Steve Haggerty; Boeing
  • Dave Cunningham; Denver Airport
  • Frederic Walbrou; BEA
  • Hannu Melaranta; EASA
  • Philippe Fouchard; Safran Aircraft Engines
https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=N885NN

https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/199853/pdf
  • Location: Denver, CO 
  • Accident Number: DCA25FA159 
  • Date & Time: March 13, 2025, 17:59 Local 
  • Registration: N885NN 
  • Aircraft: Boeing 737-823 
  • Injuries: 12 Minor, 166 None 
  • Flight Conducted Under: Part 121: Air carrier - Scheduled

On March 13, 2025, about 1759 mountain daylight time, American Airlines flight 1006, Boeing 737-823, N885NN, experienced engine vibrations during takeoff from Colorado Springs Airport (COS), Colorado Springs, Colorado. The flight crew continued the takeoff, then diverted to and landed at Denver International Airport (DEN), Denver, Colorado. After landing, the flight crew taxied to their assigned gate and both engines were shutdown. After shutdown, a fire ensued in the area of the No. 2 (right) engine and the passengers and crew evacuated the airplane.


The fire was extinguished within 1 minute by gate ramp personnel, prior to the arrival of the DEN aircraft fire fighting and rescue (ARFF). Of the three trucks that arrived, one truck, positioned toward the right side of the airplane sprayed water on the right aft fuselage area and right inboard wing “hot spots” (areas indicated by their infrared heat sensors). 


Video provided by DEN airport operations showed a trail of fluid leaking from under the right engine nacelle as the airplane taxied into the gate.


The flight was operated under the provisions of Title 14 Code of Federal Regulations Part 121 as a scheduled domestic passenger flight from COS to Dallas Fort Worth International Airport (DFW). There were 2 flight crew, 4 cabin crew and 172 passengers on board. Twelve passengers received minor injuries. The airplane received substantial damage. Visual meteorological conditions prevailed at the time of the accident.


The first officer (FO) was the pilot flying, and the captain was the pilot monitoring. According to the flight crew, during takeoff and just before V1 there was an EGT over-temp for the No. 2 engine. After gear and flaps were retracted, the power was slightly reduced on the No. 2 engine and the EGT over-temp subsided to within limits.


During climbout, the captain noted high engine vibration indications for the right engine (No. 2). The captain called for the High Engine Vibration checklist and the FO continued to fly the airplane. The flight crew discussed the need to divert and contacted American Airlines dispatch. It was determined that DEN would be the most reasonable airport to divert to. The crew climbed to 16,000 feet msl, which was the highest altitude reached for the flight.


The captain informed the passengers and the flight attendants that the flight was diverting to DEN. Approach and landing were normal, and it took about five minutes to taxi to the gate.  Soon after arriving at the gate, flight attendants heard passengers yelling “fire” and “smoke” and saw smoke start to the fill the cabin. One of the flight attendants tried calling the flight crew but did not get an answer. Another flight attendant knocked on the cockpit door to alert the flight crew of the fire outside the airplane and smoke in the cabin. In the meantime, passengers got up and were coming to the flight attendants wanting to get off the airplane. The flight attendants conducted their assessments and initiated an evacuation.


Passengers used the L1 door, both left overwing window exits, and the R2 door for egress. The passengers who used the L1 door deplaned using the jetway bridge. After the evacuation, the L2 door was observed cracked open, with maintenance subsequently discovering the escape slide jammed in the door, preventing its operation. The R2 evacuation slide deployed automatically when the R2 door was opened.


The passengers who used the left overwing window exits were evacuated off the wing by a combination of ground vehicles, ladders that were available in the gate area, and a belt loader. Post event examination found the flaps had remained at zero.


Investigation

The airplane was towed to a local maintenance hangar for examination. The airplane exhibited heat/smoke/burn indications near the right engine nacelle, right wing, right side of the fuselage aft of the wing, the right main landing gear, and the right main landing gear wheel well (see figure 1).

The on-scene engine examination found the right engine nacelle was intact; however, there was dark streaking which was consistent with in-flight streamlines and the aft and bottom of the nacelle was sooted and thermally distressed, consistent with a ground fire (see figure 2).

The airplane was powered by two CFM56-7B turbofan engines. The right engine was examined and all the engine fan blades were present, but one fan blade platform was fractured. In addition, the lockwire of a fuel fitting on the variable stator vane (VSV) was loose and installed in the incorrect direction. The VSV actuator rod end was incorrectly fastened and secured to the VSV actuator allowing fuel to leak from the fitting. The VSV rod end muscle line was fractured in the weld, and the 6 o’clock seal drain line of the inboard thrust reverser half was blocked with sealant above the lower bifurcation fire seal and in the exit tube.


The L2 slide was found removed from its bustle and on the floor of the L2 passageway with its safety pin installed. The slide pack was inspected and the bannis latch was found to move freely. There were some dark scuffs on the outboard side of the pack, and there was a tear on the underside of the girt fabric towards the center.


NTSB launched on this event and operations, powerplants, airworthiness, and survival factors groups were formed on-scene. The cockpit voice recorder (CVR) and the flight data recorder (FDR) were sent to the recorders lab at NTSB headquarters for download and audition. Intelligible CVR audio began while the aircraft was climbing from 15,000 to 16,000 ft and the crew was performing the Engine High Vibration checklist. The cockpit area microphone (CAM) channel of the CVR recorded an hour of audio prior to this time, however audio from the CAM was unintelligible for the full duration of the recording.


The FDR was in good condition and the data were extracted normally from the recorder. The FDR recording contained approximately 54 hours of data with over 1,000 parameters recorded. The event flight was the last flight of the recording, and its duration was approximately 1 hour.


Maintenance records for the right engine were reviewed. The damaged fan blade platform, rod end manifold, and the aft exhaust plug were retained for further examination.


The L2 slide was shipped to the manufacturer for a detailed inspection and its maintenance log will be reviewed. 


Parties to the investigation are American Airlines, General Electric (GE) Aerospace, Federal Aviation Administration (FAA), The Boeing Company (Boeing), Allied Pilots Association (APA), Transport Workers Union - International Association of Machinists and Aerospace Workers (TWU-IAM), Association of Professional Flight Attendants (APFA), and Denver Airport.  In accordance with the provisions of Annex 13 to the Convention on International Civil Aviation, the Bureau d’Enquetes et d’Analyses pour la securite de l’aviation civile (BEA) of France appointed an Accredited Representative since the CFM International engine is a joint venture between GE Aerospace and Safran Aircraft Engines. Safran Aircraft Engines and European Union Aviation Safety Agency (EASA) are technical advisors to BEA, as provided by Annex 13. 


The investigation continues. 

Robinson R44 Raven II, N1195P, fatal accident occurred on May 23, 2025, near Miami, Texas

  • Location: Miami, TX 
  • Accident Number: CEN25FA183 
  • Date & Time: May 23, 2025, 07:18 Local 
  • Registration: N1195P 
  • Aircraft: ROBINSON HELICOPTER COMPANY R44 II 
  • Injuries: 1 Fatal 
  • Flight Conducted Under: Part 91: General aviation - Personal

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

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

On May 23, 2025, about 0718 central daylight time, a Robinson Helicopter Company R44 II helicopter, N1195P, was destroyed when it was involved in an accident near Miami, Texas. The student pilot was fatally injured. The helicopter was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.


The student pilot reportedly planned to fly his helicopter from his home in Miami, Texas, to a personal appointment in Amarillo, Texas, on the morning of the accident. The pilot departed about 0711 and proceeded southwest. The person who the pilot was meeting in Amarillo stated that the pilot called him at 0712 while en route. The pilot told him that he was concerned about the fog. The conversation lasted about 4 minutes until he told the pilot to hang up so he could focus on flying.


A local R44 pilot stated that he had cancelled his personal flight on the morning of the accident in Canadian, Texas, about 20 nm northeast of the accident site, due to low clouds and fog.


A witness near the accident site stated that he was outside when he heard the helicopter approaching from the east. The weather conditions were foggy with low clouds and mist. He could not determine the exact altitude of the cloud layer because the fog was so low. Due to the fog and low clouds, he could not discern the color of the helicopter, and it just looked like a dark silhouette, but it was flying very low and appeared to be having trouble maintaining control. The helicopter was flying west when it descended below the terrain in a small valley, then climbed up with the nose low and appeared to climb backwards. After the backwards climb, it leveled off very briefly, then made a rapid forward descent toward terrain, in a relatively level attitude. The helicopter was headed back to the east during the rapid descent. He did not notice any parts depart from the helicopter during the accident sequence. The helicopter impacted the ground hard and exploded.


The accident site was located about 4.5 nm southwest of the departure location in a cattle pasture (figure 1). The helicopter impacted the ground facing east, then rotated left about 120° where it came to rest. A postimpact fire consumed a majority of the fuselage and part of the tailcone. The initial impact mark featured a round impression in the dirt surrounded by pieces of the windshield and door frames. On either side of the impression were parallel impact marks and fragments of the skid tubes. One of the main rotor blades impacted the ground near the initial impact mark. Before ground impact, the main rotor blades struck the aft portion of the tailboom, which separated the empennage and tail rotor assembly. All major helicopter components were identified at the accident site. On-scene examination of the airframe and engine did not reveal any evidence of preimpact malfunctions or failures that would have precluded normal operation of the helicopter.

At 0715, the automated weather observation system (AWOS-3) at Perry Lefors Field Airport, (PPA) Pampa, Texas, located about 15 miles southwest, reported wind from 140° at 7 knots, visibility 5 statute miles in mist, overcast clouds at 400 ft above ground level (agl), temperature 16°C (60°F), and dew point 16°C (60° F).


The National Weather Service (NWS) had a Graphic-AIRMET current for the accident time for instrument flight rules (IFR) conditions due to visibility below 3 miles in fog/mist and ceilings below 1,000 ft agl. Meteorological data indicated low IFR and IFR conditions along the route of flight and the fog stability index (FSI) supported a high risk of radiation type fog formation.


There was no evidence that the pilot received a weather briefing before the accident flight. 


A Spidertracks GPS unit recovered from the accident site was sent to the National Transportation Safety Board’s Vehicle Recorder Laboratory for data extraction


The pilot’s flight logbook has not been recovered, but the pilot had reportedly accumulated about 150 total flight hours in the helicopter.

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.