Friday, July 11, 2025

Cessna A150L Aerobat, N6436F, fatal accident occurred on June 18, 2025, near Three Points, Arizona

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

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

  • Location: Three Points, AZ 
  • Accident Number: CEN25FA212 
  • Date & Time: June 18, 2025, 09:22 Local 
  • Registration: N6436F 
  • Aircraft: Cessna A150L 
  • Injuries: 2 Fatal 
  • Flight Conducted Under: Part 91: General aviation - Instructional 

On June 18, 2025, about 0922 mountain standard time, a Cessna A150L airplane, N6436F, was substantially damaged when it was involved in an accident near Three Points, Arizona. The student pilot and flight instructor were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 instructional flight.

A family member of the student pilot reported that the airplane departed from Ryan Field Airport (RYN), Tucson, Arizona, about 0900 mountain standard time on June 18, 2025. An alert notification (ALNOT) was issued the following day, June 19, 2025, at 1228, when the airplane was reported missing by a family member of the student pilot. The wreckage was located about 1626, about 11 miles south of RYN in a rural area with desert vegetation.

Radar data obtained from Davis-Monthan Air Force Base revealed that the first radar return was at 0901 and that the duration of the flight was about 21 minutes. The flight path was consistent with low-altitude maneuvering, and the wreckage was located about 0.13 miles west of the last radar return. Figure 1 depicts the airplane’s flight path in magenta and the ground path in green.

The main wreckage came to rest upright on its nose and the aft fuselage was elevated. The forward cabin and engine sustained upward crushing consistent with impact damage. The fuselage was separated about midway between the rear window and the vertical stabilizer. The aft fuselage and empennage remained connected only by the flight control cables.

Both wings exhibited aft and upward crushing consistent with impact damage. The left wing remained attached to the fuselage, and the right wing remained partially attached. The right wing aft spar attachment point was separated, consistent with impact damage.

Both propeller blades exhibited chordwise scratching and leading edge polishing. One of the propeller blades was bent aft about 45° and exhibited twisting deformation. During recovery, liquid consistent with 100LL aviation fuel was drained from both wing fuel tanks. The right wing fuel tank contained about 4 gallons, and the left wing fuel tank contained about 5 gallons.

The airplane was recovered from the accident site and transported to a secure facility for further examination.

No mechanical anomalies were found with the airframe or engine during the onsite or followup wreckage examinations that would have precluded normal operations.

Thursday, July 10, 2025

Landing gear not configured: Cessna 680 Citation Sovereign, N680SA, accident on August 18, 2024, at Washington-Warren Airport (OCW/KOCW), Washington, North Carolina

  • Location: Washington, North Carolina 
  • Accident Number: ERA24LA351 
  • Date & Time: August 18, 2024, 21:39 UTC 
  • Registration: N680SA 
  • Aircraft: Cessna 680 
  • Aircraft Damage: Substantial 
  • Defining Event: Landing gear not configured 
  • Injuries: 1 Minor, 2 None 
  • Flight Conducted Under: Part 91: General aviation - Positioning

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

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

The business jet landed on the runway at the completion of a visual approach with the landing gear retracted. The airplane slid to a stop, and a post-crash fire ensued which resulted in the airplane sustaining substantial damage. The two pilots, the sole occupants, egressed the airplane successfully without injury. In telephone interviews and written statements, the pilots each stated that there were no mechanical deficiencies with the airplane that would have precluded deployment of the landing gear and a successful landing.

The first officer further stated that the gear warning was only audible in the left seat (Captain’s) headset and was not heard in her headset (right seat) or the overhead speaker, and that the communications panel had a “history” of problems.

Review of the cockpit voice recorder (CVR) confirmed the limitations of the airplane’s communication system, that the crew was aware of them, and that they discussed and debated how to mitigate the system’s limitations.

The review also revealed that during the flights on the day of the accident, the performance of Before-Starting-Engines, Engine Start, Before Taxi, Before Takeoff, Before Landing and other tasks did not comport with the manufacturer’s checklists and were sometimes performed without any verbal communication between crewmembers. The CVR recording further revealed that the captain removed his headset due to a 500Hz “squeal” that he failed to identify as the gear warning horn, and consequently missed the repeating, “too low, gear” aural warning that followed.

- Probable Cause: The flight crew’s failure to properly configure the airplane before landing and the captain’s subsequent failure to recognize the landing gear aural warning, which resulted in a gear-up landing. Contributing to the accident was the flight crew’s inadequate checklist use and crew coordination, and the known diminished capability of the airplane’s communication system.

Loss of engine power (total): Piper PA-24-250 Comanche, N6430P, accident on June 25, 2023 at Alturas Municipal Airport (AAT/KAAT), Alturas, California

  • Location: Alturas, California 
  • Accident Number: WPR23LA239 
  • Date & Time: June 25, 2023, 09:00 Local 
  • Registration: N6430P 
  • Aircraft: Piper PA-24-250 
  • Aircraft Damage: Substantial 
  • Defining Event: Loss of engine power (total) 
  • Injuries: 1 Minor 
  • Flight Conducted Under: Part 91: General aviation - Personal 
https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/192448/pdf

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

On June 25, 2023, at 0900, Pacific daylight time, a Piper PA-24-250, N6430P, was substantially damaged when it was involved in an accident near Alturas, California. The pilot sustained minor injuries. The airplane was operated as a Title 14 Code of Federal Aviation Regulations Part 91 test flight.

The pilot reported that, shortly after takeoff, the airplane’s engine began to run rough, so he returned to the airport, landed uneventfully, parked the airplane, and deplaned his passengers to conduct another preflight inspection. The pilot sampled the fuel, checked for loose spark plugs, and checked the magnetos. The pilot then decided to do an engine run-up and test flight before departing the area with the passengers. After takeoff, about 100 ft above ground level (agl), the engine began to shake violently, and he initiated a turn back to the airport. The engine lost total power, and the airplane landed hard and came to rest upright in the grass adjacent to the runway, resulting in substantial damage to fuselage, both wings, and the right horizontal stabilizer.

Postaccident examination of the engine established mechanical and valvetrain continuity. When the propeller was rotated, the No. 5 ignition harness top lead did not spark. The right magneto was removed and functionally tested with an intermittent spark. The left magneto was also removed, and spark was obtained on all posts during the functional check. Further testing revealed that the intermittent spark from the right magneto could not be duplicated. Disassembly of right magneto revealed about 1/4 of the teeth were separated from the distributor gear, which would likely result in a partial loss of engine power and a rough running engine. No additional evidence of any preexisting mechanical malfunctions that would have precluded normal operation were observed with either magneto. 

- Probable Cause: A loss of engine power due to the failure of the right magneto distributor gear and the pilot’s decision to conduct a test flight with known mechanical issues.

Loss of engine power (partial): Denney Kitfox, N605GK, accident occurred on May 10, 2024, near Powell, Wyoming

  • Location: Powell, Wyoming
  • Accident Number: WPR24LA148
  • Date & Time: May 10, 2024, 10:30 Local
  • Registration: N605GK
  • Aircraft: KJELSRUD GARY KITFOX
  • Aircraft Damage: Substantial
  • Defining Event: Loss of engine power (partial)
  • Injuries: 1 None
  • Flight Conducted Under: Part 91: General aviation - Personal

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

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

On May 10, 2024, about 1030 mountain daylight time, an experimental amateur-built Kitfox airplane, N605GK, was substantially damaged when it was involved in an accident near Powell, Wyoming. The pilot was not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

The pilot of the experimental amateur-built airplane was departing from his private dirt strip when the accident occurred. The airplane exhibited a partial loss of engine power when it was about halfway down the runway. The pilot elected to proceed with the takeoff due to an irrigation canal at the end of the runway. The airplane would not gain altitude and subsequently struck two fences before nosing over and coming to rest inverted in a nearby yard.

Postaccident examination of the engine revealed that one of the two piston-type carburetors had the retaining clip for the jet needle set to the leanest position. The other carburetor was set to the engine manufacturer’s specified position. It is likely that the overly lean setting in one of the carburetors caused the carburetors not to be synchronized, which resulted in the partial loss of engine power during takeoff. According to the pilot, he adjusted the carburetor’s retaining clip to lower the cylinder temperature while he was flying in a different state and did not notice any loss of engine performance. However, this was his first attempted takeoff in Wyoming, that was located at a high elevation. 

- Probable Cause: The pilot’s adjustment of the carburetor to an incorrect setting, which resulted in partial loss of engine power during takeoff.

Fuel exhaustion: Cessna 172K Skyhawk, N84385, accident occurred on June 23, 2023, near Marana, Arizona

  • Location: Marana, Arizona
  • Accident Number: WPR23LA241
  • Date & Time: June 23, 2023, 04:04 Local
  • Registration: N84385 Aircraft: Cessna 172K
  • Aircraft Damage: Substantial
  • Defining Event: Fuel exhaustion
  • Injuries: 1 None
  • Flight Conducted Under: Part 91: General aviation - Personal

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

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

On June 23, 2023, about 0404 mountain daylight time, a Cessna 172K, N84385, was substantially damaged when it was involved in an accident near Marana, Arizona. The pilot was not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

The pilot departed on the cross-country flight with an estimated 38 gallons of fuel onboard. While enroute, the pilot deviated from the direct route to his destination, which increased his enroute time and distance. Flight track data revealed that the airplane arrived near the planned fuel stop, but the pilot stated that he diverted to another airport when he could not activate the runway lights at his intended fuel stop. After travelling for about 3 hours, 46 minutes, a total of about 467 miles, and about 5 miles short of the airport intended to be his second fuel stop, the engine lost total power about the time that the pilot stated that the fuel quantity gauges had “dropped all the way to basically nothing.” The pilot reported that there were no mechanical malfunctions or failures that would have precluded normal operation but suspected that the airplane may have developed a fuel leak. Postaccident examination revealed no evidence of a fuel leak. Based on the available information, it is likely that the loss of power was the result of fuel exhaustion. The Owner’s Manual Cruise and Range Performance Chart revealed that with 38 gallons of fuel, the accident flight’s distance and time enroute were within the chart limits; however, the accident flight consisted mostly of low altitude maneuvering flight that were not addressed by the Owner’s Manual.

Field sobriety testing of the pilot was conducted at the scene of the accident, with no determination of impairment being made by law enforcement at that time. Toxicological testing of the pilot’s blood indicated that the pilot likely had used a cannabis product, cocaine, amphetamine, and MDMA. Although his use of these controlled substances conveyed significant risk of impairment, available evidence was insufficient to determine the precise timing of his substance use, specific impairing effects during the accident flight, or whether such effects contributed to the accident.

- Probable Cause: A total loss of engine power due to fuel exhaustion.

Wednesday, July 09, 2025

Loss of control in flight: Beechcraft E90 King Air, N522MJ, fatal accident occurred on May 17, 2023, near Winslow, Arkansas

  • Location: Winslow, Arkansas
  • Accident Number: CEN23FA190
  • Date & Time: May 17, 2023, 12:37 Local
  • Registration: N522MJ
  • Aircraft: Beech E-90
  • 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/174548/pdf

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

On May 17, 2023, about 1237 central daylight time, a Beech E-90 airplane, N522MJ, was destroyed when it was involved in an accident near Winslow, Arkansas. The pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations (CFR) Part 91 personal flight.

The airplane was being flown to another airport for maintenance work on the autopilot system. Before the flight, the pilot and an avionics technician discussed a roll issue with the airplane’s autopilot and the pilot was advised not to use the autopilot until the issue was resolved. The avionics technician further advised the pilot to wait for good weather to make the flight, but the pilot reportedly had a function back home that he wanted to attend later, on the day of the accident.

Recorded flight track data indicated that most of the flight was uneventful until the airplane began its descent toward the intended destination. During the descent, the airplane encountered overcast clouds that continued to the end of the flight. The pilot was subsequently cleared for an instrument approach to the destination airport. While maneuvering on the approach, the airplane descended below its assigned altitude and the controller issued a low-altitude alert to the pilot. The airplane briefly climbed before it entered a descending right turn that continued to the end of the recorded data.

Calculations based on recorded flight data revealed the airplane was descending over 15,000 feet per minute shortly before impact. The airplane impacted the ground near the final recorded flight track data point, in a near vertical attitude, and was fragmented. Examination of the airplane, engines, and systems did not reveal any preimpact anomalies that would have precluded normal flight.

Based on the available information, the pilot likely was not using the autopilot due to the known issue with the system and, as a result, was hand flying the airplane during the instrument approach. The pilot likely was accustomed to flying the airplane with the automation that the autopilot provided rather than by hand in single-pilot instrument meteorological conditions (IMC). Based on the recorded flight path, it is likely that the pilot became spatially disoriented and lost control of the airplane while intercepting the final approach course for the instrument approach. In addition, the pilot allowed his self-imposed pressure to influence his decision to complete the flight in less-than-ideal weather conditions without a functional autopilot.

Although ethanol was detected in liver and muscle tissue, it is likely that some, or all, of the detected ethanol was from postmortem production. Thus, it is unlikely that ethanol contributed to the accident. Tadalafil, salicylic acid, famotidine, atenolol, and irbesartan were detected in liver and muscle tissue, but it is unlikely that these substances contributed to the accident.

- Probable Cause: The pilot’s poor preflight decision to depart into known instrument meteorological conditions (IMC) without a functional autopilot system, which resulted in spatial disorientation and his failure to maintain aircraft control while flying in IMC during the instrument approach. Contributing to the accident was the pilot’s self-imposed pressure to conduct the flight.

Controlled flight into terr/obj (CFIT): Piper PA-32R-301 Saratoga SP, N43156, fatal accident occurred on January 11, 2023, near Dayton, Virginia

  • Location: Dayton, Virginia
  • Accident Number: ERA23FA108
  • Date & Time: January 11, 2023, 18:09 Local
  • Registration: N43156 Aircraft: Piper PA-32R-301
  • Aircraft Damage: Destroyed
  • Defining Event: Controlled flight into terr/obj (CFIT)
  • Injuries: 1 Fatal
  • Flight Conducted Under: Part 91: General aviation - Personal

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

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

On January 11, 2023, about 1809 eastern standard time, a Piper PA-32R-301 airplane, N43156, was destroyed when it was involved in an accident near Dayton, Virginia. The pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

The pilot departed on the visual flight rules (VFR) cross-country flight at night. Shortly after departing, the pilot established the airplane along a course directly toward the destination airport, climbed to a cruise altitude of about 6,500 ft mean sea level (msl), and contacted air traffic control to request flight following services. About 10 minutes later, the pilot advised the controller that he was descending to 5,500 ft msl, and the controller advised the pilot to “maintain VFR.” No further transmissions were received from the pilot. The airplane descended below 4,500 ft and deviated about 20° left of its previously established course. The airplane continued its steady descent until it impacted mountainous terrain at an elevation about 4,000 ft msl.

The accident site was located less than 500 ft horizontally and 100 ft vertically from the airplane’s last ADS-B-observed position, and the debris path was oriented roughly along the airplane’s previously established course line. The length of the debris path, impact signatures observed on the wreckage, and the degree of fragmentation of the wreckage were all consistent with a controlled flight into terrain-type impact. Examination of the airframe and engine displayed no evidence of any preimpact mechanical malfunctions or failures that would have precluded normal operation.

The accident pilot held a private pilot certificate and had accumulated nearly 1,800 total hours of flight experience, but did not hold an instrument rating. Review of forecast and observed weather conditions revealed that light rain and overcast clouds prevailed along the route of flight, and that the airplane many have been flying through light rain showers around the time when the pilot advised air traffic control that he was descending. AIRMETS valid at the time of the accident warned of mountain obscuration, and surface observations from nearby airports confirmed that there was likely an overcast cloud ceiling around 5,000 ft msl in the area; however, based on the available weather information, it could not be determined whether the pilot encountered instrument meteorological conditions (IMC) in flight or was descending in order to avoid IMC when the impact with terrain occurred. Given the night lighting conditions and the lack of ambient cultural lighting available in the area of the accident site, it is likely that the pilot was unable to see the terrain below.

Postmortem examination of the pilot’s remains identified no significant natural disease. Toxicology testing detected likely subtherapeutic concentrations of the sedating antihistamine, cetirizine, in his blood; however, side effects from low levels of this over-the-counter allergy medication would not likely influence his decision-making ability or his ability to control the airplane. The pilot’s use of cetirizine was likely not a factor in this accident.

- Probable Cause: The pilot’s controlled flight into terrain while descending over mountainous terrain at night.