FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL82DA203 · American AA-1

17 Jul 1982 · Covington, TN, United States

American AA-1 · Accident: airframe, component or system failure

From Covington Municipal Airport (M04) to Covington Municipal Airport (M04)

Report a problem

Event

NTSB case
ATL82DA203
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

American AA-1

Aircraft type
American AA-1
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
N5715L
Operator
Frank E. Griffin · private individual
Onboard fatalities
Unknown
Route
From Covington Municipal Airport (M04), Covington, TNTo Covington Municipal Airport (M04), Covington, 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
Unknown
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, normal brake system › Failure, partial
  • Pilot in command › Airspeed, misjudged
  • Pilot in command › Distance, misjudged
  • Pilot in command › Go-around, not performed

Approximate · Estimated position: the centre of Covington, TN, the place the record names. Not the accident site.

NTSB narrative

PRIOR TO LANDING, THE PILOT CHECKED HIS BRAKES TO INSURE THEIR INTEGRITY AND NOTED THAT THE LEFT BRAKE DID NOT HOLD PRESSURE. HE ELECTED TO LAND ON RUNWAY 01 SINCE THE HANGAR AND RAMP AREAS WERE LOCATED AT THE NORTH END OF THE FIELD AND HE DIDN'T WANT TO TAXI A LONG WAY WITH AN INOPERATIVE BRAKE. REPORTEDLY, THE AIRCRAFT WAS HIGH AND FAST ON FINAL APPROACH AND TOUCHED DOWN ABOUT 1000 FT FROM THE DEPARTURE END OF THE 4000 FT RUNWAY. DURING THE LANDING ROLL, THE AIRCRAFT CONTINUED OFF THE END OF THE RUNWAY, HIT A DITCH AND FLIPPED OVER. THE WIND WAS REPORTED TO BE FROM 210 DEG AT 7 KTS. AN EXAMINATION OF THE AIRCRAFT REVEALED THAT THE FLAPS WERE UP. A HYDRAULIC LEAK WAS FOUND AT THE 45 DEGREE FITTING AT THE BRAKE HOUSING.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record ATL82DA203
Event ID
20020917X02782
Case number
ATL82DA203
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. 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: 0b2bc2c22d85a56746c86faae7980b59b832d69c48274493aafb3f7027641883; retrieved 2026-09-24T02:18:16.690Z.