FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI00FA170 · Aeronca 7AC

23 Jun 2000 · Lakeville, MN, United States

Aeronca 7AC · Accident: loss of control in flight on approach

From LVN to an unrecorded destination

Report a problem

Event

NTSB case
CHI00FA170
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
1 · 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
N81681
Operator
Unknown
Onboard fatalities
Unknown
Route
From LVNTo not recorded
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
Approach · VFR pattern base
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 in flight
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Stall/spin
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 › Aircraft control, not maintained
  • Pilot in command › Stall/spin, encountered

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

NTSB narrative

The airplane impacted terrain following an in-flight loss of control while on approach to runway 12. The front seat pilot was fatally injured and the pilot rated rear seat occupant was seriously injured. A witness stated, "On several of these approaches, I noticed that the nose would rise to above level flight slightly during or after the turn, and it appeared that the application of right rudder was used to force the nose to align with the runway causing a skid during a portion of the turn. ... I commented to my wife that the technique used would likely be disastrous some day for whoever was flying the plane. ... It was apparent that the same techniques were being used on this approach, and suddenly the right wing started down, rotation began and the aircraft contacted the ground nearly straight down, maybe a block from the end of the runway facing west/northwest. The close in base leg with relatively flat turn (bank angle) and skid from right rudder application were visible before the roll started. The engine was audible, sounding as though normal full throttle had been applied, in an attempt to recover from the obvious spin that had begun. The aircraft spun to the right and hit the ground." Another witness stated, " I do not believe he was belted in - when I looked into the cockpit to check on pilot (female front seat) the rear seat belt on left side appeared to be somewhat neatly tucked in next to the seat. The right side belt was hanging out of the aircraft, which was the side he came out of." The pilot rated rear seat occupant stated that the aircraft did not have a nose up attitude before it nosed over. He stated that he and the front seat pilot were alternating flying the takeoffs and landings. He said the front pilot was flying the accident approach to land. The pilot did not describe a typical pattern when asked. He stated there was no binding in the aircraft controls and the engine was performing normally. The airplane's operator endorsed both pilots' applications for their instructor ratings. Leading edge nicks and chordwise abrasion were found on both propeller blades. Flight control continuity was established to all control surfaces. The engine exhibited a thumb compression at all cylinders. The magnetos produced a spark when rotated by hand. Control continuity to the engine was established. An aluminum colored seat belt end from the rear seat was found detached from the fastener that secured it. That fitting's hole was found deformed and a section was torn in the radius area about that hole.

Probable cause

the pilot not maintaining aircraft control and the stall/spin she encountered during the approach on base to final. A factor was the pilot passenger not detecting the remedial action needed to correct the aircraft's nose up attitude during the approach.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI00FA170
Event ID
20001212X21166
Case number
CHI00FA170
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2000-06-24.
  • API snapshot SHA-256: a0e02529d2342ef75036eeabe5ac6365c609365f210640ea2bc6de593e97bb30; retrieved 2026-09-20T21:07:17.799Z.