# Accident 20130531009689A: Bellanca 7ECA, San Martin, CA, May 31, 2013 - Type: FAA accident report (Accident/Incident Data System), as reported - Date: May 31, 2013, 09:55 local time - Place: San Martin, CA - Airport: South County Airport Of Santa Cla - Damage: Substantial damage - Phase of flight: Landing: Rollout - Operating rules: General operating rules (Part 91) - Location: 37.0756° N, 121.5914° W: From the FAA - Nearby events: https://openairdocs.org/map.md?lat=37.0756&lon=-121.5914&mi=10 - Aircraft: N5032G, registered now (https://openairdocs.org/aircraft/N5032G) (OpenAirDocs) - Registry model: Bellanca 7ECA (registry code 1220460, https://openairdocs.org/model/bellanca-7eca) (OpenAirDocs) - Registry engine: Lycoming 0-235 series (registry code 41505, https://openairdocs.org/engine/lycoming-0-235-series) (OpenAirDocs) - Reported make and model: BELLANCA 7ECA - Reported engine: LYCOMING 0-235C1 - People aboard: 1 - Fatal injuries: 0 - Other injuries: 0 - Pilot certificates: Private pilot - Pilot flight hours: 463 total, 210 in this make and model, 1 in the last 90 days - NTSB investigation: [NTSB WPR13CA255](https://openairdocs.org/ntsb/WPR13CA255) (OpenAirDocs) - FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/) - Page: https://openairdocs.org/incident/20130531009689A ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. ON MAY 31, 2013, AT APPROXIMATELY 0955 PACIFIC TIME, A BELLANCA 7ECA (CITABRIA) MODEL AIRCRAFT, N5032G, SUSTAINED SUBSTANTIAL DAMAGE FOLLOWING THE LOSS OF CONTROL DURING LANDING ROLLOUT AT SOUTH COUNTY AIRPORT (E16) OF SANTA CLARA COUNTY, SAN MARTIN, CALIFORNIA. THE PILOT, ^PRIVACY DATA OMITTED^, PRIVATE PILOT CERTIFICATE NUMBER ^PRIVACY DATA OMITTED^, WHO WAS THE SOLE OCCUPANT ON BOARD, WAS NOT INJURED. THE AIRCRAFT, WHICH IS REGISTERED TO AERODYNAMIC AVIATION (FORMERLY AMELIA REID AVIATION) OF SAN JOSE, CALIFORNIA, WAS BEING OPERATED IN ACCORDANCE WITH 14 CODE OF FEDERAL REGULATIONS PART 91. VISUAL METEOROLOGICAL CONDITIONS PREVAILED AT THE TIME OF THE ACCIDENT, AND NO FLIGHT PLAN HAD BEEN FILED BY THE PILOT. THE FLIGHT DEPARTED THE REID-HILLVIEW AIRPORT (RHV) IN SAN JOSE, CALIFORNIA AT APPROXIMATELY 0928 PACIFIC TIME, WITH ITS DESTINATION BEING E16. THE PILOT REPORTED TO THE FEDERAL AVIATION ADMINISTRATION (FAA) INVESTIGATOR-IN-CHARGE, THE WEATHER WAS CALM AND CLEAR, AND SHE INTENDED TO MAKE A COUPLE OF LANDINGS (IN THE PATTERN) AT E16. THE PILOT CALLED FOR TRAFFIC ADVISORIES APPROXIMATELY THREE TO FIVE MINUTES NORTH OF E16, BUT THERE WAS NO RESPONSE. SHE THEN FLEW OVER THE AIRPORT (E16) AND CHECKED THE TWO WINDSOCKS (ONE AT EACH END OF THE RUNWAY). THE PILOT FAVORED RUNWAY 14 SINCE THE WIND SPEED APPEARED TO BE MINIMAL. SHE STATED THERE WAS NO INDICATION OF A CROSSWIND PRIOR TO LANDING ON RUNWAY 14. ACCORDING TO THE PILOT, SHE MADE AN ?ABSOLUTELY FINE LANDING? ON THE RUNWAY THRESHOLD. HOWEVER, IMMEDIATELY UPON LANDING ROLLOUT, THE PILOT STATED THE AIRCRAFT MADE AN UNCOMMANDED TURN TO THE RIGHT AND DEPARTED RUNWAY 14. PRIOR TO COMING TO A REST ON THE GRASS AREA, THE LEFT MAIN LANDING GEAR BECAME DETACHED FROM THE AIRCRAFT WHICH CAUSED THE LEFT WING TO IMPACT THE GROUND CAUSING SUBSTANTIAL STRUCTURAL DAMAGE TO THE LEFT WING AND STRUTS, AS WELL AS THE FORWARD LEFT SIDE OF AIRCRAFT NEAR THE ENGINE COWLING. FURTHERMORE, THERE IS CLEAR EVIDENCE OF A PROPELLER STRIKE. A METAR WEATHER REPORT (AVIATION DIGITAL DATA SERVICE) DENOTES A 10 KNOT WIND SPEED AT E16 AT THE TIME OF THE ACCIDENT. MOREOVER, THAT INDICATES A TAILWIND WAS PRESENT WHILE LANDING ON RUNWAY 14. THE PILOT REPORTED NO MECHANICAL FAILURES OR MALFUNCTIONS WITH THE AIRCRAFT THAT WOULD HAVE PRECLUDED NORMAL OPERATIONS. THE AIRCRAFT MAINTENANCE RECORDS REVEALED THE LAST ANNUAL INSPECTION WAS PERFORMED ON AUGUST 6, 2012, AND THE 100-HOUR INSPECTION WAS COMPLIED WITH ON MAY 16, 2013. ## The NTSB's investigation of this event (1) From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. - [NTSB WPR13CA255](https://openairdocs.org/ntsb/WPR13CA255), May 31, 2013: Bellanca 7ECA (N5032G), San Martin, CA, substantial damage. Probable cause: The pilot’s failure to maintain directional control during the landing roll. ## Other reports on N5032G (6) Matched to the same aircraft by N-number and date. - [Accident 20040207000869A](https://openairdocs.org/incident/20040207000869A), Feb 7, 2004: Bbavia 7ECA (N5032G), Groveland, CA, No damage. (-23) Aircraft was high on final approach. Although "marginal" the PIC continued the approach by slipping the aircraft. The aircraft was landed hard and… - [Incident 20030618011909I](https://openairdocs.org/incident/20030618011909I), Jun 18, 2003: Bbavia 7ECA (N5032G), San Martin, CA, Minor damage. (-23) N5032G, a Bellanca 7ECA airplane, lost control while landing at San Martin, CA (south county Q99) airport and ran off the paved surface of the runway.… - [Incident 20010419006659I](https://openairdocs.org/incident/20010419006659I), Apr 19, 2001: Bbavia 7ECA (N5032G), San Jose, CA. (-23) N5032G, a Bellanca citabria model 7ECA serial number 1283-79 made an emergency landing on malech road San Jose, CA. At 11:08 PDT on April 19, 2001,… - [Incident 19990802018199I](https://openairdocs.org/incident/19990802018199I), Aug 2, 1999: Bbavia 7ECA (N5032G), San Jose, CA. (-5)Aircraft engine failed to produce power while exicuting aerobatic manuvers, pilot attempted to correct problem with no results. At approximately 3000 feet… - [Incident 19920112001689I](https://openairdocs.org/incident/19920112001689I), Jan 12, 1992: Bbavia 7ECA (N5032G), San Jose, CA, Minor damage. Lost directional control of aircraft on a crosswind landing. Veered off runway. - [Accident 19800801037419A](https://openairdocs.org/incident/19800801037419A), Aug 1, 1980: Bbavia 7ECA (N5032G), Shelter Cove, CA, Substantial damage. Pilot lost control of plane on landing, left runway, hit brush and ditch. 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.