ERA22LA329 · Aeronca 7AC
Aeronca 7AC · Accident: fuel exhaustion en route
From South Lakeland Airport (X49) to Zephyrhills Municipal Airport (ZPH)
Event
- NTSB case
- ERA22LA329
- 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
- Event fatalities
- Unknown
- Ground fatalities
- Unknown
- 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
- N84423
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From South Lakeland Airport (X49), Lakeland, FLTo Zephyrhills Municipal Airport (ZPH), Zephyrhills, FL
- 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
- En route · cruise
- 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 exhaustion
- 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 › Fluids/miscellaneous hardware
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
About 5 to 10 minutes after takeoff, the engine lost total power. The pilot performed a forced landing to a field, during which the airplane collided with a fence and drainage pipe, resulting in substantial damage. Examination of the engine and ignition system did not reveal any preimpact mechanical malfunctions. Examination of the fuel system revealed that the carburetor was absent of fuel and only a trace amount of fuel remained in the gascolator. A subsequent borescope examination of the fuel tank revealed that it was intact and that a small, immeasurable amount of fuel was in one corner of the tank, but the tank was otherwise empty. Based on the lack of mechanical anomalies and the absence of fuel in the intact fuel tank, it is likely that the loss of engine power was the result of fuel exhaustion.
Probable cause
A total loss of engine power due to fuel starvation as a result of the pilot’s inadequate preflight fuel planning.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA22LA329
- Event ID
- 20220722105547
- Case number
- ERA22LA329
- 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: 2f021f8bc697b15baaa4c7d4a483ded89f4da43beb14347c457ab4936c998cb4; retrieved 2026-09-16T15:29:49.541Z.