Monday, October 19, 2026

Structural icing: Piper PA-32R-301 Saratoga II HP, N9236J, fatal accident occurred on April 12, 2024, near Knoxville, Tennessee

  • Location: Knoxville, Tennessee 
  • Accident Number: ERA24FA176 
  • Date & Time: April 12, 2024, 16:33 Local 
  • Registration: N9236J 
  • Aircraft: Piper PA-32R-301 
  • Aircraft Damage: Destroyed 
  • Defining Event: Structural icing 
  • Injuries: 1 Fatal 
  • Flight Conducted Under: Part 91: General aviation - Personal

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

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

On April 12, 2024, about 1633 eastern daylight time, a Piper PA-32R-301, N9236J, was substantially damaged when it was involved in an accident near Knoxville, Tennessee. The commercial pilot was fatally injured. The flight was operated under Title 14 Code of Federal Regulations Part 91 as a personal flight.

The pilot departed on an instrument flight rules cross-country flight. About 15 minutes after departure, shortly after reaching a cruise altitude of 8,000 ft mean sea level (msl), the pilot reported to air traffic control that he was “picking up moisture in the clouds” and asked for a course deviation or a higher altitude. The controller approved course deviations and cleared the pilot to climb to 10,000 ft msl, which the pilot accepted. A performance study of the airplane's ADS-B flight track data showed that the airplane's airspeed decreased during the subsequent climb, and the airplane reached a maximum altitude about 8,500 ft msl and a minimum airspeed around 80 knots (kts) before it rapidly rolled left and lost altitude at a rate of about 1,300 ft per minute, consistent with an aerodynamic stall. The airplane briefly leveled off before entering a descending right turn, reaching a descent rate of 6,000 ft per minute. The descending turn continued until flight track data was lost at an altitude about 5,750 ft msl. At this time, the airplane's calculated calibrated airspeed was about 210 kts; the airplane's published never-exceed speed (Vne) was 197 kts indicated airspeed.

A witness on the ground near the accident site observed the airplane “twirling” as it descended below the clouds and also observed debris falling from the sky. The wreckage was distributed over a distance of more than 10,000 ft, consistent with an in-flight breakup. Postaccident examination of the airplane and engine revealed no evidence of a mechanical failure that would have precluded normal operation. Control cable separations and airframe structural fractures all exhibited characteristics consistent with overload failure. The airplane was not equipped with anti- or de-icing equipment and was not certified for flight into known icing conditions.

Review of weather information for the area indicated cloud bases around 4,500 to 5,000 ft with tops around 18,500 ft. The freezing level was around 5,500 ft, with supercooled large droplets (SLD) likely between 6,000 and 8,000 ft. The pilot filed his instrument flight plan for the accident flight with a flight planning application that generated a route briefing. The briefing contained weather information for the route of flight, including the forecast for moderate icing conditions; however, information regarding the potential SLD conditions would have been contained in supplemental icing information not provided in the standard briefing. Whether the pilot accessed supplemental icing information before the flight could not be determined.  

Flight track information indicated that the airplane likely entered instrument meteorological and icing conditions shortly after takeoff, and that the airframe and flight control surfaces began to accumulate ice rapidly, as the time between the pilot's request for a higher altitude and the loss of flight track data was about 2 minutes. The airplane then likely encountered an aerodynamic stall while flying at an airspeed of 80 kts (15 kts faster than its maximum published stall speed). This was consistent with the effects of increased drag and stall speed due to ice accretion. It is likely that the pilot lost control of the airplane following the initial aerodynamic stall and was unable to recover. During the subsequent descending turn, the airplane exceeded its structural limitations, resulting in an in-flight breakup.

The pilot held an instrument rating; however, review of available logbook information indicated limited recent instrument experience, with two instrument approaches and one holding procedure conducted during an instructional flight about 7 months before the accident. Whether the pilot's loss of airplane control was the result of his inability to control the airplane due to ice accretion, a lack of proficiency in instrument flight, or a combination of those factors, could not be determined.

Although the pilot's awareness of the potential for SLD could not be determined, the route briefing generated at the time he filed the flight plan provided adequate information to alert him to the potential for icing conditions along his intended route of flight. Nevertheless, the pilot chose to depart and continue into an area with a known potential for icing conditions in the airplane that was not equipped to do so.

- Probable Cause: The pilot's decision to depart into an area of instrument meteorological and icing conditions, which resulted in loss of airplane control and a subsequent in-flight breakup.

Fuel starvation: Cessna 414A Chancellor, N414BS, fatal accident occurred on June 27, 2024,near McKinney National Airport (TKI/KTKI), McKinney, TX

  • Location: McKinney, Texas 
  • Accident Number: CEN24FA240 
  • Date & Time: June 27, 2024, 10:28 Local 
  • Registration: N414BS
  • Aircraft: Cessna 414A 
  • Aircraft Damage: Destroyed
  • Defining Event: Fuel starvation 
  • Injuries: 2 Fatal, 1 Serious 
  • Flight Conducted Under: Part 91: General aviation - Personal

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

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

On June 27, 2024, at 1028 central daylight time, a Cessna 414A airplane, N414BS, was destroyed when it was involved in an accident near McKinney, Texas. The private pilot and a passenger were fatally injured, and a second passenger sustained serious injuries. The airplane was operated under Title 14 Code of Federal Regulations Part 91 as a personal flight

The pilot was departing on a local flight to check newly installed avionics on the airplane. During takeoff, the airplane lifted off within the performance specifications cited in the airplane flight manual. Shortly after liftoff, the pilot reported to air traffic control (ATC) that he had lost left engine power. The pilot continued the takeoff with the landing gear still extended.

A witness stated that the airplane seemed to lose left engine power during the takeoff before reaching taxiway B4, and “yawed left quite a bit.” The remaining runway distance from the B4 taxiway to the departure end of the runway was about 2,600 to 2,700 ft. The witness stated that the airplane was not far past the departure end of runway when it began to turn left.

As the pilot continued the takeoff and attempted the climb out, ATC instructed the pilot to turn right. The pilot responded that he was going to turn left, which was a turn into the inoperative engine and in the improper direction due to the greater left rolling tendency and increased likelihood of a loss of control. As the flight progressed, the airplane ground speed slowed to the airplane's air minimum control speed (Vmc) when it rolled left and impacted terrain in an inverted attitude. The airplane was destroyed.

Postaccident examination of the airplane revealed no mechanical anomalies that would have precluded normal operation. The examination revealed the left engine fuel tank valve was in the Off position, which starved the left engine of fuel, creating a total loss of left engine power. The left engine propeller was not feathered, and the landing gear was extended.

Although the pilot completed ground and flight training and a proficiency check in the make and model airplane about 4 months before the accident, he failed to ensure proper fuel tank selection, with the fuel selector in the OFF position for the left engine and failed to land on the remaining runway after the loss of left engine power. Following the decision to continue the takeoff, the pilot also failed to follow engine inoperative emergency procedures that would have increased airspeed/climb rate to enable continued flight. The pilot's actions resulted in a loss of control that led to a Vmc roll and impact with terrain.

- Probable Cause: The pilot's improper decision to attempt continued flight after a loss of left engine power with usable runway remaining and his subsequent failure to follow the emergency procedures and maintain air minimum control speed, which resulted in a loss of control. Contributing to the accident was the pilot's improper fuel tank selection that resulted in a loss of left engine power due to fuel starvation.

Loss of control in flight: XAG P150 MAX, unregistered, accident occurred on July 2, 2026, near Wolcott, Indiana

  • Location: Wolcott, Indiana 
  • Accident Number: CEN26LA245 
  • Date & Time: July 2, 2026, 08:12 Local 
  • Registration: None 
  • Aircraft: XAG P150 MAX
  • Aircraft Damage: Substantial 
  • Defining Event: Loss of control in flight 
  • Injuries: 1 Serious 
  • Flight Conducted Under: Part 137: Agricultural 

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

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

The pilot/operator commanded the takeoff sequence on the agricultural unmanned aircraft system (UAS) and the UAS climbed to about 15 ft above its launch rig. Hearing an abnormal “popping” noise coming from the UAS, the pilot initiated the automated landing sequence and the UAS descended to about 2 ft above the rig and about 4 to 5 ft from the operator's station. The pilot lost control of the UAS as it moved towards his position causing the pilot to duck behind the operator's barrier. When he ducked, the UAS's right-rear propeller struck his left hand resulting in a serious injury. The UAS descended and crashed into terrain resulting in substantial damage to the right-rear arm and propeller.

The operator sent the UAS on-board data to the manufacturer for decoding. The manufacturer's report found that about 1 second after the UAS started up, a joystick input was received which paused the UAS's takeoff. A couple seconds later, additional control inputs were recorded and the UAS responded accordingly. The data found no mechanical malfunction or failure with all engine parameters in the normal range.

- Probable Cause: The pilot's failure to maintain control of the UAS during takeoff.

Powerplant sys/comp malf/fail: Titan T-51 Mustang, N751TX, fatal accident occurred on July 21, 2024, near Germack Airport (7D9), Geneva, Ohio

  • Location: Geneva, Ohio 
  • Accident Number: ERA24FA310 
  • Date & Time: July 21, 2024, 17:54 Local 
  • Registration: N751TX 
  • Aircraft: WILLIAMS JOHN TITAN T-51 MUSTANG 
  • Aircraft Damage: Substantial 
  • Defining Event: Powerplant sys/comp malf/fail 
  • Injuries: 1 Fatal 
  • Flight Conducted Under: Part 91: General aviation - Personal

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

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

On July 21, 2024, about 1754 eastern daylight time, an experimental, amateur-built Titan T-51 Mustang, N751TX, was substantially damaged when it was involved in an accident near the Germack Airport (7D9), Geneva, Ohio. The commercial pilot was fatally injured. The airplane was operated by the pilot as a personal flight conducted under the provisions of Title 14 Code of Federal Regulations Part 91.

The pilot, who was the builder of the experimental amateur-built airplane, was conducting a post-maintenance test flight. After performing several aerobatic maneuvers near the airport, the pilot began a high-speed low pass over the runway. Upon passing most of the runway, the airplane began a climb. A witness heard the engine go to a high rpm and then saw the entire propeller hub break apart. After the propeller hub fractured and separated, the airplane began a left turn toward a road. While maneuvering toward the road, the airplane's left wing impacted a tree and the airplane subsequently rolled over and impacted terrain.

Onboard recorded data revealed that, at the time the propeller separated, the engine was operating at 6,813 rpm, which equated to a propeller speed of 3,585 rpm. This speed was considerably in excess of the propeller blade blank manufacturer's limit of 2,100 rpm. This speed would have produced a centrifugal force that was more than 3 times the design limit of the propeller blade blanks. Further examination of the onboard data revealed that, around the time of the propeller overspeed, the airplane was traveling at an airspeed about 223 miles per hour (mph); the published never-exceed speed (Vne) for the airplane was 215 mph. The data also revealed a sudden decrease in the longitudinal load factor, consistent with a sudden deceleration of the airplane, followed shortly thereafter by the longitudinal load factor returning to normal. A possible reason for the deceleration was a sudden increase in drag from the propeller blades moving to low pitch. This was followed by a reduction in drag on the airplane, which was likely due to the propeller separating from the airplane.

Postaccident examination of the propeller governor, governor adapter, and the propeller gearbox revealed no evidence of any preacident mechanical failures or malfunctions that would have precluded normal operation. Ultimately, the reason for the propeller overspeed could not be determined based on available information.

- Probable Cause: A sudden propeller overspeed and subsequent separation of the propeller blades and hub, while maneuvering at high speed and at low altitude, which resulted in a collision with a tree during the subsequent forced landing attempt.