ERA10CA321 · Aeronca 7BCM
Aeronca 7BCM · Accident: loss of control on ground during landing
From Lawrenceburg Lawrence County Airport (2M2) to William L. Whitehurst Field (M08)
Event
- NTSB case
- ERA10CA321
- 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 7BCM
- 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
- N2553B
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Lawrenceburg Lawrence County Airport (2M2), Lawrenceburg, TNTo William L. Whitehurst Field (M08), Bolivar, TN
- 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
- 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
- Loss of control on ground
- 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 › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that he was landing on runway 19, a 5,000-foot-long, 75-foot-wide asphalt runway, when the airplane encountered a sudden gust of wind. The airplane veered 90 degrees to the right, struck a runway light located about 2,000 feet from the approach end of the runway and a chain-link fence, before coming to rest in a wooded area. The airplane sustained substantial damage to both wings and the fuselage. The pilot reported 631 hours of total flight experience, which included 30 hours in the same make and model as the accident airplane, and 2 hours during the 30 days preceding the accident. He also stated that he did not experience any mechanical problems during the flight. Winds reported at an airport located about 25 miles north of the accident site, about the time of the accident, were variable at 3 knots. The pilot estimated the winds at the time of the accident were from 200 degrees at 5 knots, gusting to 20 knots.
Probable cause
The pilot's failure to maintain directional control while landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA10CA321
- Event ID
- 20100621X55821
- Case number
- ERA10CA321
- 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. 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: e2796ff6578fa371b94951e546b94a7f8915ce616915f1fccb433ed25052cdcb; retrieved 2026-09-15T14:28:49.217Z.