Wednesday, March 04, 2026

VFR encounter with IMC: Zenith STOL CH 701, N4209W, fatal accident occurred on December 29, 2023, near Marienville, Pennsylvania

  • Location: Marienville, Pennsylvania 
  • Accident Number: ERA24FA077 
  • Date & Time: December 29, 2023, 21:57 Local 
  • Registration: N4209W 
  • Aircraft: Zenith STOL CH701 
  • Aircraft Damage: Destroyed 
  • Defining Event: VFR encounter with IMC 
  • Injuries: 1 Fatal 
  • Flight Conducted Under: Part 91: General aviation - Personal

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

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

On December 29, 2023, about 2157 eastern standard time, an experimental, amateur-built Zenith STOL CH 701, N4209W, was destroyed when it was involved in an accident near Marienville, Pennsylvania. The private pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

Prior to departing on the night visual flight rules (VFR) flight, the non-instrument-rated pilot accessed a flight planning application to plot a route for the cross-country flight, but did not obtain a weather briefing, nor did he obtain a weather briefing from any other flight service provider. ADS-B data showed the pilot departed and established the airplane at an altitude of about 3,100 ft mean sea level (msl). Weather reporting along the route of flight showed the airplane flying through areas of cloud cover with bases ranging between 1,700 and 3,300 ft msl, and a weather model estimated that cloud bases were about 3,000 ft msl near accident site around the time of the accident.

About 90 seconds before the last recorded ADS-B data, weather radar indicated that the airplane, flew into an area of developing light snow. About this time, the airplane began a left turn while flying at 2,900 ft msl. The left turn tightened, and the airplane climbed to about 3,350 msl, before it entered a steep descent in a tight left spiral. The airplane then impacted trees and terrain. Postaccident examination of the airplane revealed no evidence of any preimpact mechanical malfunctions or failures that would preclude normal operation.

The circumstances of the accident—visual flight in dark night lighting conditions under an overcast cloud ceiling into an area of deteriorating visibility due to snow by a non-instrumentrated pilot, which culminated in a steep, turning, un arrested descent—are consistent with the pilot experiencing a form of spatial disorientation known as the somatogyral illusion or graveyard spiral. After encountering the reduced visibility conditions, the pilot likely did not perceive that the airplane was turning and pulled back on the flight controls, tightening the spiral and increasing the descent rate, which ultimately continued to ground contact Postmortem toxicological testing indicated that the pilot had used methamphetamine, which has substantial potential to result in impairment. The degree to which the effects of methamphetamine contributed to the pilot’s decision to continue visual flight into deteriorating visibility conditions at night, could not be determined with certainty.

- Probable Cause: The pilot’s decision to continue visual flight into deteriorating visibility conditions at night, which resulted in spatial disorientation and subsequent descent that continued to ground contact. 

Fuel contamination: Grumman GA-7 Cougar, N887CC, fatal accident occurred on February 1, 2024, in Coatesville, Pennsylvania


  • Location: Coatesville, Pennsylvania 
  • Accident Number: ERA24FA103 
  • Date & Time: February 1, 2024, 13:30 Local 
  • Registration: N887CC 
  • Aircraft: GRUMMAN AMERICAN AVN. CORP. GA-7 
  • Aircraft Damage: Substantial 
  • Defining Event: Fuel contamination 
  • Injuries: 1 Fatal Flight Conducted Under: Part 91: General aviation - Positioning

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

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

On February 1, 2024, about 1330 eastern standard time, a Grumman American Aviation Corporation GA-7, N887CC, was substantially damaged when it was involved in an accident near Coatesville, Pennsylvania. The private pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 positioning flight.

The most recent annual inspection was completed about 45 days before the accident. After completion of the annual inspection the airplane was flown to another airport, where it would be the subject of a restoration project and then sold. The airplane then sat outside, and during that period the airport received about 10 inches of precipitation. The purpose of the accident flight was to deliver the airplane to its new owner.

According to company and airport employees, the pilot arrived at the departure airport around 1230 and made it clear that he was “in a hurry,” as he had a return flight booked for 1800 that evening. According to witnesses, the airplane was fueled with 80 gallons of 100LL fuel and the pilot performed a very brief and incomplete preflight inspection, which did not include obtaining fuel samples from either of the airplane’s fuel tanks. During takeoff, the airplane’s engine “popped,” which was followed by sputtering and an aggressive turn to the right (consistent with a Vmc roll), before it disappeared behind the trees.

Postaccident examination of the airplane revealed that both fuel tanks were intact and fuel was observed in the tanks. Fuel samples taken from the sump tank, engine-driven fuel pump, and the carburetor bowl on the airplane’s right side all contained water and debris.

The examination also revealed that the right fuel cap was missing its gasket, which was required, and should have been detected during the most recent annual inspection.

- Probable Cause: The pilot’s inadequate preflight inspection, which resulted in a loss of engine power due to water-contaminated fuel, and his subsequent loss of control. Contributing to the accident was an inadequate annual maintenance inspection, during which maintenance personnel failed to detect and replace the missing right fuel cap gasket.

Low altitude operation/event: Bellanca 7GCBC Citabria, N8569V, fatal accident occurred on January 12, 2025, near Batesville, Arkansas

  • Location: Batesville, Arkansas 
  • Accident Number: CEN25LA075 
  • Date & Time: January 12, 2025, 14:15 Local 
  • Registration: N8569V 
  • Aircraft: Bellanca 7GCBC 
  • Aircraft Damage: Substantial 
  • Defining Event: Low altitude operation/event 
  • Injuries: 1 Fatal 
  • Flight Conducted Under: Part 91: General aviation - Personal

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

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

On January 12, 2025, about 1415 central standard time, a Bellanca 7GCBC, N8569V, was substantially damaged when it was involved in an accident near Batesville, Arkansas. The pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. 

The pilot was conducting a local flight when the airplane struck and became entangled in a high-tension power line, leaving the airplane suspended nose-down about 130 ft above the ground. The pilot of a second airplane that was flying behind and higher than the accident airplane witnessed the collision, and his passenger called 911 to report it. After landing at a nearby airport, the second pilot and his passenger went to the accident site, where the accident pilot remained inside the suspended airplane awaiting rescue. He stated that he  heard the accident pilot say that he did not see the power lines until it was too late due to the snowy background.

Postaccident examination of the airplane revealed no preimpact mechanical malfunction or failure that would have prevented normal operation. The sectional chart current at the time of the accident depicted the location of the power lines.

The accident pilot sustained fatal injuries when attempting to egress the suspended airplane using harness and rope provided by persons on the ground. Toxicology results indicated that the accident pilot had used multiple sedating medications. Such medications have the potential to cause cognitive and psychomotor impairment, especially when combined. However, no detailed determination about impairment during the accident flight or subsequent rescue effort can be made from the reviewed toxicology results alone. Further, considering that the detected medications all may be used to treat insomnia, whether the pilot was experiencing the impairing effects of disordered sleep also is unknown.

- Probable Cause: The pilot’s failure to maintain clearance from powerlines while flying at low altitude. 

Loss of control in flight: Beechcraft 95-B55 Baron, N7345R, fatal accident occurred on January 14, 2024, near Leyden, Massachusetts

  • Location: Leyden, Massachusetts 
  • Accident Number: ERA24FA088 
  • Date & Time: January 14, 2024, 11:25 UTC 
  • Registration: N7345R 
  • Aircraft: Beech 95-B55 (T42A) 
  • Aircraft Damage: Substantial 
  • Defining Event: Loss of control in flight 
  • Injuries: 3 Fatal 
  • Flight Conducted Under: Part 91: General aviation - Instructional

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

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

On January 14, 2024, at 1125 eastern standard time, a Beechcraft 95-B-55 airplane, N7345R, was substantially damaged when it impacted terrain near Leyden, Massachusetts. The flight instructor, commercial pilot, and the passenger were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 instructional flight.

The flight instructor, commercial-certificated/multi-engine-rated pilot receiving instruction, and a passenger departed on a local flight to practice maneuvers so the pilot could obtain currency in a multi-engine airplane. The pilot receiving instruction had not flown a twin-engine airplane in almost 11 years. This was his first time flying this make/model airplane, and with this flight instructor.

Shortly after departure, the airplane climbed to about 3,000 to 3,300 ft mean sea level (msl) and made four alternating left and right 360° turns. After the fourth 360° turn, the airplane began to climb, reaching an altitude of about 4,000 ft msl. The airplane then entered a rapid descent and impacted terrain. Witnesses described that the airplane “corkscrewed” or “spiraled” as it descended nose-down toward the ground. Other witnesses said the airplane sounded as if it were having engine trouble.

The airplane came to rest upright with evidence of little forward movement, consistent with the airplane being in a flat attitude at the time of impact. All major components of the airplane were accounted for at the site, and there was no postimpact fire. Photos taken by first responders revealed some airframe icing on the airplane’s left wing, left engine cowling, and nose baggage area. Weather at the time included wind gusts up to 23 kts, with an active AIRMET (Airman Meteorological Information) for icing and a SIGMET (Significant Meteorological Information) for severe turbulence between 3,000 and 16,000 ft msl. A postaccident examination of the airplane and engines revealed no preimpact mechanical deficiency that would have precluded normal operation.

Based on the witness’ description of the airplane’s descent and the condition of the wreckage, the airplane entered a spin from which it was not recovered. Since an airplane must first be in a stalled condition before it can spin, either an inadvertent or deliberate stall must have immediately preceded the spin.

Further, because a spin entry requires the presence or introduction of a yawing moment at the stall, the NTSB conducted an airplane performance study that considered possible conditions and scenarios that could affect the airplane’s stall performance and produce a yawing moment. These considerations included airframe ice contamination, operation of the engines at different thrust levels (such as during a Vmc demonstration, which is commonly performed during multi-engine airplane instructional flights to demonstrate the airplane’s minimum control airspeed with one engine deliberately shut down or set to minimum thrust), and improper stall recovery technique.

The study determined that the airplane entered two stalls in the minute before the accident. The airplane was successfully recovered from the first stall but not the second, during which the spin developed and continued to ground impact. The study determined that, during each stall, the airplane achieved the nominal flaps-up stall speed outlined in the airplane flight manual (AFM). As such, there was no evidence that airframe icing contamination adversely affected the airplane’s stall speed or other aerodynamic characteristics, such as asymmetric stall behavior (one wing stalling before the other).

In addition, the study determined that the computed engine power required during the time surrounding the first stall exceeded the power available from one engine, indicating that both engines must have been operating at the time of the first stall. This was inconsistent with a scenario involving a Vmc demonstration.

The study determined that, at the time of the second stall, the required engine power was reduced compared to the first stall. Given that this second stall occurred less than 30 seconds after the first, the performance study concluded that it was unlikely that the second stall was associated with an attempted Vmc demonstration.

Having excluded an asymmetrical aerodynamic condition and asymmetrical engine thrust as potential sources of the yawing moment that induced the airplane’s spin, the study concluded that the spin may have resulted from an improper stall recovery technique, possibly involving an excessive or inadvertent rudder input. FAA guidance for pilots related to spin avoidance in multi-engine airplanes emphasizes initiating stall recovery (reducing the airplane’s angle of attack) as soon as the airplane reaches the stall warning, such as an aural alert or buffet. The guidance references stall practice among the scenarios in which “spin awareness must be at its greatest.”

Toxicological testing of the flight instructor identified that he had used multiple central nervous system (CNS) depressants, including medications for anxiety and depression. Although postmortem drug levels do not reliably predict specific impairing effects in this case, the presence of multiple CNS depressants increased the risk of adverse CNS effects, such as increased sedation, decreased alertness, slowed reflexes, and impaired concentration; these effects can potentially occur despite chronic use. The status of the flight instructor’s underlying condition and its response to treatment could not be determined.

As pilot-in-command, the flight instructor had ultimate responsibility for the safety of the flight. It is possible that the flight instructor’s judgment may have been adversely affected by his substance use or underlying condition, or both. Also, despite the predictable need to be immediately ready to react to prevent a spin, the experienced flight instructor failed to prevent the spin. The adverse effects of his substance use, the associated underlying condition, or both likely diminished his capacity to act in a timely and appropriate manner, although a more specific determination of the individual contributions of specific medical factors is not possible based on the available evidence.

- Probable Cause: The flight instructor’s failure to maintain airplane control during a stall, which resulted in an inadvertent spin from which the airplane was not recovered. Contributing to the accident were the overall effect of the flight instructor’s use of multiple central nervous system depressants, the associated underlying conditions they treated, or both. 

Mooney M20G Statesman, N6915N, incident occurred on February 28, 2026, at Fort Meade Executive Airport (FME/KFME), Fort Meade/Odenton, Maryland

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

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

- History of Flight:
On February 28, 2026, at about 1631 local time, a Mooney M20G Statesman, N6915N, sustained unknown damage when it was involved in an incident at Fort Meade Executive Airport (FME/KFME), Fort Meade/Odenton, Maryland. The pilot was not injured. The local flight originated from KFME at 1549 LT.

The FAA reported: "Aircraft landed gearup." ADS-B data show that the airplane was conducting several touch and go(es) and was coming in for a landing on runway 10.

AeroVironment Nano Hummingbird UAS accident occurred on March 2, 2026, near Kemah, Texas

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

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

- History of Flight:
On March 2, 2026, at about 1413 local time, an AeroVironment Nano Hummingbird UAS was destroyed when it was involved in an accident near Kemah, Texas. There were no injuries.

The FAA reported: "Aircraft crashed while returning to base and post crash fire."

Figure: AeroVironment Nano Hummingbird UAS

MightyFly MF-100, N258MF, accident occurred on March 2, 2026, at Castle Airport (MER/KMER), Atwater, California

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

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

- History of Flight:
On March 2, 2026, at about 1357 local time, a MightyFly MF-100 eVTOL, N258MF, registered to MightyFly Inc out of San Leandro, CA, was destroyed when it was involved in an accident at Castle Airport (MER/KMER), Atwater, California. There were no injuries.

Figure 1: MightFly MF-100

The FAA reported: "Aircraft on autonomous test flight, the wind caused uas to descend and crashed into the ground and caught fire." and reported the accident time as 1457 LT. However, ADS-B data show that the UAS taxied from the ramp and was traveling over the taxiway at KMER when it entered a right hand descent at around 1357 LT (see figures). At the time, the winds were from 350° at 9 knots. The NTSB is investigating.

Figure 1: Overall review of ADS-B data

Figure 2: End of track

- Weather:

METAR KMER 022055Z 35009KT 10SM CLR

METAR KMER 022155Z 35009KT 10SM CLR

Lindstrand Balloons 260A, N261RR, accident occurred on March 2, 2026, near Casa Grande, Arizona

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

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

- History of Flight:
On March 2, 2026, at about 0730 local time, a Lindstrand 260A hot air balloon, N261RR, sustained substantial damage when it was involved in an accident near Casa Grande, Arizona. The pilot and twelve passengers were not injured, and one passenger sustained minor injuries.

The FAA reported: "Hot air balloon made contact with a hilltop and then landed safely in a field."