FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC00LA091 · Aeronca 7AC

7 Mar 2000 · Pawling, NY, United States

Aeronca 7AC · Accident: loss of engine power en route

From Robertson Field (4B8) to 6KN4 · KOBELT, NY

Report a problem

Event

NTSB case
NYC00LA091
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
N474HH
Operator
Unknown
Onboard fatalities
Unknown
Route
From Robertson Field (4B8), PAINVILLE, CTTo 6KN4 · KOBELT, NY
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 · 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
Loss of engine power
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
Tree(s)
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

No findings designated as a cause are recorded in the NTSB data yet.

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

NTSB narrative

Twenty minutes after takeoff, and at a cruise altitude of 3,500 feet msl, the airplane's engine began to surge. The pilot attempted to identify the problem. He switched the magnetos on and off, and observed no change. He applied carburetor heat, but the engine ran even rougher so he selected carburetor heat off. After 5 minutes, the pilot cycled the fuel selector; simultaneously he experienced a further drop in engine power. Unable to make an airport, the pilot maneuvered the airplane to land in an open field. On final, the airplane struck trees short of the pilot's intended touchdown point, and then impacted the ground. A FAA Inspector stated that he rotated the propeller and obtained good compression. He added that the airplane was placard for auto-gas only, and that it was equipped with new magnetos, wires, and plugs. He also stated that the fuel inside the fuel tank smelled 'rancid.'

Probable cause

Loss of engine power for undetermined reasons.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC00LA091
Event ID
20001212X20718
Case number
NYC00LA091
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: 21eb56360d6de5a063a0fec640fab92d35b96225067384ed84cbdb979c8bf0fb; retrieved 2026-09-21T20:17:34.864Z.