CSA PS-28 Cruiser, N538SF, accident occurred on August 25, 2025, near Pierce County Airport (PLU/KPLU), Puyallup, Washington

• Location: Puyallup, WA 
• Accident Number: WPR25LA259 
• Date & Time: August 25, 2025, 14:56 Local 
• Registration: N538SF 
• Aircraft: CZECH AIRCRAFT GROUP SRO SPORTCRUISER 
• Injuries: 1 Serious, 1 Minor 
• Flight Conducted Under: Part 91: General aviation - Flight test

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

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

On August 25, 2025, about 1456 Pacific daylight time, a Czech Aircraft Group SRO Sportcruiser, N538SF was substantially damaged when it was involved in an accident near Puyallup, Washington. The pilot sustained serious injuries, and the passenger was not injured. The airplane was operated as a Title 14 Code of Federal Regulations part 91 maintenance test flight.

A 100-hr maintenance inspection had just been completed and a pilot and mechanic from the flight school were conducting a post-maintenance check flight. After takeoff from runway 35, the pilot reported that there was an engine problem, and he attempted to turn back to the runway. However, the airplane would not maintain altitude and impacted a heavily vegetated field, west of the airport perimeter fence.

The airplane was recovered for further examination.

Gulfstream V, N820MS, accident occurred on September 2, 2025, at Portland International Airport (PDX/KPDX), Portland, Oregon

• Location: Portland, OR 
• Incident Number: WPR25LA273 
• Date & Time: September 2, 2025, 12:45 Local 
• Registration: N820MS 
• Aircraft: GULFSTREAM AEROSPACE G-V 
• Injuries: 3 None 
• Flight Conducted Under: Part 91: General aviation - Personal

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

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

On September 2, 2025, about 1245 Pacific daylight time, a Gulfstream Aerospace G-V, N820MS, was substantially damaged when it was involved in an accident near Portland, Oregon. The pilot, co-pilot and passenger were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

The flight crew reported that, after landing at the Portland International Airport (PDX), Portland, Oregon, the airplane was taxied to a fixed-based operator to disembark two passengers and refuel the airplane. A passenger boarded the airplane, and the flight crew conducted a preflight of the airplane and prepared the airplane to depart. The pilot noted that after the no. 2 engine was started, there was a low indication from the hydraulic oil pressure gage. He activated the power transfer unit (PTU), and upon activation of the PTU, the nose landing gear retracted, and the forward fuselage impacted the ground. The forward pressure bulkhead sustained substantial damage. The flight crew conducted an emergency engine shut down and all occupants of the airplane exited the airplane through the aft baggage door.

The airplane was secured for further examination. 

Jabiru J230-D (JabirWatt), N824DW, accident occurred on August 18, 2025, near Albany Municipal Airport (S12), Albany, Oregon

• Location: Albany, OR 
• Accident Number: WPR25LA267 
• Date & Time: August 18, 2025, 13:00 Local 
• Registration: N824DW 
• Aircraft: DAVID ULLMAN JABIRWATT 
• Injuries: 1 None 
• Flight Conducted Under: Part 91: General aviation - Personal

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

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

On August 18, 2025, about 1300 Pacific daylight time, an experimental amateur-built Jabirwatt, N824DW, was substantially damaged when it was involved in an accident near Albany, Oregon. 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 about 3.5 miles northwest of the Albany Municipal Airport (S12), Albany, Oregon, at 1,500 ft mean sea level (msl), the engine lost all power. Unable to maintain altitude, he elected to make an off airport landing to an open field. During the landing roll, the airplane exited the open field and impacted a hazelnut grove which resulted in substantial damage to both wings.

The wreckage was recovered for further examination.

Piper PA-28-181 Archer II, N8150J, accident occurred on August 16, 2025, near San Diego, California

• Location: San Diego, CA 
• Accident Number: WPR25LA261 
• Date & Time: August 16, 2025, 17:37 Local 
• Registration: N8150J 
• Aircraft: Piper PA-28-181 
• Injuries: 2 None 
• Flight Conducted Under: Part 91: General aviation - Personal

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

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

On August 16, 2025, about 1737 Pacific daylight time, a Piper PA-28-181, N8150J, was substantially damaged when it was involved in an accident near San Diego, California. The pilot and passenger were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

According to the pilot, he and a passenger had planned a local personal flight and departed Montgomery-Gibbs Executive Airport (MYF), San Diego, California, with full fuel. The airplane flew north along the coastline and about 15 minutes into the flight, the pilot switched fuel tanks. He did not recall whether he clearly felt the valve’s position detents when adjusting the fuel tank selector valve handle. Several minutes after switching fuel tanks, while at an altitude of 1,700 ft mean sea level, the engine began to sputter and lost partial power. The pilot declared an emergency with Southern California Terminal Radar Approach Control and troubleshot the loss of engine power by turning the fuel pump on, switching fuel tanks, and checking the ignition, however, the engine continued to sputter. The pilot initiated a forced landing to the southbound lanes of Interstate 805. During the landing roll, the left wing struck a highway sign post and the airplane came to rest upright against the center highway divider. The left wing, fuselage, and horizontal stabilator sustained substantial damage.

The wreckage was recovered to a secure facility for further examination.

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

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

Winco Inc

- History of Flight:
On September 11, 2025, at about 1402 local time, an MD Helicopters MD 500 (369D), N5072F, registered to Winco Inc out of Aurora, Oregon, was destroyed when it was involved in an accident near Jim Thorpe, Pennsylvania. The pilot and crewmember were fatally injured. The helicopter was operated as a Title 14 Code of Federal Regulations Part 133 external load flight.

The operator was contracted to conduct work on powerlines as part of a construction project. According to the available Automatic Dependent Surveillance – Broadcast (ADS-B) data for the helicopter, it departed from a nearby parking garage and headed west towards the powerlines (figure 1). The helicopter was observed flying around the powerlines for about 20 seconds before it entered a -1400 feet per minute (fpm) descent. (figure 2)

- Wreckage and Impact Information:
The helicopter came to rest on its side. There was no post crash fire. The main rotor blade and tail rotor were impact damaged and separated. The hook was also separated from the airframe. (figure 3)

Figure 1: Departure parking lot with dolly (left) and powerlines to the west of it

Figure 2

Figure 3

- Pilot Information:
unknown

- Aircraft Information:
None

- Airport Information:
None

- Weather:

METAR K22N 111755Z AUTO 00000KT 10SM CLR 26/06 A3014 RMK AO2

METAR K22N 111815Z AUTO 05003KT 10SM CLR 25/06 A3014 RMK AO2

Beechcraft C23 Sundowner, N997V, incident occurred on September 10, 2025, at South Bend International Airport (SBN/KSBN), South Bend, Indiana

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

- History of Flight:
On September 10, 2025, at about 2206 local time, a privately-registered Beechcraft C23 Sundowner, N997V, sustained unknown damage when it was involved in an incident at South Bend International Airport (SBN/KSBN), South Bend, Indiana. The pilot and passenger onboard was not injured. The airplane was originating at the time.

According to an FAA report issued on September 11, "aircraft door opened after departure, returned to airport, landed, veered off runway damaging wings, gear collapsed and incurred a propeller strike."

ADS-B data shows that the airplane departed runway 9R and entered a climbing left turn to pattern altitude before it landed back on the same runway. (figure 1)

(Note: at this time it is an incident because no photos are available/damage is still unknown)

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

- METARs:

METAR KSBN 102354Z 35006KT 10SM CLR 21/12 A3014 RMK AO2 SLP205 T02110122 10267 20211 53001

METAR KSBN 110054Z 00000KT 10SM CLR 18/12 A3015 RMK AO2 SLP207 T01830117

Ground collision: Bombardier CRJ-200LR, N420AW, accident occurred on February 1, 2025, at Chicago O’Hare International Airport (ORD/KORD), Chicago, Illinois

• Location: Chicago, Illinois 
• Accident Number: DCA25LA120 
• Date & Time: February 1, 2025, 19:02 Local 
• Registration: N420AW 
• Aircraft: BOMBARDIER INC CL-600-2B19 
• Aircraft Damage: Substantial 
• Defining Event: Ground collision 
• Injuries: 1 Serious, 13 None 
• Flight Conducted Under: Part 121: Air carrier - Scheduled

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

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

A serious injury was sustained by a tug driver following a collision with the left wing of Air Wisconsin flight 6181, a CRJ-200, during taxi operations at Chicago O’Hare International Airport (ORD). No injuries were reported among the airplane’s crew or passengers. Night visual meteorological conditions (VMC) prevailed at the time of the accident.

Flight 6181 landed at ORD and was initially held at the B Pad for an open gate (see Figure 1). Once cleared, the aircraft proceeded southbound on Taxiway A under a standard clearance. The first officer was actively monitoring both ramp and ground control frequencies during the taxi.

The captain reported first observing the tug on Taxiway B as the tug began crossing at the access road. The tug appeared to be slowing down suggesting an intent to stop. The captain could not recall whether the tug’s headlights were illuminated and believed he saw the vehicle using ambient lighting.

After briefly diverting attention toward the gate area, the captain looked back and recognized an imminent collision with the tug. Braking was initiated immediately by the captain, but the impact occurred shortly thereafter. The captain described the impact as “not that bad” and believed the tug had struck the wingtip. The flight crew then communicated with the flight attendants, followed by dispatch via the Aircraft Communications Addressing and Reporting System (ACARS).

According to the tug driver, while returning from the international terminal, the vehicle approached the service road leading to the L gates. Before entering the road and crossing taxiway B, the tug came to a complete stop at the designated stop sign and the driver observed an airplane taxiing outbound on Taxiway B. The driver checked both directions and waited until the outbound aircraft cleared the taxiway. The driver also verified that no aircraft were approaching from behind or the opposite direction before proceeding to cross the taxiways (A&B).

The driver stated that as the tug was crossing the taxiways, the left wing of flight 6181, approaching on taxiway A, was not visible until the last moment, leaving insufficient time to react. He also noted the absence of a nose-gear light on flight 6181, which may have contributed to the tug driver not detecting the presence of flight 6181 before the collision.

The collision resulted in the tug overturning and trapping the driver, leading to serious injury. Post-flight inspection revealed substantial damage to the leading-edge front spar of the airplane’s left wing. The tug driver emphasized that had he been aware of the airplane’s presence, he would not have entered the intersection.

According to the Chicago Department of Aviation (CDA) ground motor vehicle operating regulations manual, dated August 2023, a driver must stop prior to initiating the crossing of the taxiways A, B, and V to determine if the crossing could be accomplished without stopping in the islands between the taxiways. Vehicles on service roads must yield to vehicles crossing taxiways.

- Probable Cause: The tug driver’s failure to ensure the taxiway was clear of aircraft prior to crossing, resulting in a collision with the left wing of the taxiing aircraft. Contributing to the accident was the limited visibility of the aircraft due to ambient lighting conditions and the absence of the aircraft’s nose-gear light, which reduced the tug driver’s ability to detect the aircraft’s presence in time to avoid the collision.