FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL00LA067 · Aeronca 11AC

22 Jun 2000 · Tylertown, MS, United States

Aeronca 11AC · Accident: airframe, component or system failure during landing

From McComb-Pike County Airport / John E Lewis Field (MCB) to T36

Report a problem

Event

NTSB case
ATL00LA067
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 11AC

Aircraft type
Aeronca 11
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
N85861
Operator
Unknown
Onboard fatalities
Unknown
Route
From McComb-Pike County Airport / John E Lewis Field (MCB), MC COB, MSTo T36
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
Airframe, component or system failure
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

  • Landing gear, tailwheel assembly › Separation

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

NTSB narrative

According to the CFI who was occupying the right seat, they had been practicing both three-point and wheel landings. He said that this particular landing was a three-point landing. He said that when they touched down, the tail-wheel shook excessively back and forth at first and then it was smooth. He stated that the airplane veered right while both of them were pushing on the left rudder. The airplane departed the right side of the runway turned around about 180 degrees, slid left into a ditch and collapsed the left main landing gear. According to the CFI, and FAA Inspector, a tail-wheel spring and associated parts had pulled apart from the tail-wheel and were later found on the runway near the point where the airplane veered right, off of the runway.

Probable cause

Loss of directional control due to separation of the tail-wheel spring assembly. A factor was the ditch which run adjacent to the runway.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL00LA067
Event ID
20001212X21161
Case number
ATL00LA067
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2000-06-23.
  • API snapshot SHA-256: 49d76252ee433e8d0f766f933d4d9dad01734cdcb5482ea1e5162b3999bf46b5; retrieved 2026-09-22T12:46:53.987Z.