CHI01LA323 · Aeronca 7EC
Aeronca 7EC · Accident: loss of control on ground/water during takeoff
From Leaders Clear Lake Airport (8Y6) to Sleepy Eye Municipal Airport (Y58)
Event
- NTSB case
- CHI01LA323
- 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 7EC
- Aircraft type
- Aeronca 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
- N81910
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Leaders Clear Lake Airport (8Y6), Clear Lake, MNTo Sleepy Eye Municipal Airport (Y58), Sleepy Eye, MN
- 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
- Takeoff · roll/run
- First occurrenceThe 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/water
- 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
- Pilot in command › Directional control, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The aircraft went off of the left side of the runway during takeoff and nosed over. The pilot said in a written report, "I started the take off on the paved runway, which is 25 feet wide. The airplane veered to the left shortly after the tail came up and although I was using full right rudder, I was not able to straighten the airplane out. I got about a foot high and I was in a soybean field adjacent to runway 36. I attempted to correct the direction but hit first the right wheel and then the left wheel. When the left wheel hit, we ground looped. During the ground loop the airplane flipped over and the left wing was broken. The ground is relatively level at the airport and the 25 foot wide paved runway is located in the center of the 3000 foot by 150 foot runway 18-36." The pilot listed no mechanical malfunctions or failures is his report. No anomalies were found with respect to the airplane that could be associated with a pre-impact condition.
Probable cause
The pilot not maintaining directional control of the airplane during the takeoff. A factor was the soybean crop.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI01LA323
- Event ID
- 20011004X02037
- Case number
- CHI01LA323
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 73125a71e3ad3546e1b0e308115eb9a32581892244ab16100641f5506002418d; retrieved 2026-09-22T11:33:22.105Z.