Friday, September 26, 2025

Piper PA-46-500TP Malibu Meridian, N388TW, accident occurred on September 25, 2025, at Rusk County Airport (RFI/KRFI), Henderson, 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=N831VA

- History of Flight:
September 25, 2025, at about 1128 local time, a Piper PA-46-500TP Malibu Meridian, N388TW, registered to TL Lobo Group LLC out of Rockwall, TX, sustained substantial damage when it landed gearup on runway 35 at Rusk County Airport (RFI/KRFI), Henderson, Texas. The sole pilot onboard was not injured. The personal flight originated from Ralph M. Hall/Rockwall Municipal Airport (F46), Rockwall, Texas, at about 1058 LT.

Maule M-5-235C Lunar Rocket, N343GA, accident occurred on September 13, 2025, near Point MacKenzie, Alaska

  • Location: Point MacKenzie, AK 
  • Accident Number: ANC25LA105 
  • Date & Time: September 13, 2025, 12:28 Local 
  • Registration: N343GA 
  • Aircraft: Maule M-5-235C 
  • Injuries: 1 Serious 
  • Flight Conducted Under: Part 91: General aviation - Personal

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

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

On September 13, 2025, about 12:28 Alaska daylight time, a Maule M5-235C airplane, N343GA, was substantially damaged when it was involved in an accident near Point McKenzie, Alaska. The commercial pilot sustained serious injuries. The airplane was operated under Title 14 Code of Federal Regulations as a Part 91 personal flight.

According to the pilot, the airplane departed Merrill Field (MRI) Anchorage, Alaska at around 12:20 and was en route to land at a private strip near Point McKenzie Alaska. The pilot reported that he was going to land to the south and was on the downwind leg of the traffic pattern at about 80 knots with one notch of flaps extended. As the pilot maneuvered the airplane on the base leg of the traffic pattern about 300-400 feet agl (above ground level), he slowed to about 65 knots and added the second notch of flaps, the airplane immediately rolled to the left. The pilot attempted to recover the airplane; however, the airplane impacted the ground and came to rest on a northerly heading (see figure 1).


The wreckage has been recovered, and a postaccident wreckage examination is pending.

Tuesday, September 23, 2025

Aircraft structural failure: Boeing 737 MAX 9, N27515, accident occurred on October 24, 2024, at Houston-George Bush Intercontinental Airport (IAH/KIAH), Houston, Texas

  • Location: Houston, Texas 
  • Accident Number: DCA25LA025 
  • Date & Time: October 24, 2024, 12:52 Local 
  • Registration: N27515 
  • Aircraft: Boeing 737-9 
  • Aircraft Damage: Substantial 
  • Defining Event: Aircraft structural failure 
  • Injuries: 145 None 
  • Flight Conducted Under: Part 121: Air carrier - Scheduled

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

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

United Airlines flight 1181 experienced a failure of the number 3 and number 4 tires on the right main landing gear (MLG) during landing on runway 26L at George Bush Intercontinental/Houston Airport (IAH), Houston, Texas. The airplane exited the runway and stopped on a high-speed taxiway, and the passengers were deplaned and bussed to the terminal. Post landing inspection revealed substantial damage to the aircraft fuselage skin.

The captain was the pilot flying and the first officer (FO) was the pilot monitoring for the entire duration of the flight. During preflight preparations for departure from Harry Reid International Airport (LAS), Las Vegas, Nevada, both pilots reviewed the flight release and noted three Minimum Equipment List (MEL) items: the autobrake system, the antiskid system, and a coffee maker. The autobrake and antiskid systems had been deferred earlier that morning due to maintenance issues, specifically an antiskid alert light that failed to test correctly.

Given these deferrals, the crew stated they reviewed the enroute and destination weather conditions and reviewed operational limitations with the MEL items. Weather was visual flight rules (VFR) at both departure and destination airports. The crew determined that all MELrelated limitations were satisfied, including the need for a dry runway, no tailwind, use of flaps 40 for landing, and sufficient landing distance. The aircraft departed LAS without incident.

During descent into Houston, the crew stated they conducted the approach briefing, incorporating the limitations due to the MEL items. The FO noted a slight tailwind component on Runway 26L and requested an opposite-direction landing due to the autobrake and antiskid systems not available. However, Houston approach air traffic control (ATC) was unable to accommodate the request due to traffic volume and airspace restrictions. Winds were later reported as calm, and the crew proceeded with a visual approach to Runway 26L. When the FO did a final wind check with the tower, they were informed of a direct left-to-right crosswind relative to the runway, at 8 knots.

Both the captain and FO described the landing as soft and initially uneventful. The speed brakes deployed automatically, and the captain stated he applied brakes and activated the thrust reversers. However, shortly after the reversers were deployed, the captain perceived an abnormal condition, suspecting a tire failure due to the unusual noise and slight lateral swaying. The FO described the sensation as skidding followed by grinding and noted that the aircraft did not roll smoothly below 10 knots, with a right-wing-down lean. The captain suspected a blown tire and steered the aircraft off the runway and onto a high-speed taxiway.

A review of the FDR data for the landing show that as the pitch angle was reduced, the brake pressure began to rise to about 500 psi, prior to the right MLG air/ground switch changing to “ground”. After the right MLG was on the ground, the brake pressure continued to rise, peaking at about 1500 psi as the left MLG air/ground switch changed to “ground”. Brake pressure then eased to about 1000 psi as the nose gear air/ground switch changed to “ground” and the vertical acceleration peaked at about 1.3g. About one second later, there was a second spike in vertical acceleration to 1.3g, concurrent with an increased roll attitude to about 2 degrees right wing down, consistent with the failure of the right MLG tires.

Since the autobraking and antiskid systems were disabled, the flight crew had to manually apply brakes during the landing. The FDR data showed that the brake application happened before all three landing gear had changed to “ground” status, and likely before the wheels had an opportunity to fully spin up. The early application of the brakes during the landing likely contributed to the failure of the tires on the right MLG.

The ATC tower reported seeing smoke emanating from the aircraft during rollout, prompting the crew to request emergency vehicles. Upon stopping, ground personnel confirmed that both tires on the right MLG were severely damaged. The crew started the auxiliary power unit (APU), shut down the engines, and completed the after-landing and parking checklists. Passengers were informed of the situation and deplaned via air stairs approximately 40–45 minutes after landing. Buses transported all passengers and crew to the terminal. No injuries were reported.

Post landing inspection showed an impact dent on the fuselage above the right MLG. The affected area is identified in the United Airlines structural repair manual (SRM) as a principal structural element and required repair utilizing the techniques identified in the SRM. Inspection of the frames, stringers, and shear ties near the damaged area showed no damage to any adjacent areas. 

- Probable Cause: Brake application before all three landing gears were on the ground, which caused the failure of the right main landing gear tires and resulted in tire fragments impacting the fuselage.

Robinson R44 Raven II, N831VA, accident occurred on September 19, 2025, near Alvord, 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=N831VA

- History of Flight:
September 19, 2025, at about 1007 local time, a Robinson R44 Raven II, N831VA, registered to Travel Systems LLC out of Boerne, TX, and being operated by a 
FAR 141 Pilot School, sustained unknown, but apparent substantial damage when it was involved in an accident near Alvord, Texas. The two occupants onboard were not injured. The flight originated from Fort Worth Alliance Airport (AFW/KAFW), Fort Worth, Texas, at about 0942 LT.

The FAA reported that: "Aircraft during landing maneuvers, the main rotor blades separated the tail boom from the fuselage."

Figure 1: ADS-B Exchange data of end of track

Cessna 182H Skylane, N2383X, and Grumman American AA-5B Tiger, N81317, accident occurred on September 19, 2025, at Plymouth Municipal Airport (PYM/KPYM), Plymouth, Massachusetts

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=N2383X

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

- History of Flight:
September 19, 2025, at about 0700 local time, a Cessna 182H Skylane, N2383X, registered to Como Aviation LLC out of South Weymouth, MA, and a privately-registered Grumman American AA-5B Tiger, N81317, were involved in a ground collision while both were taxiing for departure at Plymouth Municipal Airport (PYM/KPYM), Plymouth, Massachusetts. The sole pilot onboard each airplane was not was injured. Both airplanes were being operated as a Title 14 Code of Federal Regulations Part 91 personal flights.

The FAA reported that the Grumman was on the ramp taxiing for departure when its propeller struck the right wing of the Cessna. The Grumman sustained minor damage, and the Cessna sustained substantial damage.

Monday, September 22, 2025

Vanilla Unmanned VA-001, N246VU, accident occurred on August 20, 2025, near Ninilchik, Alaska

  • Location: Ninilchik, AK 
  • Accident Number: ANC25LA091 
  • Date & Time: August 20, 2025, 06:32 Local 
  • Registration: N246VU 
  • Aircraft: VU HOLDINGS LLC/DBA VANILLA UN VA 001 
  • Injuries: 2 None 
  • Flight Conducted Under: Public aircraft

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

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

On August 20, 2025, at about 0632 Alaska daylight time, a Platform Aerospace VA 001 Unmanned Aerial System (UAS), N246VU, was substantially damaged when it was involved in an accident on a beachside cliff near Ninilchik, Alaska. The aircraft was unmanned. The aircraft was operated under Title 14 Code of Federal Regulations as a Public Use Armed Forces Aircraft on a Certificate of Authorization (COA) Waiver.

According to the operator, the airplane was returning to Kenai Municipal Airport in Kenai Alaska after a 72-hour continuous flight to Shemya Island. While flying over open water at an altitude of 5500 ft msl, less than an hour from its expected return, the UAS experienced a total loss of engine power and began an uncommanded descent. While troubleshooting, the flight crew was able to briefly restore partial power after opening the wing fuel drain solenoid. However, this was not enough to maintain altitude. After further attempts to restore engine power were unsuccessful, the flight crew shutdown the engine, to arrest the descent rate, and began a power-off glide towards shore for an off-airport emergency landing. During the emergency landing, the UAS impacted a beachside cliff which resulted in substantial damage to the wings and fuselage.

The wreckage has been moved to a secure location, and a detailed NTSB examination is pending.

Friday, September 19, 2025

MD Helicopters MD 500 (369D), N5072F, fatal accident occurred on September 11, 2025, near Jim Thorpe, Pennsylvania

  • Location: Jim Thorpe, PA 
  • Accident Number: ERA25FA344 
  • Date & Time: September 11, 2025, 14:02 Local 
  • Registration: N5072F 
  • Aircraft: Hughes 369D 
  • Injuries: 2 Fatal 
  • Flight Conducted Under: Part 133: Rotorcraft ext. load

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

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

On September 11, 2025, about 1402 eastern daylight time, a Hughes (McDonnell Douglas) 369D helicopter, N5072F, was destroyed when it was involved in an accident near Jim Thorpe, Pennsylvania. The commercial pilot and line technician were fatally injured. The helicopter was operated as a Title 14 Code of Federal Regulations Part 133 external load flight.

According to the operator, the helicopter departed a landing zone about 1400 with 45 gallons of Jet-A fuel, to perform work near a 120-ft-tall transmission tower about 1 mile away. The purpose of the flight was to measure and mark sections along a fiber optic wire, located above the transmission wires. Anti-galloping devices (dampers) were to be installed at a later time, on the conductor wire below the fiber optic wire markings. To accomplish this task, the line technician would be positioned on a skid plate, on the left outside of the helicopter, behind the pilot seat, with colored tape. The line technician would then adhere a section of colored tape to the fiber optic wire at the position where the anti-galloping device was to be installed.

There were no known witnesses to the accident sequence. Other line technicians, working about 2 miles away, reported feeling and hearing vibrations in the lines about the time of the accident.

The wreckage came to rest in a vertical nose-down position adjacent to the transmission tower with severed fiber optic wire, oriented about a 210° magnetic heading. The fuel tank had been breached during impact. A strong odor of Jet-A fuel was present at the accident site. Additionally, residual fuel was noted in the tank and on the ground near the wreckage.

Four of the five main rotor blades (MRB) separated from the hub and the tailboom also separated. One MRB remained partially attached to the hub and was curled around the wreckage. Two other MRBs were located in the forward vicinity of the main wreckage. One MRB was bent downward about mid-span, and the other MRB was curled downward near the tip. A section of the fourth MRB was located in a tree aft of the main wreckage, and the fifth MRB was found aft of that, on the ground. The fifth MRB exhibited buckling near the outboard leading edge. A smaller outboard section of MRB was also found about 200 ft forward of the main wreckage.

The upper vertical and horizontal stabilizer were located about 70 ft aft of the main wreckage. Sections of the tailboom, tailrotor driveshaft, tailrotor gearbox, lower vertical stabilizer, and separated tailrotor were located together about 40 ft aft of the main wreckage. The tailrotor hub had separated from the tailrotor gearbox and one tailrotor blade remained attached to the hub. It was bent about 45° near the inboard one-third section. The other tailrotor blade separated about 4 in from the root and the inboard leading edge area of the separated section exhibited an impact scrape indentation.

The pilot held a commercial pilot certificate with a rating for rotorcraft-helicopter. He reported a total flight experience of 11,700 hours on his most recent application for a Federal Aviation Administration second-class medical certificate, dated November 25, 2024. According to the operator, of the pilot’s total flight experience, 2,626 hours were in the same make and model as the accident helicopter. 

The helicopter was manufactured in 1981 and equipped with an Allison (Rolls-Royce) 250-C20R/2, 450-shaft-hp engine. The helicopter was maintained under a manufacturer’s approved inspection program. Its most recent 100-hour inspection was completed on June 21, 2025. At that time, the airframe had accrued 7,985 total hours of operation and the engine had accrued 6,009 total hours of operation. The helicopter had flown 78.2 hours between the inspection and the accident. 

The wreckage was retained for further examination.