FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA05CA094 · Aeronca 7AC

18 Apr 2005 · Lakeland, FL, United States

Aeronca 7AC · Accident: on ground/water collision with terrain/water during landing

From Mid Florida at Eustis Airport (X55) to Lakeland Linder International Airport (LAL)

Report a problem

Event

NTSB case
MIA05CA094
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
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
N4264E
Operator
Unknown
Onboard fatalities
Unknown
Route
From Mid Florida at Eustis Airport (X55), Eustis, FLTo Lakeland Linder International Airport (LAL), Lakeland, FL
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
Landing · landing roll
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
On ground/water collision with terrain/water
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 › Directional control, not maintained
  • Pilot in command › Recovery from bounced landing, improper

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot stated that during landing the airplane veered off to the left and the left wing started to lower towards the runway; he added power to increase effectiveness of the rudder to try to straighten out. The airplane straightened out and ran into a ditch. The pilot stated there were no mechanical failures or malfunctions to the airplane or any of its systems prior to the accident. A witness stated the airplane landed and had a small bounce; both wheels were on the ground when it looked as if the wind picked up the left wing. The airplane came back down but sideways and spun in a circle. It then headed down into a ditch and came out the other side becoming briefly airborne before impacting the grass in a nose down attitude and spinning around.

Probable cause

The pilot's improper recovery from a bounced landing, and his failure to maintain directional control during landing resulting in the airplane departing the runway and colliding with a ditch.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA05CA094
Event ID
20050510X00581
Case number
MIA05CA094
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, coordinates. 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: 36b9b581067204ddc730d42caaf67492315aad180a9f5a5aa13220642d2f7a58; retrieved 2026-09-21T19:02:38.729Z.