# Incident 20260215000839I: Mooney M20F, San Antonio, TX, February 15, 2026

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: February 15, 2026, 11:57 local time
- Place: San Antonio, TX
- Airport: Stinson Municipal
- Damage: Minor damage
- Phase of flight: Landing: Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 29.3370° N, 98.4710° W: Placed by OpenAirDocs at STINSON MUNI (SSF), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=29.3370&lon=-98.4710&mi=10
- Aircraft: N9504M, registered now (https://openairdocs.org/aircraft/N9504M) (OpenAirDocs)
- Registry model: Mooney M20F (registry code 5870214, https://openairdocs.org/model/mooney-m20f) (OpenAirDocs)
- Registry engine: Lycoming I0360 series (registry code 41515, https://openairdocs.org/engine/lycoming-i0360-series) (OpenAirDocs)
- Reported make and model: MOONEY M20F
- Reported engine: LYCOMING I0360 SER
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Private pilot, student
- Pilot flight hours: 185 total, 99 in this make and model, 45 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20260215000839I

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

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.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft 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. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.