# Incident 19960320007669I: Beech 3533, Visalia, CA, March 20, 1996

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: March 20, 1996, 18:40 local time
- Place: Visalia, CA
- Airport: Visalia Municipal
- Damage: Minor damage
- Phase of flight: Level Off Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 36.3186° N, 119.3929° W: Placed by OpenAirDocs at VISALIA MUNI (VIS), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=36.3186&lon=-119.3929&mi=10
- Aircraft: 634V9 (not matched to a registry record)
- Reported make and model: BEECH 3533
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 3,800 total, 600 in this make and model, 11 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19960320007669I

## Narrative

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

NARRATIVE: A BEECHCRAFT MODEL BE-35-33, N634V, DEPARTED FRESNO AIR TERMINAL (FAT) ON MARCH 20, 1996 TO GO TO VISALIA, CA (VIS) TO PRACTICE NIGHT TAKEOFF AND LANDINGS. THE PILOT FLEW THE ILS TO RUNWAY 30 AND PUT THE LANDING GEAR LEVER DOWN APPROACHING THE AIRPORT. HE LANDED AT APPROXIMATELY 1840 PST WITH THE LANDING GEAR RETRACTED. HE NOTICED THAT THE GEAR POSITION LIGHT WAS NOT INDICATING DOWN (GREEN), BUT THOUGHT THE MECHANICAL INDICATOR WAS READING THAT THE LANDING GEAR WAS DOWN. HE KNEW THAT THE LANDING GEAR WAS NOT DOWN WHEN THE AIRCRAFT TOUCHED THE GROUND AND SLID TO A STOP. IN RETROSPECT THE COMMERCIAL PILOT STATED THAT HE THOUGHT THAT HE HEARD A BUZZING NOISE DURING THE LANDING FLARE BUT DISMISSED IT AS RADIO FEED BACK. APPARENTLY THE PILOT SAID IT MUST HAVE BEEN THE LANDING GEAR WARNING HORN. THE LANDING GEAR MOTOR CIRCUIT BREAKER WAS FOUND IN THE POPPED POSITION AFTER THE LANDING. THE PILOT, SOLE OCCUPANT WAS UNINJURED AND NO FLIGHT PLAN WAS FILED. THIS INCIDENT CLOSED.

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.