FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI96LA023 · Aeronca 7AC

29 Oct 1995 · Lapeer, MI, United States

Aeronca 7AC · Accident: total loss of engine power (non-mechanical) en route

From D95 to an unrecorded destination

Report a problem

Event

NTSB case
CHI96LA023
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
N84124
Operator
Unknown
Onboard fatalities
Unknown
Route
From D95To 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
En route · climb to cruise
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
Total loss of engine power (non-mechanical)
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
Fuel exhaustion; Stall
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

  • Fluid, fuel › Exhaustion
  • Pilot in command › In-flight planning/decision, improper
  • Pilot in command › Stall, inadvertent

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

NTSB narrative

THE AIRPLANE HAD CLIMBED TO 500 FEET ABOVE GROUND LEVEL AFTER TAKEOFF WHEN THE ENGINE LOST POWER. THE PILOT TURNED THE AIRPLANE AROUND TO LAND ON THE OPPOSITE RUNWAY. WHEN THE AIRPLANE CROSSED THE APPROACH END OF THE RUNWAY, 'THE ENGINE STARTED RUNNING AGAIN.' BEFORE THE PILOT COULD CLOSE THE THROTTLE, 'THE AIRPLANE BALLOONED INTO THE AIR.' BECAUSE OF HIS ALTITUDE AND A 10 KNOT TAILWIND, THE PILOT DETERMINED THAT HE WOULD NOT BE ABLE TO LAND THE AIRPLANE WITHOUT RUNNING OFF THE END OF THE RUNWAY. HE THEN DECIDED TO ATTEMPT A LANDING ON THE AIRPORT'S DIAGONAL RUNWAY WHICH REQUIRED THE PILOT TO EXECUTE A LEFT 130 DEGREE HEADING CHANGE AT LOW ALTITUDE AND AIRSPEED. THE AIRPLANE 'STALLED,' AND IMPACTED THE TERRAIN LEFT WING FIRST. EXAMINATION OF THE WRECKAGE SHOWED NO EVIDENCE OF FUEL AT THE ACCIDENT SITE. EXAMINATION OF THE AIRPLANE'S FUEL SYSTEM SHOWED NO INDICATIONS OF FUEL PRIOR TO IMPACT. THE AIRPLANE DID NOT HAVE FUEL QUANTITY INDICATOR INSTALLED.

Probable cause

fuel exhaustion resulting in engine failure, the inadvertant stall, and improper decision by the pilot to attempt a large heading change at low altitude and airspeed. A factor relating to this accident is no fuel quantity gage installed in the airplane.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI96LA023
Event ID
20001207X04676
Case number
CHI96LA023
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: 0e61e60020bdd702f736e69e9458e26dda4666ee2457cd615da91e70366e531d; retrieved 2026-09-21T22:01:20.929Z.