FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR13CA255 · Bellanca 7ECA

31 May 2013 · San Martin, CA, United States

Amelia Reid Aviation Bellanca 7ECA · Accident: loss of control on ground during landing

From Reid-Hillview Airport of Santa Clara County (RHV) to San Martin Airport (E16)

Report a problem

Event

NTSB case
WPR13CA255
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Bellanca 7ECA

Aircraft type
Bellanca 7
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N5032G
Onboard fatalities
Unknown
Route
From Reid-Hillview Airport of Santa Clara County (RHV), San Jose, CATo San Martin Airport (E16), San Martin, CA
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Landing · landing roll
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Loss of control on ground
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot reported that as she approached the airport to land she called for traffic advisories, however, received no response. She flew over the airport to observe the windsocks, which are located at each end of the runway, and elected to land on runway 14. During the landing roll, the airplane made a sudden turn to the right, exited the right side of the runway, and came to rest on the grass. During the accident sequence the airplane’s left wing sustained substantial damage. At the time of the accident, the airport’s weather system reported wind from 340 degrees at 10 knots. The pilot reported no mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation.

Probable cause

The pilot’s failure to maintain directional control during the landing roll.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR13CA255
Event ID
20130531X12801
Case number
WPR13CA255
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 139343e0226f51234a2bbc1c53471d85c0e2f48acd91037f998946e9d989b558; retrieved 2026-09-15T21:43:55.850Z.