# Incident 20260826011409I: Beech M35, San Marcos, TX, August 26, 2026

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: August 26, 2026, 12:49 local time
- Place: San Marcos, TX
- Airport: San Marcos Regional Airport
- Damage: No damage
- Phase of flight: Landing: Approach
- Operating rules: General operating rules (Part 91)
- Location: 29.8927° N, 97.8630° W: Placed by OpenAirDocs at SAN MARCOS RGNL (HYI), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=29.8927&lon=-97.8630&mi=10
- Aircraft: N332Z, registered now (https://openairdocs.org/aircraft/N332Z) (OpenAirDocs)
- Registry model: Beech M35 (registry code 1151526, https://openairdocs.org/model/beech-m35) (OpenAirDocs)
- Registry engine: Continental I0-470 series (registry code 17027, https://openairdocs.org/engine/continental-i0-470-series) (OpenAirDocs)
- Reported make and model: BEECH M35
- Reported engine: CONT MOTOR I0-470 SERIES
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Private pilot
- Pilot flight hours: 925 total, 135 in this make and model, 15 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20260826011409I

## Narrative

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

ENROUTE FROM E70 [HUBER AIRPARK, SEGUIN, TX] TO HYI [SAN MARCOS REGIONAL AIRPORT]. PILOT REPORTED 34 GALLONS ONBOARD. ENTERED RIGHT BASE RUNWAY 08. MID FIELD TOWER REQUESTED A 360° FOR SPACING. WHEN THE TURN WAS INITIATED THE ENGINE COUGHED. THE PILOT SWITCHED TO THE FULLEST FUEL TANK INDICATED [AUX]. ENGINE CONTINUED IN FAILURE MOD AND LANDED IN PLOWED FIELD ~MILE SOUTH OF THE AIRPORT.

## Other reports on N332Z (1)

Matched to the same aircraft by N-number and date.

- [Incident 19810203019169I](https://openairdocs.org/incident/19810203019169I), Feb 3, 1981: Beech M35 (N332Z), San Diego, CA, Minor damage. Pilot stated he moved gear switch down but failed to check position> problem in normal system> emergency system ok>

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.