ERA24LA238 · Aeronca 11AC
Aeronca 11AC · Accident: loss of control on ground during takeoff
Event
- NTSB case
- ERA24LA238
- 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
- Event fatalities
- Unknown
- 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
- N9418E
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 78 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
- Takeoff
- 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 had previously performed three uneventful landings and elected to depart for a final landing. The pilot initiated the takeoff roll from but started to lose directional control, drifting from one side of the runway to the other. When the left main tire was in tall vegetation adjacent to the runway he decided to continue the takeoff but the airplane veered more to the left and entered taller vegetation. While slowing the airplane nosed over, and both of the right wing’s lift struts were substantially damaged. The pilot reported, and a postaccident examination of the airplane confirmed, that there were no preimpact mechanical malfunctions or failures of the airplane that would have precluded normal operation.
Probable cause
The pilot’s failure to maintain directional control during the takeoff roll resulting in a runway excursion, and subsequent nose over.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA24LA238
- Event ID
- 20240603194362
- Case number
- ERA24LA238
- 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, cause areas. 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: 126ffbd332b4b5bce19b4f504ac86d4a9eb93e9215218d31e1739ef358d94813; retrieved 2026-09-16T18:49:39.790Z.