20260215000839I

Incident · Minor damage

FAA incident report · Mooney M20F · San Antonio, TX · February 15, 2026

Date
February 15, 2026 · 11:57 local
Place
San Antonio, TX
Airport
Stinson Municipal
Phase of flight
Landing: Touchdown
Operating rules
General operating rules (Part 91)
Damage
Minor damage
Aircraft
N9504M
Reported as
Mooney M20F
Reported engine
Lycoming I0360 series
People aboard
2
Fatal injuries
0
Other injuries
0
Pilot’s certificates
Private pilot, student
Pilot’s flight hours
185 total99 in this make and model45 in the last 90 days

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.

During our investigation, the pilot in command stated that he was flying from kela to kssf. The pilot in command stated that the flight was unevenful up until a few minutes before the incident on runway 32.

The pilot in command stated that he experienced a cockpit distraction on base and again on final, interrupting his pre-landing and final gumps check.

Around 5-6 miles from the airport the pilot in command was given a squawk code by the tower and a vector of 230 to enter base 32, while he was in the middle of his pre-landing checklist. His normal sequence of checklists was interrupted by the squawk and vector, and he inadvertently failed to complete it after the interruption.

Right after his turn from base to final, the pilot side window popped open. At this point he would do his gumps check on final, but was focused instead on the distraction of the window plus gusty wind conditions and focused his attention on getting down to the runway safely.

Upon landing he realized the gear was not extended, and maintained his wings level, and performed an emergency shutdown of the engine and electrical systems - after informing the tower of the emergency.

As the FAA filed it

DURING OUR INVESTIGATION, THE PILOT IN COMMAND STATED THAT HE WAS FLYING FROM KELA TO KSSF. THE PILOT IN COMMAND STATED THAT THE FLIGHT WAS UNEVENFUL UP UNTIL A FEW MINUTES BEFORE THE INCIDENT ON RUNWAY 32.

THE PILOT IN COMMAND STATED THAT HE EXPERIENCED A COCKPIT DISTRACTION ON BASE AND AGAIN ON FINAL, INTERRUPTING HIS PRE-LANDING AND FINAL GUMPS CHECK.

AROUND 5-6 MILES FROM THE AIRPORT THE PILOT IN COMMAND WAS GIVEN A SQUAWK CODE BY THE TOWER AND A VECTOR OF 230 TO ENTER BASE 32, WHILE HE WAS IN THE MIDDLE OF HIS PRE-LANDING CHECKLIST. HIS NORMAL SEQUENCE OF CHECKLISTS WAS INTERRUPTED BY THE SQUAWK AND VECTOR, AND HE INADVERTENTLY FAILED TO COMPLETE IT AFTER THE INTERRUPTION.

RIGHT AFTER HIS TURN FROM BASE TO FINAL, THE PILOT SIDE WINDOW POPPED OPEN. AT THIS POINT HE WOULD DO HIS GUMPS CHECK ON FINAL, BUT WAS FOCUSED INSTEAD ON THE DISTRACTION OF THE WINDOW PLUS GUSTY WIND CONDITIONS AND FOCUSED HIS ATTENTION ON GETTING DOWN TO THE RUNWAY SAFELY.

UPON LANDING HE REALIZED THE GEAR WAS NOT EXTENDED, AND MAINTAINED HIS WINGS LEVEL, AND PERFORMED AN EMERGENCY SHUTDOWN OF THE ENGINE AND ELECTRICAL SYSTEMS - AFTER INFORMING THE TOWER OF THE EMERGENCY.