FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA19TA182 · Aeronca 7AC

27 May 2019 · Concord, GA, United States

Aeronca 7AC · Accident: loss of control on ground during landing

From Windrift Aerodrome (2GA5) to Windrift Aerodrome (2GA5)

Report a problem

Event

NTSB case
ERA19TA182
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
N1797E
Operator
Unknown
Onboard fatalities
Unknown
Route
From Windrift Aerodrome (2GA5), Concord, GATo Windrift Aerodrome (2GA5), Concord, GA
Aircraft age
About 73 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
Landing · landing roll
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 systems
  • Not determined › Not determined

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 reported that he approached the turf runway intending to conduct a full-stop landing. He stated that upon applying the brakes, the right brake “stuck and would not release,” which resulted in the airplane veering right. The pilot attempted to pump the brakes to release the right brake and was unable to regain directional control. The airplane traveled off the right side of the runway and impacted trees. A ground scar consistent with skidding of the right tire was observed on the turf leading up to the edge of the road near where the airplane came to rest. The spars of both wings were fractured, and the fractured wing sections were displaced aft. During a postaccident interview, the airplane’s owner reported that the brakes were “very old” and required frequent adjustments and that she had planned to replace them. Review of the airframe logbooks revealed multiple entries related to the right brakes in the 4 years before the accident.

Postaccident examination and operational testing of the brake assemblies did not reveal any evidence of preimpact mechanical malfunctions or failures that would have caused the right brake to lock.

Probable cause

The pilot's inability to maintain directional control during landing for reasons that could not be determined because postaccident examination of the airplane brake assemblies revealed no anomalies that would have caused the right brake to lock, which resulted in a runway excursion.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA19TA182
Event ID
20190527X21715
Case number
ERA19TA182
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. 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: b8d5b2e6684df7bf26a7a869893c20d61e8e06c0523da1d94341bb7866bd409d; retrieved 2026-09-16T09:03:59.875Z.