Friday, September 26, 2025

Extra EA-300/L, N763DT, incident occurred on September 25, 2025, at North Las Vegas Airport (VGT/KVGT), Las Vegas, Nevada

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

- History of Flight:
September 25, 2025, at about 1457 local time, an Extra EA-300/L, N763DT, registered to KD Leasing LLC out of North Las Vegas, sustained unknown damage when it was involved in an incident at North Las Vegas Airport (VGT/KVGT), Las Vegas, Nevada. The pilot and passenger were not injured. The local flight originated from KVGT at about 1443 LT.

According to the FAA "Aircraft lost control on landing, veered off runway and right gear broke off." ADS-B data shows that the airplane landed on runway 12L with a reported groundspeed of 100 knots, 19 seconds later, the airplane exited the left side of the runway while going about 58 knots (GS). Winds at the time were from 110° at 7 knots.

On October 26, 2014, the same airplane was involved in a runway excursion at KVGT due to a failure of the rudder cable due to tension overstress as a result of the cable's strength being compromised by wear damage.

Figure 1: ADS-B exchange data

Beechcraft V35B Bonanza, N17827, accident occurred on September 25, 2025, near New Kent County Airport (W96), Quinton, Washington

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

- History of Flight:
September 25, 2025, at about 1415 local time, a privately-registered Beechcraft V35B Bonanza, N17827, suffered a bird strike near New Kent County Airport (W96), Quinton, Washington. The pilot and passenger sustained minor injuries. The airplane entered a left turn and landed back at the airport.

According to the FAA, a post flight inspection revealed damage to the windshield and avionics, and the damage was reported as substantial, and the event was assigned as an accident. ADS-B data (figure 1) shows that the airplane was climbing through 1,900 ft when the bird strike happened, this was followed by a rapid 1500 feet per minute (fpm) descent rate.

Figure 1: Flightaware ADS-B data ran through Google Earth

Pipistrel Alpha Trainer, N246EA, accident occurred on September 25, 2025, near Wickenburg, 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=N246EA

- History of Flight:
September 25, 2025, at about 0654 local time, a Pipistrel Alpha Trainer, N246EA, registered to Mesa Pilot Development LLC, sustained substantial damage when it was involved in an accident near Wickenburg, Arizona. The two occupants onboard sustained minor injuries. The local training flight originated from Glendale Municipal Airport (KGEU), 
Glendale, Arizona, at about 0553 LT.

The FAA reported that "Aircraft experienced engine issues and made an emergency landing and flipped over." ADS-B data shows that the airplane was cruising at 6,600 ft before it conducted a descent towards secluded desert terrain (figure 1).

Figure 1: ADS-B exchange data ran through Google Earth

- Weather: (KBXK was closest to flightpath)

METAR KBXK 251255Z AUTO 32004KT 9SM CLR 25/12 A2988 RMK AO2
METAR KBXK 251315Z AUTO 00000KT 10SM CLR 24/12 A2989 RMK AO2
METAR KBXK 251335Z AUTO 31005KT 10SM CLR 24/12 A2989 RMK AO2
METAR KBXK 251355Z AUTO 00000KT 10SM CLR 25/12 A2990 RMK AO2

Cessna 525C Citation CJ4, N361MB, incident occurred on September 25, 2025, at Baton Rouge Metropolitan Airport (BTR/KBTR), Baton Rouge, Louisiana

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

- History of Flight:
September 25, 2025, at about 1819 local time, a Cessna 525C Citation CJ4, N361MB, registered to Pacifia LLC out of Baton Rouge, sustained unknown damage when it was involved in a landing mishap on runway 31 at Baton Rouge Metropolitan Airport (BTR/KBTR), Baton Rouge, Louisiana. The two occupants were not injured. The flight originated from Pensacola International Airport (KPNS), Pensacola, Florida, at about 1514 LT.

The FAA reported that: "Aircraft right main gear went through the wing after applying the brakes on landing." A review of previous accidents/incidents involving the CJ4 did not reveal any similar events. ADS-B data shows the airplane on final approach to runway 31 at 105 knots groundspeed.

- Weather:

METAR KBTR 252253Z 26003KT 10SM SCT055 28/21 A2989 RMK AO2 SLP119 T02830211

METAR KBTR 252353Z 25004KT 10SM FEW044 FEW050 SCT065 26/22 A2989 RMK AO2 SLP119 T02610217 10289 20261 56009

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. 

Beechcraft P35 Bonanza, N463T, fatal accident occurred on September 5, 2025, near Centennial Airport (APA/KAPA), Denver, Colorado

  • Location: Englewood, CO 
  • Accident Number: CEN25FA366 
  • Date & Time: September 5, 2025, 06:23 Local 
  • Registration: N463T 
  • Aircraft: Beech P35 
  • Injuries: 2 Fatal 
  • Flight Conducted Under: Part 91: General aviation - Instructional

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

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

On September 5, 2025, about 0623 mountain daylight time, a Beech P35 airplane, N463T, was destroyed when it was involved in an accident near Englewood, Colorado. The pilot receiving instruction and flight instructor were both fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 instructional flight.

The pilot receiving instruction was receiving familiarization training as he planned to purchase a similar airplane. ADS-B data for the accident flight showed the airplane departed from runway 35R at the Centennial Airport (KAPA), Englewood, Colorado, about 0543, remained in the traffic pattern. and performed several landings. 

Archived tower audio recordings captured that after performing a stop and go landing to runway 17L, one of the pilots said they were “on the roll”. This was the last recorded radio transmission from the airplane. When the tower controller cleared them “the option” no response was recorded. The tower controller later requested the pilots “ident” if they heard the transmission and the tower controller replied, “ident observed.” No distress calls were recorded from either pilot.

ADS-B data showed at 0622:15, the airplane stopped a climb and began to descend. At 0622:43, data recorded the airplane’s ident. The descent continued until the last recorded point of 0623:05 when the airplane was about 5,900 ft mean sea level, and 77 knots groundspeed.

A firefighter located about 1.5 miles south of the accident site heard the airplane fly overhead and heard the engine stop completely. A woman who lives in a neighborhood south of the airport was walking when she saw the airplane flying on a different flight path and lower than she was used to normally seeing. She heard the engine go silent and looked up to observe the airplane in a “hard” left bank towards the airport and in a descent. The airplane appeared normal, and she thought the airplane was conducting training.

Cameras from businesses around the accident site captured low-resolution video which showed the airplane descending in a left bank. Just before ground impact, the airplane banked right. 

The airplane impacted a paved driveway of an industrial facility. Initial impact points were scrapes on the asphalt aligned on a 280° heading towards the accident site. The main wreckage consisted of a majority of the airplane. Portions of the right wing were scattered to the south of the debris path. The left wing was fractured near the wing root and was found folded aft. The remainder of the airplane remained in its expected orientation. Signatures were consistent with the airplane colliding with several concrete pole barriers in front of a generator unit before coming to rest on a 060°heading. 

Flight control continuity was established from the cockpit to the aileron bellcranks and ruddervators. The dual control wheel chain was observed with the aileron yoke chain around its sprocket. The landing gear and flaps were both found retracted. The propeller remained attached to the engine which was displaced aft into the cockpit area. 

The airplane was retained for further examination. 

CZAW SportCruiser, N336SC, fatal accident occurred on September 4, 2025, near Eastern Slopes Regional Airport (IZG/KIZG), Fryeburg, Maine

  • Location: Fryeburg, ME 
  • Accident Number: ERA25FA332 
  • Date & Time: September 4, 2025, 14:18 Local 
  • Registration: N336SC 
  • Aircraft: Czech Sport Aircraft Sportcruiser 
  • Injuries: 1 Fatal 
  • Flight Conducted Under: Part 91: General aviation - Personal

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

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

On September 4, 2025, about 1418 eastern daylight time, a Czech Sport Aircraft Sportcruiser, N336SC, was substantially damaged when it was involved in an accident near Fryeburg, Maine. The private pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

The pilot’s son, who had flown with him earlier in the day, reported that the purpose of the flight was to reposition the airplane from Eastern Slopes Regional Airport (IZG), Fryeburg, Maine, to Moultonborough Airport (4MB), Moultonborough, New Hampshire, as IZG was scheduled to close on September 10th for construction. He reported that after the morning flight they washed the airplane, and added 8 gallons of non-ethanol unleaded gasoline, 4 gallons to each wing tank. This brought the total amount of fuel to 13 gallons, 7 gallons in the left wing fuel tank and 6 gallons in the right wing fuel tank. He then departed IZG to drive to 4MB prior to the airplane departing as it was about a 1-hour drive and only about a 20-minute flight. 

Preliminary ADS-B data showed the airplane departed runway 14 at IZG then made a climbing left turn to a maximum altitude of about 2,100 ft mean sea level (msl) on a flight track of about 300°. Two minutes and 26 seconds after the first ADS-B target the airplane stopped climbing at 2,100 ft msl on a flight track of about 210°, and 5 seconds later began about a 500 ft/min descent. About 15 seconds later the airplane began a left turning descent which continued until the ADS-B data ended. The final data point reported the airplane at an altitude about 1,700 ft msl on a flight track of 025° with a descent rate of about 1,300 ft/min. Witnesses on the ground reported hearing a “loud pop” sound, which made them look up, and observe the airplane “in a dive” with the ballistic parachute recovery system partially deployed. One witness who was working at the airport described hearing a “bang” then seeing the accident airplane about 1,000 ft above ground level (agl) in a left spin pointed “straight into the ground.” 

The airplane came to rest in a wooded area just off a firebreak about 1 nautical mile (nm) from the departure airport. The wreckage was oriented on a magnetic heading of 118° and an elevation of 433 ft msl. All major components were contained within about a 40 ft radius from the main wreckage site. The initial impact point was about 30 ft above ground level on a tree located about 50 ft east of where the main wreckage came to rest. The initial ground impact scar was about 25 ft from the initial impact tree, the scar contained rocks which exhibited blue paint transfer consistent with wingtip impact. A larger ground impact crater consistent with impact of the airplane’s engine was observed about 15 ft from the initial ground impact scar. The airplane came to rest about 10 ft from the large impact crater.

The fuselage was impact crushed up and aft. The cockpit canopy was impact separated and found near the airplane. The canopy latch attachment points were torn in a manner consistent with the canopy being closed and latched at the time of impact. The vertical stabilizer, rudder, and right horizontal stabilizer were undamaged. The left horizontal stabilizer, elevator, and pitch trim were displaced forward consistent with impact with a tree during the accident sequence. Both wings remained attached at the main wing spars. The leading edge of the right wing outboard of the fuel tank was impact crushed up and aft. The left wing was impact crushed up and aft and was bent upwards. Control continuity was established from all flight control surfaces to the flight controls in the cockpit through fractures in multiple rod ends consistent with overload impact separation.

Both fuel tanks were breached. The left wing fuel tank contained no fuel and about 1.5 gallons of fuel was drained from the right wing fuel tank via the wing fuel sump. Both the left and right wing fuel tank caps were secured in place and both fuel tank finger screens were unobstructed. The fuel selector was found set to the right fuel tank and continuity of the fuel system was confirmed from the wing tanks through the fuel selector. The fuel line from the fuel selector to the fuel strainer was impact separated. The fuel strainer exhibited impact damage and contained no fuel; the strainer screen was unobstructed. Fuel was drained from the lines of the electric fuel pump and fuel bypass. The fuel was collected in a clear container and tested for water; the presence of water was not detected. An external electrical source was connected to the electric fuel pump, and when the intake was placed in a bucket of water, the fluid pumped with no anomalies. Air was blown through the electric fuel pump fuel bypass, and it was unobstructed. The fuel flow transducer was removed and when air was blown through, it was unobstructed, and the wheel spun smoothly.

The airplane was equipped with a ballistic parachute recovery system (BPRS) which was partially deployed. The red BPRS activation handle in the cockpit was out of its mount consistent with an inflight deployment. The BPRS motor launch tube was mounted to the firewall, and the parachute and other packing materials were stored in a bag which located in a bracket mounted horizontally to the firewall. All 4 parachute harness mounts were secure to the aircraft, and the airframe harness was partially deployed. The harness remained attached to the parachute riser and the riser was partially deployed. The suspension lines remained attached to the riser with a portion of the lines still undeployed in the sleeve. The parachute remained attached to the suspension lines and was partially deployed from the sleeve. The drogue chute was entangled in the parachute sleeve and suspension lines and remained attached to the sleeve. The rocket motor and cable attachments remained attached to the drogue and the rocket motor was found inside the baggage compartment. The nose of the rocket motor had paint transfer consistent with the entry hole in the top aft portion of the fuselage.

Postaccident examination of the engine showed both carburetors had been impact separated from the engine; one remained attached to the wreckage through the throttle control cable and the other was imbedded in the air intake housing. The reduction gearbox sustained impact damage, and the propeller shaft was forced aft into the crankcase. The large gear within the gearbox was also displaced aft, into the crankcase, which displayed gear tooth stamp marks with no rotational scoring signatures. Once the gearbox was removed, both the propeller shaft and crankshaft rotated freely. The cylinder piston and valve faces were examined using a lighted borescope and exhibited lead buildup on the piston face and intake valves. The rocker covers were removed from each cylinder head, and all rocker arms, valve springs, and valves functioned normally. All top and bottom sparkplugs were removed and examined. The spark plugs were yellow, consistent with the use of 100 LL aviation fuel and lead deposits were observed on the electrode. The engine driven fuel pump and right carburetor bowl contained fuel, and the presence of water was not observed when tested with water finding paste. The oil filter adapter and oil filter were impact separated from the crankcase and remained attached to the engine via safety wire. The oil filter was removed and cut open. No debris was noted in the oil filter pleats.

The airplane was equipped with avionics capable of recording and retaining flight and engine data. These units were removed and sent to the National Transportation Safety Board Vehicle Recorders Laboratory for data extraction.

The airplane was retained for further examination. 

Piper PA-28R-200 Cherokee Arrow II, N1147X, fatal accident occurred on August 31, 2025, near Alta, Utah

  • Location: Alta, UT 
  • Accident Number: WPR25FA269 
  • Date & Time: August 31, 2025, 17:20 Local 
  • Registration: N1147X 
  • Aircraft: Piper PA-28R-200 
  • Injuries: 1 Fatal, 1 Serious 
  • Flight Conducted Under: Part 91: General aviation - Personal 

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

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

On August 31, 2025, about 1720, mountain daylight time a Piper PA28-200R, N1147X, was substantially damaged when it was involved in an accident near Alta, Utah. The pilot was seriously injured, and the passenger sustained fatal injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

Preliminary ADS-B data indicated that after departure from Bolinder Field/Tooele Valley Airport (TVY), the airplane initiated a climbing right turn to the northeast. After receiving a clearance from the Salt Lake Terminal Radar Approach Control (TRACON), the airplane followed the Salt Lake City I-80 VFR Transition route east towards Salt Lake International Airport, then to the south at altitude of about 6,600 ft. By 1711, the airplane had completed the transition, and was on a southbound track, as it approached South Jordan, Utah. About that time, the airplane began a climbing left turn to the east, towards the entrance of Little Cottonwood Canyon.

The last ADS-B target indicated the airplane was climbing at a rate of about 380 fpm, and was at an altitude of 8,400 ft by the time it had reached the entrance of the canyon. At that time the canyon walls were about 1.3 miles apart, with terrain immediately rising to 11,330 ft to the north, and 11,253 ft to the south.

A short time later, witnesses located at a lodge at an elevation of about 8,600 ft and about 6 miles further up the canyon, observed an airplane flying up the canyon and directly over their location. One witness, who was a pilot, stated that he estimated the airplane to be about 100 to 200 ft above him, and flying so low that he was immediately concerned. He could hear the engine operating as it continued towards the end of the canyon, which was about 2 miles beyond their location.

Another witness, located in a south facing residence within the canyon at an elevation of about 9,100 ft, and 3/4 miles past the lodge, was resting on his deck when he was woken by a loud engine sound. When he looked across the valley, he could see an airplane traveling right to left, and almost level with his position. He could hear the engine operating, and the wings were rocking. He stated that the airplane continued up the valley and started to make a gradual left turn, that suddenly became aggressive such that he could see the entire overhead profile of the airplane. The airplane’s nose then dropped, and it collided with the ground in an area of trees on the north face of the valley.

The airplane impacted terrain within a bowl-shaped area at the end of the canyon. The first point of impact was identified on the trunk at the base of a 4-ft wide pine tree at an elevation of about 9,060 ft. The bark on the southeast side of the trunk had been removed, leaving a series of three scallop-shaped marks that appeared to match the shape of the three propeller blades.

The airframe came to rest about 70 ft uphill from the tree impact point. Fragments of the right outboard wing and aileron were located at the base of the tree. The debris field continued uphill where the inboard wing and integral fuel tank, along with the right flap were located. The tank was breached, with semi-circular crush damage to the main spar, that matched the general shape of the tree trunk at the initial impact point.

The main wreckage was composed of the detached forward cabin and instrument panel, along with the main cabin, empennage, and left wing, all of which remained generally intact. The engine had detached from the airframe during the accident sequence and was located about 30 ft uphill from the main wreckage.

The airplane has been retained for further examination.

Piper PA-28-181 Archer III, N961DA, fatal accident occurred on July 30, 2025, at Block Island State Airport (BID/KBID), New Shoreham, Rhode Island

  • Location: Block Island, RI 
  • Accident Number: ERA25FA280 
  • Date & Time: July 30, 2025, 12:10 Local 
  • Registration: N961DA 
  • Aircraft: Piper PA-28-181 
  • Injuries: 1 Fatal, 1 Serious, 1 Minor 
  • Flight Conducted Under: Part 91: General aviation - Personal 
https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/200669/pdf

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

On July 30, 2025, about 1210 eastern daylight time, a Piper PA-28-181, N961DA, was substantially damaged when it was involved in an accident near Block Island, Rhode Island. The pilot sustained serious injuries, one passenger received minor injuries, and one passenger was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

The flight departed Albany International Airport (ALB), Albany, New York, about 1050, enroute to Block Island State Airport (BID), Block Island, Rhode Island. The pilot reported that the purpose of the flight was to fly with two passengers to BID for lunch. About 20 nautical miles (nm) from BID, the pilot began his descent and obtained the automated weather information.

At 1156, the automated weather observation at BID recorded wind from 230° at 7 knots, which corresponded to a tailwind and crosswind component for landing on runway 10.

The pilot reported that he entered the left downwind leg of the traffic pattern for runway 10, and on the final approach leg of the traffic pattern, he observed an airplane departing runway 28 and initiated a go-around. During a second approach, he turned from the downwind leg to final approach leg of the traffic pattern too close to the runway and initiated another go-around. After a third approach to runway 10, the airplane touched down with full flaps about 1,500 ft down the 2,500-ft-long runway. As the pilot applied the brakes, the airplane’s right wing lifted due to a gust of wind. There was insufficient runway remaining for a go-around, the airplane overran the runway and impacted trees.

Preliminary ADS-B data indicated the airplane crossed the runway threshold at 174 ft altitude and 104 knots groundspeed, touched down at 83 knots, and exited the runway at 73 knots. The final recorded point was about 55 ft from the end of the overrun area at 70 knots.

Preliminary air traffic control (ATC) audio indicated the pilot was receiving visual flight rules (VFR) advisories from Providence Terminal Radar Approach Control (TRACON). About 20 nm from BID, ATC advised that radar services were terminated, to “squawk” VFR, and frequency change was approved. Although the pilot acknowledged, he remained on the Providence TRACON frequency and reported his position in the BID traffic pattern for two of three approaches. ATC advised him several times that he was transmitting on the incorrect frequency and provided the correct advisory frequency.

The overrun area of runway 10 was a flat grassy surface about 243 ft long at an elevation of about 102 ft mean sea level (msl). Three linear tire impressions, consistent with landing gear, were observed about 25 ft from the end of the overrun area on a 099° magnetic heading. No tire friction marks were observed on the runway or overrun before that point. The airplane came to rest inverted on a 209° magnetic heading about 640 ft east of the departure end of runway 10 at an elevation of about 40 ft msl. All major components of the airplane were located at the accident site.

The first identified point of impact was a tree canopy about 50 ft above ground level and 467 ft from the departure end of the runway. Several tree branches exhibited angular cuts with black transfer marks. A ground impression containing the separated nose landing gear was located about 128 ft from the first impact point and 45 ft from the main wreckage. The wreckage path was oriented on a 096° magnetic heading and about 173 ft long. Vegetation staining consistent with fuel exposure was observed along the debris path.

Examination of the airframe and engine revealed that flight control continuity was established from the cockpit to all the flight control surfaces, and the flap position was noted at 40°. The empennage exhibited impact damage and the stabilator trim was noted in a partial nose-down trim setting. Both wings exhibited impact damage, and the left wing was partially separated from the fuselage. Both fuel tanks were breached from impact forces. Fuel system continuity was established, and fuel consistent in color and odor to 100LL aviation gasoline was observed in the system.

The engine remained attached to the engine mount. Both magnetos produced spark from their ignition towers during hand rotation of their attached drive gears. Crankshaft and valvetrain continuity were established, and compression and suction were obtained on all four cylinders. The propeller remained attached to the engine with chordwise abrasion and leading-edge damage noted to both propeller blades.

The wreckage was retained for further examination.

Thursday, September 18, 2025

Cirrus SR22T GTS G5 Carbon, N218VB, fatal accident occurred on September 18, 2025, at Macon County Airport (1A5), Franklin, North Carolina

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

- History of Flight:
On September 18, 2025, at about 1457 local time, a Cirrus SR22T GTS G5 Carbon, N218VB, registered to a private individual out of Brentwood, TN, was substantially damaged when it impacted terrain near the Macon County Airport (1A5), Franklin, North Carolina. The three occupants onboard sustained fatal injuries. The cross-country personal flight originated from John C. Tune Airport (KJWN), Nashville, Tennessee, and was destined to 1A5.

According to preliminary Automatic Dependent Surveillance – Broadcast (ADS-B) data (figure 1), the airplane departed runway 20 at KJWN and entered a climbing left turn to an inflight cruising altitude of 11,000 ft. The flight appeared to be uneventful. At 1438:06, the airplane started its descent towards 1A5. At 1449:34, the airplane started a 360 turn about 1.50 miles west of runway 7. At the conclusion of the turn, the airplane proceeded to fly over the runway before turning left and joining the left pattern for runway 7 (figure 2). At 1455:39, the airplane was at 2500 ft, 101 knots groundspeed, and descending 1300 feet per minute (fpm) on final approach to runway 7. At 1455:55, the airplane was at 2100 ft, 92 knots groundspeed, and descending 850 fpm. At 1456:11, the airplane was observed on the runway with a groundspeed of 78 knots. Immediately after that, the airplane drifted to the left and was observed climbing to about 2250 ft with a reported groundspeed of 70 knots before the track ended in the vicinity of the accident site. (figure 3)

Figure 1: Climb and Flight

Figure 2: Approach

Figure 3: End of Track

- Pilot Information:
Unknown at this point.

The current registered owner (unknown if this was accident pilot) holds a private pilot certificate, issued/updated on 11/3/2020, with an airplane single engine land and instrument airplane ratings. His second class medical was issued on October 2023, with a note stating that he must wear corrective lens(es) to meat vision standards at all required distances.

- Aircraft Information:
The accident airplane, serial number 1378, was manufactured in 2016. It was a five-seat low-wing monoplane aircraft of composite construction. It was powered by a Continental TSIO-550-K engine driving a three-blade constant speed governor-regulated propeller.

According to the Cirrus SR22T Pilot Operating Handbook (POH), the recommended airspeed for a go-around with flaps 50% is 80 KIAS (knots Indicated airspeed).

Additionally, Section 4, Normal Procedures:

Balked Landing/Go-Around 

  • 1. Autopilot........................DISENGAGE 
  • 2. Power Lever .........................FULL FORWARD 
  • 3. Flaps .............................................50% 
  • 4. Airspeed............................80-85 KIAS After clear of obstacles: 
  • 5. Flaps................... UP 

Amplification

In a balked landing (go around) climb, disengage autopilot, apply full power, then reduce the flap setting to 50%. If obstacles must be cleared during the go around, climb at 80-85 KIAS with 50% flaps. After clearing any obstacles, retract the flaps and accelerate to the normal flaps up climb speed.

- Wreckage and Impact Information:
The main wreckage, which consisted of the entire airplane, came upright about 500 ft north of the runway. There was no post crash fire. Both wings and tail remained attached to the fuselage, and there was no debris field leading to the airplane. The engine remained attached to the firewall and was pushed down into the grass. Both wings sustained leading edge impact damage. The tail was twisted forward. The cockpit/passenger cabin remained intact. The impact appears consistent with a low altitude aerodynamic stall/spin with little no forward speed.

- Airport Information:
Macon County Airport is an uncontrolled public airport located about 3 miles northwest of Franklin, North Carolina. The airport field elevation is 2033.9 ft. It features a single asphalt runway 7/25 that is 5002 feet long and 100 feet wide.

The airport is surrounded by rapidly rising terrain at all quads.

- Weather:
The recorded weather at 1A5, at 1555 (about 2 minutes before the accident), was: wind 0 knots; sky clear;visibility 10 miles; temperature 27 degrees C; dew point 17 degrees C, altimeter 30.13 inches of mercury. The calculated density altitude was 
3727 ft.

Area Forecast Discussion

Area Forecast Discussion
National Weather Service Greenville-Spartanburg SC
142 PM EDT Thu Sep 18 2025

.SYNOPSIS...
Weak high pressure will keep conditions mostly dry today outside of
a mountain shower or storm. An uptick in shower and storm chance are
possible Friday into the weekend, especially over the High Country.
Temperatures will be on the warm side of normal through Saturday
before a slight cool down commences Sunday into the early part of
next week.

&&

.NEAR TERM /THROUGH FRIDAY/...
As of 1233 PM EDT Thursday: Quiet weather to continue for the
near term!  Mostly clear conditions are ongoing with a light NE
wind, beneath expansive high pressure and a nebulous upper pattern.
Ill-defined troughiness will persist through much of the period,
but heights are gently climbing ahead of a ridge axis extending
from the Ozark Plateau north into the lower Great Lakes.  As a
result, above-normal highs are expected today - climbing into
the mid-80s across the Piedmont and Upstate - and any convection
trying to get a foothold in the mountains will encounter a mostly
suppressive environment.  So, while some widely scattered showers
will likely develop today over the high terrain...neither coverage
nor intensity will be very impressive.

Any convection that develops will dissipate quickly after sunset.
Mostly clear skies are expected overnight, except of course in the
mountain valleys, where another round of valley fog and stratus
should develop in the wee hours of Friday morning.  Wind should be
calm enough and radiative cooling effective enough that at least
patchy fog may develop over parts of the NC Foothills and Savannah
River Valley, too.  Lows will fall into the low 60s again.

Friday will be similar, with ridgetop convection in the afternoon
but no mentionable PoP outside the mountains.  Highs should climb
into the upper 80s, with some favored spots along I-77 hitting
90 degrees.  Skies will be mostly clear again, with some fair
weather cu outside the mountains.
.AVIATION /18Z THURSDAY THROUGH TUESDAY/...
At KCLT and elsewhere: Dry and VFR across the terminal forecast
area.  Expect mostly clear conditions with some FEW/SCT cumulus
through the afternoon.  Some ridgetop convection will probably
develop...but remain isolated to widely scattered...and so no
mention in the 18z TAF for KAVL.  Expect light and variable winds,
and mostly-clear skies overnight, except for the mountain valleys,
which will see another round of valley fog and stratus into Friday
morning.  Another round of SE winds will develop after daybreak,
but should remain light.  Better coverage of showers is expected
over the mountains Friday.

Outlook: Isolated to widely scattered diurnal showers will occur
again on Saturday, then drying is expected on Sunday and Monday.
Valley fog and stratus will be possible each morning where clouds
do not inhibit nocturnal radiation.

Sun and Moon Data

The sun’s position at the time of the accident was about 50° over the horizon on an azimuth of 217° SW, and the the Moon was 37 degrees over the horizon on an azimuth of 264° W.

- Additional Information:
no

Cessna 150F, N8047F, accident occurred on September 17, 2025, near Rigby Airport (U56), Rigby, Idaho

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

- History of Flight:

On September 17, 2025, at about 1136 local time, a privately-registered Cessna 150F, N8047F, sustained substantial damage when it collided with powerlines and a building near Rigby Airport (U56), Rigby, Idaho. The pilot and passenger sustained minor injuries. The local training flight originated from U56.

Preliminary ADS-B data suggests the airplane landed on runway 1 and conducted a go-around before the accident. The accident site was located about 0.50 mile north of the airport. The FAA reported "aircraft struggled to gain altitude and ran into powerlines." The calculated density altitude was roughly 5862 ft.

- Weather:

METAR KIDA 171653Z 04009KT 10SM CLR 16/06 A3030 RMK AO2 SLP238 T01560056

METAR KIDA 171753Z 36005KT 10SM CLR 17/06 A3028 RMK AO2 SLP234 T01720056 10172 20050 58005 <<<

Cirrus SR22 GTS G2, N22VC, incident occurred on September 17, 2025, at Norwood Memorial Airport (OWD/KOWD), Norwood, 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=N22VC

On September 17, 2025, at about 0730 local time, a Cirrus SR22 GTS G2, N22VC, registered to Kalila LLC out of Weston, MA, sustained unknown, but apparent minor damage when it was involved in an incident at Norwood Memorial Airport (OWD/KOWD), Norwood, Massachusetts. There were no injuries.

According to the FAA ASIAS report: "Aircraft inadvertently moved across the airport into a swampy area due to pilot attempting a prop start."

Wednesday, September 17, 2025

Bell 206B JetRanger III, N992MR, accident occurred on September 10, 2025, near Monroe, Georgia

  • Location: Monroe, GA
  • Accident Number: ERA25LA338
  • Date & Time: September 10, 2025, 11:00 Local
  • Registration: N992MR
  • Aircraft: Bell 206
  • Injuries: 2 Serious
  • Flight Conducted Under: Part 91: General aviation - Instructional

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

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

On September 10, 2025, about 1100 eastern daylight time, a Bell 206, N992MR, was destroyed when it was involved in an accident near Monroe, Georgia. The flight instructor and student pilot were seriously injured. The helicopter was operated as a Title 14 Code of Federal Regulations Part 91 instructional flight.

According to the flight instructor, he and the student were practicing hovering at about 10-15ft agl in an open field when the helicopter suddenly, and violently, turned to the right. The instructor, who was sitting in the left seat, immediately rolled the throttle control to the idle position before the helicopter contacted the ground. The helicopter immediately caught fire and was consumed.

The flight instructor stated that the student pilot had purchased the helicopter about a month ago and that he had flown with the student 3 or 4 times in that helicopter prior to the accident. On the day of the accident, the flight instructor met the student pilot at the student pilot’s residence where the helicopter was stored. The training for the day included a flight from the student pilot’s residence to Covington Municipal Airport (CVC) in Covington, Georgia, where they did some training before refueling. The instructor stated that they filled the helicopter with fuel before departing CVC and headed toward the field where the accident occurred to practice hovering. While practicing hovering, the instructor stated that he was on the controls with the student and did not feel any erratic maneuvers or jerking that would have caused the helicopter to turn violently to the right.

The wreckage was retained for further examination.

Robinson R66 Turbine, N6633L, fatal accident occurred on September 6, 2025, near Airlake Airport (LVN/KLVN), Lakeville, Minnesota

  • Location: Lakeville, MN 
  • Accident Number: CEN25FA367 
  • Date & Time: September 6, 2025, 14:42 Local 
  • Registration: N6633L 
  • Aircraft: ROBINSON HELICOPTER CO R66 
  • Injuries: 2 Fatal 
  • Flight Conducted Under: Part 91: General aviation - Personal 
https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/200949/pdf

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

On September 6, 2025, about 1442 central daylight time, a Robinson Helicopter Company R66 helicopter, N6633L was destroyed when it was involved in an accident near Lakeville, Minnesota. The pilot and passenger were fatally injured. The helicopter was operated under the provisions of Title 14 Code of Federal Regulations Part 91 as a personal flight.

The helicopter departed a farm near Jordan, Minnesota, about 1434 and was enroute to New Richmond Regional Airport (RNH), New Richmond, Wisconsin, when it impacted the ground near a cornfield and came to rest near railroad tracks and a rail car about 0.2 nautical miles northwest of Airlake Airport (LVN), Lakeville, Minnesota. A post impact fire ensued and destroyed the helicopter.

The impact heading was about 78° and the main wreckage came to rest on a heading of about 177°. Cornstalks preceding the initial impact site were cut at 45°. Most of the debris was contained to a 55 ft path between the cornfield and the rail car, consisting of the tail cone, empennage, tail rotor, fuselage, landing gear, and most of the main rotor; however, some pieces of the main rotor blades were found near the approach end of runway 12 at LVN, 610 ft beyond (southeast) the impact site.

Due to impact damage, the main rotor and tail rotor flight controls could not be functionally tested. The main rotor drive shaft was bent due to impact above the swashplate; however, the driveshaft could be moved slightly by hand confirming continuity from the input yoke through the main rotor driveshaft and the tail rotor output yoke. The tail rotor input yoke was rotated by hand with no anomalies.

A witness to the accident stated that the helicopter was flying straight and level and then it turned sharply to the right and the nose of the helicopter pointed toward the ground. It remained in that attitude until it disappeared behind a building, and she lost sight of it. Video surveillance near the approach end of runway 12 at LVN captured the helicopter impacting the ground in a nose low attitude on its ride side.

The helicopter was retained for further examination.

Tuesday, September 16, 2025

Bellanca 17-30A Super Viking 300A, N432DM, fatal accident occurred on September 16, 2025, near Moriarty Municipal Airport (0E0), Moriarty, New Mexico

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


- History of Flight:
On September 16, 2025, at about 1131 local time, a privately-registered 
Bellanca 17-30A Super Viking 300A, N432DM, sustained substantial damage when it impacted powerlines and terrain near Moriarty Municipal Airport (0E0), Moriarty, New Mexico. One occupant sustained fatal injuries, the second occupant serious injuries. The flight originated from Sandia Airpark Estates East Airport (1N1), Edgewood, NM, and was destined to an unknown location.

According to preliminary Automatic Dependent Surveillance – Broadcast (ADS-B) data (figure 1), the airplane departed 1N1 at 1059 and proceeded to the north. About 9 minutes into the flight, the airplane turned right (to the south) and continued to climb. At 1116, the airplane conducted two 360 loops. At 1123, the airplane overflew 0E0 and flew west in preparations to land on runway 26. At 1128:30, the airplane landed on runway 26. At 1129:05, the airplane conducted a go-around, climbed to an altitude of 6,450 ft and started to turn left. At about 1130:26, the airplane was at 128 knots groundspeed and climbing 700 feet per minute (fpm) when it started to lose altitude and groundspeed while in the turn. At 1131:27, the airplane had deaccelerated to about 95 knots groundspeed and descending 700 fpm. The last ADS-B return was recorded at 1131:49, the airplane was at 5825 ft, 74 knots groundspeed, and descending -200 fpm (figure 2 and 3).

Figure 1: ADS-B Exchange track ran through Google Earth Pro

Figure 2: Landing, go-around, and accident

Figure 3: End of track with "extend to ground" option disabled, the airplane collided with one of the powertowers in the figure before impacting terrain.

The airplane struck powerlines and impacted terrain about 2 miles southeast of the airport. Local newspapers reported that "The cause of the crash is believed to be engine failure."

- Pilot Information:
unknown at this point.

The current registered owner (It is unknown if this was the accident pilot) held a private pilot certificate (issued/updated on 8/25/2010) with a rating for airplane single engine land. He had an FAA BasicMed Course dated 1/28/2025.

- Airplane Information:
The four-seat, retractable landing gear, low-wing monoplane with an all-wood wing construction and a fabric covered steel-tube fuselage, serial number 30413, was manufactured in 1971. It was powered by a 300-horsepower Continental IO-520 engine equipped with a constant-speed propeller.

- Wreckage and Impact Information:
The airplane came to rest upright and there was no post crash fire. The main wreckage consisted of the entire airplane. Both wings and tail remained attached to the airframe. The first identified point of impact was a group of downed powerlines which led to the main wreckage. Scorching damage was noted on the right side of the fuselage.

- Airport Information:

The Moriarty Airport, 0E0, is a public, uncontrolled airport located 2 miles southeast of Moriarty, New Mexico, at a surveyed elevation of 6204.2 feet. The airport features two asphalt runways, runway 8/26, which is 7,700 feet long by 75 feet wide. and runway 17/35, which is 6,201 feet long by 75 feet wide.

- Weather Information:
(1) Brief:

The reported weather at 0E0, at 1115 (about 16 minutes before the accident) included: winds 200 at 6 knots, 10 statute miles visibility, no clouds under 12,000 ft (CLR), a temperature of 24° C, a dew point of 11° C, and a barometric altimeter setting of 30.35 inches of mercury. The calculated density altitude was 8303 ft.

(2) METARs:

METAR K0E0 161655Z AUTO 17007KT 10SM CLR 23/11 A3035 RMK AO2 T02290111

METAR K0E0 161715Z AUTO 20006KT 10SM CLR 24/11 A3035 RMK AO2 T02360108

METAR K0E0 161815Z AUTO 18004KT 10SM VCTS CLR 26/10 A3032 RMK AO2 LTG DSNT SE THRU SW T02580097

(3) Area Forecast Discussion:

731
FXUS65 KABQ 161138 AAA
AFDABQ

Area Forecast Discussion...UPDATED
National Weather Service Albuquerque NM
538 AM MDT Tue Sep 16 2025

...New AVIATION...

.KEY MESSAGES...
Updated at 533 AM MDT Tue Sep 16 2025

- Showers and thunderstorms with gusty outflow winds and brief
  heavy downpours will return to southern, central, and eastern
  parts of New Mexico Tuesday and Wednesday, then continue east of
  the central mountain chain Wednesday night.

- Isolated strong to severe thunderstorms will be possible east of
  the central mountain chain Tuesday afternoon and evening. Then,
  scattered severe thunderstorms are increasingly likely across
  far northeast New Mexico Wednesday afternoon and evening with a
  few producing locally heavy rainfall.

- There will be a minor risk of burn scar flash flooding on
  Tuesday and a minor to moderate risk on Wednesday. The threat
  for burn scar flash flooding may persist Thursday and Friday.

&&

.SHORT TERM...
(Tonight through Wednesday)
Issued at 1135 PM MDT Mon Sep 15 2025

A relatively weak upper low near the tri-state area of ID/MT/WY
will slowly drop southeastward into the central Great Plains today
and Wednesday. This feature will be led by a 60-70 kt speed max
aloft at 300 mb that will drop toward the Four Corners and NM-CO
border. Meanwhile a subdued upper level ridge over the Mexican
mainland is keeping the flow much lighter to our south, and
tropical storm Mario is tracking northward near 22N, 116W
(west southwest of the Baja Peninsula). At the surface, winds have
been taking on more of a southerly component which is advecting
suptropical moisture into NM, ad a few eastern plains sites are
already observing 60 degree F dewpoints. While these will mix down
some into the afternoon, a much broader swath of 40`s to 50`s
dewpoints will be observed later this afternoon over the
southeastern half of the forecast area, and PWATs will climb to
two-thirds of an inch upwards to near 1.0 inch in this sector.
This will bring a notable increase in storms from the past couple
of days, but coverage should still be isolated to scattered
(20-50% spatial coverage), generally stretching from the
southwest and south central mountains northward to the Jemez and
Sangre de Cristos before drifting east southeastward to nearby
lower elevations. With the speed max aloft over northern NM,
enough shear would be present to enhance updraft longevity, and a
lone strong to severe cell or two would be possible, mainly in
Colfax, Harding, and Union counties. Drier, high-based storms over
the Zuni mountains, Grants, Cuba and western Jemez would have
larger DCAPE profiles with a higher downburst threat and much
less rainfall efficiency. All storms would gradually become
outflow dominant and gust out late this evening as they roll into
the highlands and high plains to the east of the central mountain
chain.

By Wednesday, the initial upper low would move just east of the NE
panhandle with a secondary shortwave trailing and dropping into
south central WY. The speed max aloft would strengthen slightly
over northern NM, and drier air would filter into northwestern NM,
sharpening the moisture and PWAT gradient. The southwestern and
south central mountains would initiate convection Wednesday
afternoon with a few cells potentially going up over the Sangre de
Cristos, but the northeastern zones will likely not get too active
until the evening when a surface front arrives with increased moisture
and surface convergence. These storms in northeastern NM would
have the potential to turn severe with large directional shear
profiles.
.AVIATION...
(12Z TAFS)
Issued at 533 AM MDT Tue Sep 16 2025

Very weak showers and thunderstorms are ongoing across western New
Mexico early this morning, but otherwise dry weather with VFR
conditions is prevailing. This shower and storm activity will fade
through the morning with new batches of isolated to scattered
showers and thunderstorms redeveloping this afternoon and evening,
mainly across the southwestern to north central and northeastern
areas. Storms will be capable of producing gusty downburst winds
(especially near KGNT, KABQ, KAEG, KLAM, and KSAF) and brief
downpours. Most of the storm activity will dwindle through the
this evening.

&&

.FIRE WEATHER...
Issued at 1135 PM MDT Mon Sep 15 2025

Isolated to scattered showers return to portions of northern and
central NM today and Wednesday. The best prospects of wetting
rainfall will be found in the southwestern mountains and the
south central highlands, as well as the northeastern plains once
a front arrives Wednesday evening. Temperatures will be seasonable
today and Wednesday, and true to form, the driest areas will be
in northwestern NM where dewpoints will be lowest and afternoon RH
will plummet to 15 percent or slightly lower each day. Any wind
concerns will stem from thunderstorm outflows with the drier
storms over the Zuni mountains, Mount Taylor, and western Jemez
being more prone to gusty downbursts and even dry lightning
strikes. Storms will stay active Thursday over the southwestern
mountains and also along and east of the central mountain chain
with the driest area remaining in northwestern zones. There is
some uncertainty with Friday`s storm coverage forecast, but for
now it appears the focus will temporarily shift back over the
Continental Divide with increased moisture there. However, by the
weekend a drier and less stormy trend will get underway.

- Additional Information:
no