Wednesday, June 18, 2025

AC/prop/rotor contact w person: Aero AT-4 LSA, N401G, accident occurred on October 25, 2024, at Mallory Airport (WV12), South Charleston, West Virginia

  • Location: South Charleston, West Virginia 
  • Accident Number: ERA25LA032 
  • Date & Time: October 25, 2024, 11:30 Local 
  • Registration: N401G 
  • Aircraft: AERO SP Z O O AT-4 LSA 
  • Aircraft Damage: Minor 
  • Defining Event: AC/prop/rotor contact w person 
  • Injuries: 1 Serious, 2 None 
  • Flight Conducted Under: Part 91: General aviation - Instructional
https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=N401G

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

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

At the conclusion of a short cross-country flight, the flight instructor and student pilot elected to a perform takeoff and landings at their destination airport. The airport was privately owned, the single asphalt runway was 1,900 ft-long by 24 ft-wide, and there was no taxiway parallel to the runway. The flight instructor stated that, he scanned the runway for obstructions and announced over the airport’s Common Traffic Advisory Frequency the airplane’s position in the traffic pattern and their intent to land. No obstructions were observed during the landing. As the pilots taxied the airplane down the recently-paved runway, a person wearing dark-colored clothing “suddenly” came into view. The person was walking along the runway with his back toward the approaching airplane. The airplane’s left wingtip contacted the pedestrian and knocked him forcefully to the ground, resulting in serious injuries. The airplane’s wingtip incurred minor damage. The flight instructor then stopped the airplane, and he and the student rendered aid to the pedestrian until emergency responders arrived. The flight instructor reported that the pedestrian typically carried a hand-held radio that he would use to listen for traffic calls, but he was not carrying it with him on the day of the accident.


- Probable Cause: The pedestrian’s inadequate visual lookout while walking next to an active runway, which resulted in the airplane striking him during taxi.

Cessna S550 Citation S/II, N666DS, fatal accident occurred on May 22, 2025, near Montgomery-Gibbs Executive Airport (MYF/KMYF), San Diego, 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.

  • Location: San Diego, CA 
  • Accident Number: WPR25FA161 
  • Date & Time: May 22, 2025, 03:47 Local 
  • Registration: N666DS 
  • Aircraft: Cessna S550 
  • Injuries: 6 Fatal, 8 Minor 
  • Flight Conducted Under: Part 91: General aviation - Business

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

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

Daviator LLC


On May 22, 2025, at 0347 Pacific daylight time (PDT), a Cessna Citation S550, N666DS, was destroyed when it was involved in an accident near San Diego, California. The pilot and five passengers were fatally injured. Eight people on the ground received minor injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.


The airplane departed Teterboro Airport (TEB), Teterboro, New Jersey, on May 21, about 2309 eastern daylight time (2009 PDT) and arrived at Colonel James Jabara Airport (AAO), Wichita, Kansas, about 0148 central daylight time (2348 PDT). The airplane was refueled with 548 gallons of Jet-A fuel before departing about 0236 central daylight time (0036 PDT) with a destination of Montgomery-Gibbs Executive Airport (MYF), San Diego, California. MYF is a tower-controlled airport between the hours of 0700 and 1800 and operates as an uncontrolled airport during the remaining hours of the day.


As the airplane neared MYF, the pilot checked in on frequency with the Southern California Terminal Radar Approach Control (SOCAL TRACON) controller while at 17,000 ft mean sea level (msl). The controller informed the pilot that the Automated Surface Observing System (ASOS) at MYF was out of service and the pilot acknowledged that he was aware of that. The controller asked the pilot what approach he would like to fly into MYF and the pilot responded that he would like to fly the RNAV (GPS) instrument approach to runway 28R. The pilot did not specify whether he would fly the localizer performance with vertical guidance (LPV) approach or the lateral navigation (LNAV) approach. The pilot was then cleared direct to the NESTY approach fix and instructed to descend to 9,000 ft. The pilot subsequently asked the controller if they could assist in determining the weather conditions at MYF. The controller provided the pilot the weather conditions at Marine Corp Air Station Miramar (NKS), located about 4 miles north of MYF, which was briefed as wind calm, ½ mile visibility, and an indefinite 200 ft ceiling.


The pilot then discussed alternate airport weather conditions with the controller in the event he had to perform a missed approach. He stated he would notify SoCal TRACON of his selection of an alternate airport, but did not do so during the remainder of the flight.


When the airplane was about 10 mi northeast of NESTY, the controller asked the pilot if he was going to “make your descent” and asked if he would like vectors to the south. The pilot replied, “I think we’ll be alright.” The airplane was at about 8,000 ft msl and 270 knots ground speed at that time. The controller informed the pilot that he was 5 miles from NESTY and instructed them to cross NESTY at or above 3,800 ft msl, and that he was cleared the RNAV approach to runway 28R at MYF, which the pilot acknowledged.


ADS-B data showed the airplane subsequently turned abeam NESTY at about 3,750 ft msl and a ground speed of 200 knots, or 191 knots calibrated airspeed (KCAS). The airplane continued to slow and descend and as it crossed PENYY, the final approach fix, at 0344:50 and about an altitude of 2,450 ft msl and ground speed of about 175 knots (167 KCAS).


The pilot made a position call on the MYF common traffic advisory frequency that he was at 3 miles on the approach, followed by the sound of the microphone button being keyed 7 times, consistent with an attempt to activate the pilot-controlled runway lighting.


The airplane crossed PALOS, located 2.9 nm from the runway 28R displaced threshold, at 0346:12, at an altitude of about 1,190 ft msl, and ground speed of about 120 knots (117 KCAS). PALOS has a published minimum crossing altitude at or above 1,380 ft msl. The airplane continued to descend until the ADS-B data ended at 0346:47, at an altitude of about 464 ft msl (about 60 ft agl).


The first identified point of contact (FIPC) was damaged power transmission lines about 90-95 ft above the ground (about 500 ft msl), located about 1.8 nm from the runway 28R displaced threshold. Portions of the left horizontal stabilizer, left elevator, and the vertical stabilizer were located about 200 ft downrange of the lines. The debris field was about 1,200 ft in length and on a magnetic heading of about 300° from the FIPC. The debris field spanned brush-covered terrain and a residential neighborhood.


The main wreckage, which consisted of thermally damaged remnants of the cabin, engines, and left wing, were located on a residential street about 1.6 nm from the runway 28R displaced threshold. The airplane impacted one residential structure and 20 vehicles, which were damaged or destroyed by impact or post impact fire. The wreckage was moved to a secure location for additional examination.


A cockpit voice recorder (CVR) was recovered from the wreckage and was sent to the NTSB Vehicle Recorders Laboratory for examination and audio extraction. The left and right engine Full Authority Digital Engine Control (FADEC) units were recovered and retained for data download. The airplane was not equipped with a flight data recorder (FDR).


The RNAV (GPS) RWY 28 approach allowed for instrument approaches for Category A and B aircraft only (figure 1).


The Flight Standardization Board Report, Rev.2, for the CE-500 series airplanes states:


“13.2 Aircraft Approach Category. The CE-500 Series aircraft are considered a Category B aircraft for the purposes of determining the appropriate instrument approach procedure category in accordance with § 97.3.”


There was a notice to airmen (NOTAM) in effect at the time of the accident informing pilots that the Runway Alignment Indicator (RAI) lights were out of service at MYF and had been so since March 28, 2022. The repairs of the affected RAI lighting components and replacement of the light system have been delayed awaiting completion of an environmental study. All other runway lighting was operable at the time of the accident.


The pilot was based at MYF and underwent a flight evaluation and received an exemption to fly the Cessna S550 single-pilot on December 15, 2024.

Mooney M20TN Acclaim, N242RE, fatal accident occurred on April 26, 2025, near Sparta-Upper Cumberland Regional Airport (SRB/KSRB), Sparta, Tennessee

  • Location: Sparta, TN 
  • Accident Number: ERA25FA187 
  • Date & Time: April 26, 2025, 11:47 Local 
  • Registration: N242RE 
  • Aircraft: Mooney M20TN 
  • Injuries: 3 Fatal 
  • Flight Conducted Under: Part 91: General aviation - Personal
https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/200069/pdf

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

On April 26, 2025, about 1147 central daylight time, a Mooney M20TN, N242RE, was substantially damaged when it was involved in an accident near Sparta, Tennessee. The private pilot and two passengers were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

Earlier that day the pilot flew from the Upper Cumberland Regional Airport (SRB), Sparta, Tennessee, to Shelby County Airport (EET), Alabaster, Alabama, where he landed, boarded 2 passengers and some cargo, then departed to return to SRB.

According to Federal Aviation Administration (FAA) preliminary air traffic control audio and Automatic Dependent Surveillance – Broadcast (ADS-B) data, after takeoff about 1039 the flight proceeded toward SRB while maintaining contact with several air traffic control facilities along the route of flight. Approaching SRB from the southwest, at 1136:55, the Sector 41 Radar Position controller of the Memphis Air Route Traffic Control Center instructed the pilot to cross the WENUB (intermediate fix/initial approach fix) at or above 4,000 ft and cleared the flight for the RNAV runway 4 approach to SRB. The flight continued direct to WENUB then turned to a northeast direction while flying toward SRB. At 1143:52, when the flight was about 6.2 nautical miles from the approach end of runway 4, the pilot cancelled his instrument flight rules clearance and informed the controller that the cloud bases were at 3,000 ft. Personnel at SRB reported hearing the pilot announce on the SRB common traffic advisory frequency that the flight was 11 miles and then 3 miles from SRB. There was no reported distress call made by the pilot.

The flight continued direct towards SRB until 1146:56, after which time a slight deviation to the right occurred. A witness who was located about .3 nautical mile west-northwest of the accident site reported there was, “some kind of trouble the engine was cutting in and out like it was out of gas.” She observed the airplane was in level flight then diverted her attention and then heard the sound of a crash.

During the final portion of the flight the airplane flew over a field with crop and impacted into trees and a creek about 1.5 nautical miles southwest from the approach end of runway 4. Initial examination of the engine revealed evidence of internal catastrophic malfunction. The No. 3 cylinder connecting rod was fractured and not attached at either end. The No. 3 cylinder connecting rod journal did not display any evidence of lack of lubrication. The engine was retained for further examination.

A Stratus 3 receiver was located in the wreckage and retained for read-out by the NTSB Vehicle Recorders Division. Additionally, the shoulder harness airbag electronic module assembly, a portion of the pitch trim system and an annunciator panel were also retained for further examination.

Lancair 360, N77LH, accident occurred on June 11, 2025, at Fort Stockton–Pecos County Airport (FST/KFST), Fort Stockton, Texas

  • Location: Fort Stockton, TX 
  • Accident Number: CEN25LA205 
  • Date & Time: June 11, 2025, 21:45 Local 
  • Registration: N77LH 
  • Aircraft: Lancair 360 
  • Injuries: 1 None 
  • Flight Conducted Under: Part 91: General aviation - Personal
https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/200314/pdf

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

On June 11, 2025, about 2145 central daylight time, a Lancair 360 airplane, N77LH, was destroyed when it was involved in an accident near Fort Stockton, Texas. The airline transport pilot was not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.


According to the pilot, he had recently purchased the airplane in California, and he was performing a cross-country flight to his home base in Florida. The airplane stopped at the El Paso International Airport (ELP), El Paso, Texas to refuel. The airplane departed from ELP about 1940 mountain daylight time. While enroute to the San Antonio International Airport, San Antonio, Texas, the pilot smelled smoke in the cockpit. The pilot contacted air traffic control and changed his destination airport to the Fort Stockton-Pecos County Airport, Fort Stockton, Texas, due to the emergency. Once the pilot maneuvered the airplane for landing on runway 12, the cockpit was filled with smoke, and flames were emitting from underneath the instrument panel.


During the landing, the pilot reported he did not have brake authority, and the airplane departed the runway to the left. The airplane came to rest upright against a barbed wire fence along the airport perimeter. The pilot was able to egress from the airplane without further incident.


The fire consumed the engine compartment, part of the fuselage, and the left wing. The wreckage was recovered from the accident site, and it was transported to a secure location for future examination.


The experimental airplane was built from a kit in 1999. The composite construction airplane was equipped with a Lycoming Engines O-360-A1A reciprocating engine. The airplane had a condition inspection performed by a mechanic on the airframe and the engine on June 9, 2025. During the inspection, it was noted that the airframe had accumulated 440.4 hours total time, and the engine had accumulated 2,220.9 hours total time (with 911.9 hours since overhaul).


The pilot reported that the airplane maintenance records and the historical airplane build records were stored in the baggage compartment and consumed by the fire.

Rans S-20 Raven, N327KM, accident occurred on May 27, 2025, near Fairfield, Utah

  • Location: Fairfield, UT 
  • Accident Number: WPR25LA163 
  • Date & Time: May 27, 2025, 13:30 Local 
  • Registration: N327KM 
  • Aircraft: RANS S20 
  • Injuries: 1 None 
  • Flight Conducted Under: Part 91: General aviation - Personal

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

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


On May 27, 2025, about 1330 mountain daylight time, an experimental amateur-built RANS S20 Raven, N327KM, was substantially damaged when it was involved in an accident near Fairfield, Utah. The pilot was not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.


The pilot reported that shortly after departing the runway at the West Desert Airpark (UT9), Fairfield, Utah, about 800 ft above ground level, the airplane had a total loss of engine power followed by an error message on the multi function display. The pilot attempted to restart the engine but was unsuccessful, and initiated a forced landing on a field. The airplane landed hard on a vegetated field and sustained substantial damage to the fuselage.


The airplane was recovered to a secure location for further examination

Tuesday, June 17, 2025

Zenair STOL CH 701, N514JG, fatal accident occurred on May 25, 2025, near Germack Airport (7D9), Geneva, Ohio

 

  • Location: Geneva, OH
  • Accident Number: ERA25FA211 
  • Date & Time: May 25, 2025, 10:07 Local 
  • Registration: N514JG 
  • Aircraft: Zenith STOL CH701 
  • Injuries: 1 Fatal, 1 Serious 
  • Flight Conducted Under: Part 91: General aviation - Flight test

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

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

On May 25, 2025, about 1007 eastern daylight time, an experimental, amateur-built Zenith STOL CH701, N514JG, was substantially damaged when it was involved in an accident near Geneva, Ohio. The pilot was fatally injured and the pilot-rated passenger sustained serious injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 test flight.


According to the pilot-rated passenger, who was also the owner of the airplane, he purchased the airplane in October 2024. He and the pilot subsequently removed the wings and transported the airplane to Germack Airport (7D9), Geneva, Ohio. The purpose of the flight was to conduct a test flight following the airplane’s reassembly and inspection. During the preflight inspection, the pilot ensured the flight controls were free and correct and no anomalies were noted during the engine run-up check.


The passenger reported that during the initial takeoff roll, “the airplane didn’t seem like it wanted to fly”, and the takeoff was aborted. The pilot taxied the airplane back to the departure end of runway 19 and initiated a second takeoff. The airplane became airborne approximately 1,800 ft down the 3,260-ft-long paved runway. During the initial climb, at an altitude of about 150 ft above ground level (agl), the airplane was unable to gain additional altitude. The pilot then pitched the nose down to gain airspeed, but the airplane was unable to maintain level flight. A surveillance video captured the engine sound consistent with operating power as the airplane descended to the trees in a nose-up attitude (see figure 1).

The airplane impacted trees and terrain about ½ mile southwest of the departure end of the runway. The first identified point of impact was a tree about 40 ft agl. The airplane came to rest in an upright position on a heading of about 330°, and about 30 ft from the initial point of impact. Several tree limbs located within the wreckage area exhibited angular cuts with black transfer marks in their separation areas. A postcrash fire ensued and consumed majority of the fuselage and right-wing fuel tank. All major components of the airplane were accounted for within the wreckage area. Both wings were partially separated from the fuselage and exhibited semicircular impressions to their leading edges. Flight control continuity was established from the cockpit controls to the rudder and elevator. The flaperon control was observed retracted and flight control continuity was established from the cockpit to the flaperon mixer assembly and bellcranks. The left and right flaperon control rods were impact separated from the flaperons. 


About 10 gallons of fuel was recovered from the left wing. A fuel sample from the left wing was free of contaminants, and a test utilizing water-finding paste was negative for the presence of water. The fuel valve was noted in the on position and was confirmed functional during a field test using low-pressure air. Majority of the fuselage mounted fuel lines were thermally destroyed. 


The engine remained attached to the fuselage with thermal damage noted to the accessory area of the engine. The spark plug electrodes were undamaged and displayed normal wear and coloration. Both magnetos produced spark from their ignition leads during hand rotation of the attached propeller. Crankshaft continuity was established from the propeller flange to the rear gears. Valvetrain continuity was established, and compression and suction were attained from all four cylinders. No anomalies were noted to the induction air filter or exhaust system. The throttle control cable remained attached to the carburetor and was observed in the open position. The mixture control cable remained attached and was noted in the rich position. The carburetor fuel inlet screen was clear of debris. The three-bladed composite propeller remained attached to the engine. One propeller blade was separated at the hub area and the remaining two blades exhibited impact damage to their leading edges.


The wreckage was retained for further examination.

Stinson 108 Voyager, N40518, fatal accident occurred on June 3, 2025, near near Sugar Valley Airport (5NC2), Farmington, North Carolina

  • Location: Farmington, NC 
  • Accident Number: CEN25FA194 
  • Date & Time: June 3, 2025, 11:45 Local 
  • Registration: N40158 
  • Aircraft: UNIVERSAL STINSON 108 
  • Injuries: 2 Fatal, 1 Serious 
  • Flight Conducted Under: Part 91: General aviation - Personal

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

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

On June 3, 2025, about 1145 eastern daylight time, a Universal Stinson 108 airplane, N40518 was destroyed when it was involved in an accident near Farmington, North Carolina. The pilot and one passenger were fatally injured, and one passenger was seriously injured. The airplane was operated under the provisions of Title 14 Code of Federal Regulations Part 91 as a personal flight.


The airplane departed runway 2 at the Sugar Valley Airport (5NC2), Mocksville, North Carolina, and flew around the traffic pattern. Upon turning base leg for runway 2, the UNICOM operator, who was looking out the airport office window facing southeast, advised the pilot that there was a turtle on the runway. According to the UNICOM operator, the pilot landed about 1,400 ft down the 2,424 ft runway and then lifted the right main wheel to avoid the turtle. The UNICOM operator stated that she heard the pilot advance the throttle after he raised the right wheel. The airplane left her point of view, and she was unable to see the airplane after that. 


A man cutting the grass at the end of runway 2 reported that he saw the turtle on the runway and the pilot raised the right wheel to avoid the turtle. After that, the wings began to rock back and forth. Then the airplane took off again, but he lost site of the airplane when it passed behind a hangar. The airplane disappeared just over the trees on the northeast side of the runway and then he heard a loud crash and saw smoke. 


The airplane impacted a heavily forested area about 255 ft northeast of the departure end of runway 2. A post impact fire ensued. The airplane came to rest on a heading of about 100°. 


The airplane was wedged between several trees and remained in one piece except for a few pieces of fabric that were found in an adjacent stream next to the accident site. The fabric on the fuselage, cowling, and wings was completely burned off and the airplane frame was visible. The fabric on the vertical stabilizer and horizontal stabilizer was intact; however, parts of the vertical stabilizer fabric were melted. The metal rudder and elevator were not fire damaged.


The airplane came to rest on its left side with the left wing folded underneath the fuselage and the right wing bent aft. Control cable continuity was confirmed to the rudder, elevator, and right aileron. Due to impact damage, cable continuity could not be confirmed to the left aileron or flaps. 


The airplane wreckage and engine were retained for further examination.