FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA24LA334 · Aeronca 7AC

16 Jun 2024 · Topsham, ME, United States

Aeronca 7AC · Accident: fuel related while maneuvering

From Brunswick Executive Airport (BXM) to an unrecorded destination

Report a problem

Event

NTSB case
ERA24LA334
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
N3854E
Operator
Unknown
Onboard fatalities
Unknown
Route
From Brunswick Executive Airport (BXM), Brunswick, METo not recorded
Aircraft age
About 77 years (built 1947)
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
Maneuvering · low-altitude flying
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
Fuel related
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

  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Action/decision

Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.

NTSB narrative

The pilot was on a local flight following an annual inspection. For the first 45 minutes of flight, the pilot remained in the traffic pattern where he operated from a grass runway. He then departed the airport traffic pattern and then flew at about 1,500 ft above ground level (agl) over rivers and open water for another 45 minutes. He began a climbing 180° turn back toward the airport at full power when the engine lost partial power. The pilot attempted to troubleshoot the loss of engine power by applying carburetor heat and manipulating the throttle without success. He was unable to maintain altitude and, with no desirable locations available to land, the pilot executed a forced landing to a river, which resulted in substantial damage to the left wing. The airplane was recovered from the river and a postaccident examination of the airplane’s fuel system and engine was conducted. Water was present in the fuel system and disassembly of the engine’s carburetor revealed a “white gummy substance” throughout the unit that was blocking the main fuel jet. There were no other mechanical malfunctions or anomalies with the airframe or engine that would have precluded normal operation. A sample of the unknown substance from the fuel system was analyzed and found to most likely be a plant or other naturally occurring cellulosic material. A review of the maintenance logbooks for the airplane revealed that the fuel tank was emptied and flushed about one month before the accident, during the most recent annual inspection. The fuel strainer, carburetor inlet screen, carburetor bowl was “inspected and cleaned” at the same time. According to the owner, this inspection and cleaning was the result of a fuel contamination issue following the restoration of the airplane. Considering that the carburetor was inspected and cleaned during the annual inspection, just a month before the accident, and that the engine had operated normally for about 90 minutes of flight, it is likely that the contamination found in the carburetor was the result of the water immersion in the river. The temperature and dew point at the time of the accident were conducive to the formation of serious icing at glide engine power settings. Considering that the airplane operated from a grass runway and flew at low altitudes over rivers and open water for about 90 minutes, it is likely that the airplane encountered higher relative humidity than anticipated, which resulted in a partial loss of engine power due to carburetor icing. Additionally, because the pilot did not activate the carburetor heat until after the engine had begun losing power, the likelihood that the icing could be remediated and engine power restored was substantially reduced.

Probable cause

A total loss of engine power due to carburetor icing as a result of the pilot’s delayed application of carburetor heat.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA24LA334
Event ID
20240801194822
Case number
ERA24LA334
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, coordinates, 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: cbfe7e2ce9439438a0c217c60eb00b23bb8ead4fb380c04f18d50103a6549c4b; retrieved 2026-09-16T19:07:05.732Z.