WPR20CA058 · Aeronca 11AC
Aeronca 11AC · Accident: loss of control on ground during landing
From Montgomery-Gibbs Executive Airport (MYF) to Montgomery-Gibbs Executive Airport (MYF)
Event
- NTSB case
- WPR20CA058
- 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
Aeronca 11AC
- Aircraft type
- Aeronca 11
- 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
- N9510E
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Montgomery-Gibbs Executive Airport (MYF), San Diego, CATo Montgomery-Gibbs Executive Airport (MYF), San Diego, CA
- Aircraft age
- About 73 years (built 1946)
- 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
- Environmental issues › Conditions/weather/phenomena
- Environmental issues › Physical environment
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that, due to a quartering tailwind, he conducted a wheel landing in the tailwheel-equipped airplane. Shortly after touchdown, the airplane was pushed toward the left side of the runway. The pilot attempted to correct the drift by applying full right rudder and power to no avail. The airplane subsequently struck a sign along the edge of the runway and ground looped, which resulted in substantial damage to the aft fuselage. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.
Probable cause
The pilot's failure to maintain directional control during the landing roll with a quartering tailwind, which resulted in a collision with an airport sign and subsequent ground-loop.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR20CA058
- Event ID
- 20200106X50409
- Case number
- WPR20CA058
- 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: 7a171b0dfba7a8e8543c6b1eb747d414d4115a4fe2283a3ad1502aa3497ac24e; retrieved 2026-09-16T10:52:26.282Z.