20251002019372I

Incident · Minor damage

FAA incident report · Piper Archer · MI · October 2, 2025

Date
October 2, 2025 · 14:00 local
Place
MI
Phase of flight
Cruise/Level Flight
Operating rules
General operating rules (Part 91)
Collision
Midair collision
Damage
Minor damage
Aircraft
N9659W
Reported as
Piper Archer
People aboard
1
Fatal injuries
0
Other injuries
0

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry by N-number and event date, checked against the reported make and model; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

While in cruise at 3000 feet, the pilot saw something fly over top of his wing, and subsequently heard a thud near the rear of the aircraft. Pilot then tested the flight controls to ensure there was no damage or disconnection in the flight control surfaces. Upon landing, the pilot observed damage to the leading edge of the stabilator. The damage appeared to be caused by metal to metal contact and he assumed it was a drone that caused the damage, as it was not consistent with a bird strike in his opinion. Pilot then called to report the incident to the FSDO.

As the FAA filed it

WHILE IN CRUISE AT 3000 FEET, THE PILOT SAW SOMETHING FLY OVER TOP OF HIS WING, AND SUBSEQUENTLY HEARD A THUD NEAR THE REAR OF THE AIRCRAFT. PILOT THEN TESTED THE FLIGHT CONTROLS TO ENSURE THERE WAS NO DAMAGE OR DISCONNECTION IN THE FLIGHT CONTROL SURFACES. UPON LANDING, THE PILOT OBSERVED DAMAGE TO THE LEADING EDGE OF THE STABILATOR. THE DAMAGE APPEARED TO BE CAUSED BY METAL TO METAL CONTACT AND HE ASSUMED IT WAS A DRONE THAT CAUSED THE DAMAGE, AS IT WAS NOT CONSISTENT WITH A BIRD STRIKE IN HIS OPINION. PILOT THEN CALLED TO REPORT THE INCIDENT TO THE FSDO.

Other aircraft in the event · 1

Each aircraft in a collision has its own report.

NONEMake and model not reportedNo report for this aircraft in the release