ERA23LA002 · Aeronca 7AC
Aeronca 7AC · Accident: flight control system malfunction/failure during takeoff
Event
- NTSB case
- ERA23LA002
- 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
- 0
- 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 7AC
- 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
- N3005E
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 76 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
- Flight control system malfunction/failure
- 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 systems
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airplane had been in maintenance for repair work on the airplane’s tail section. On the first flight after the completed work, following a preflight inspection and engine run-up, the pilot taxied the airplane to the runway for departure. During the takeoff roll, when the pilot applied forward stick controls to raise the tail, the tail did not rise, and the airplane instead “shot straight up, stalled, then descended nose-first onto the runway.”
Examination of the airplane by a Federal Aviation Administration inspector revealed substantial damage to the fuselage. The inspector also noted that the elevator control cables were installed incorrectly such that the elevator moved in the direction opposite to that commanded.
Probable cause
The incorrect (reverse) rigging of the elevator cables by maintenance personnel and their subsequent failure to verify that the rigging was correct during post-maintenance checks and the pilot's inadequate preflight check.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA23LA002
- Event ID
- 20221004106053
- Case number
- ERA23LA002
- 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: cccb884e50dd57f2720a249d8f6cd94d01886e422837170d670f01c74e73524e; retrieved 2026-09-16T16:10:44.915Z.