# Incident 20240830014849I: Beech 35-C33, San Marcos, TX, August 30, 2024

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: August 30, 2024, 12:44 local time
- Place: San Marcos, TX
- Damage: Minor damage
- Phase of flight: Landing: Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 29.8833° N, 97.9414° W: Placed by OpenAirDocs: center of San Marcos, TX, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=29.8833&lon=-97.9414&mi=10
- Aircraft: N9437S, registered now (https://openairdocs.org/aircraft/N9437S) (OpenAirDocs)
- Registry model: Beech 35-C33 (registry code 1151408, https://openairdocs.org/model/beech-35-c33) (OpenAirDocs)
- Registry engine: Continental I0-470 series (registry code 17027, https://openairdocs.org/engine/continental-i0-470-series) (OpenAirDocs)
- Reported make and model: BEECH 35-C33
- Reported engine: CONT MOTOR I0-470 SERIES
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Private pilot
- Pilot flight hours: 510 total, 5 in this make and model, 19 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20240830014849I

## Narrative

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

^PRIVACY DATA OMITTED^ A BE-33 ^PRIVACY DATA OMITTED^ WAS BEING OPERATED ON A PERSONAL FLIGHT UNDER PART 91 RULES. THE AIRCRAFT DEPARTED FROM KTDP TO KHYI WITH THE ^PRIVACY DATA OMITTED^/PIC AND ONE PASSENGER, (^PRIVACY DATA OMITTED^). THE AIRCRAFT WAS CLEARED TO LAND ON RUNAY 08 AND LANDED GEAR UP. A PHONE CONVERSATION WAS PERFORMED WITH THE PILOT AND THE ROC. THE PILOT STATED THE GEAR WOULD NOT COME DOWN AND THAT HIS ^PRIVACY DATA OMITTED^ WAS 'FREAKING OUT'. HE ALSO STATED THAT HE TRIED TO CRANK THE GEAR VIA THE EMERGENCY EXTENSION HANDLE, HOWEVER HIS "100 POUND" BAGGAGE IN THE REAR SEAT HAD SHIFTED FORWARD SOMETIME DURING THE FLIGHT AND BLOCKED/PREVENTED HIM FROM OPERATING THE EMERGENCY EXTENSION HANDLE TO EXTEND THE LANDING GEAR. AT NO TIME DID HE STATE HE NOTIFED ATC. THIS INSPECTOR CONTACTED ATC. ATC STATED AT NO TIME DID THE PIC OF ^PRIVACY DATA OMITTED^ NOTIFY THEM OF ANY LANDING GEAR ISSUE NOR DID HE DECLARE AN EMERGENCY.

NO EVIDENCE TO SUPPORT A REGULATORY NONCOMPLIANCE OTHER THAN THE FAILURE OF THE PIC TO PROPERLY STOW BAGGAGE TO PREVENT INFLIGHT SHIFTING IN AN UNSAFE CONDITION.

AMENDMENT ADDED 10/18/2024 - SPOKE WITH THE A&P WHO HELPED RECOVER THE AIRCRAFT. HE STATED THAT THE EMERGENCY EXTENSION HANDLE HAD TO BE DISENGAGED IN ORDER TO NORMALLY EXTEND THE LANDING GEAR AFTER LIFTING THE AIRCRAFT. HE STATED THAT ENGAGING THE EMERGENCY EXTENSION HANDLE DISENGAGES THE NORMAL EXTENSION SWITCH.

## Other reports on N9437S (1)

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

- [Incident 20080515836639I](https://openairdocs.org/incident/20080515836639I), May 15, 2008: Beech 35C33 (N9437S), Penrose, NC, Minor damage. (-23) PIC stated he was returning to home base after flight test of replacement propeller, entered a right downwind to runway 27, completed a pre-landing…

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.