FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL83FA001 · Eagle C-7

3 Oct 1982 · Piedmont, SC, United States

Eagle C-7 · Accident: loss of control in flight on approach

From C · Piedmont, SC to C · Piedmont, SC

Report a problem

Event

NTSB case
ATL83FA001
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
3 · 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

Eagle C-7

Aircraft type
Eagle C-7
Category
Balloon
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
N70014
Operator
Abrams, Lawrence L. · private individual
Onboard fatalities
Unknown
Route
From C · Piedmont, SCTo C · Piedmont, SC
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
Approach · VFR pattern final
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
Loss of control in flight
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Wire, transmission
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Pilot in command › Inadequate transition/upgrade training
  • Pilot in command › Operation with known deficiencies in equipment, performed
  • Pilot in command › Procedures/directives, improper
  • Pilot in command › Weather evaluation, inadequate
  • Weather condition › Gusts
  • Weather condition › Unfavorable wind

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

NTSB narrative

BALLOON WAS INFLATED WITH DIFFICULTY BECAUSE OF GUSTY WINDS.BALLOON DID NOT HAVE A SKIRT. DURING THE FLIGHT WHICH ENDED IN THE ACCIDENT THE BALLOON SEEMED TO HAVE TROUBLE AND DURING THE FINAL MOMENTS IT WAS IN A DESCENT WHICH ENDED WITH THE ENVELOPE AS A STREAMER UNTIL CONTACT WITH WIRES.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record ATL83FA001
Event ID
20020917X04290
Case number
ATL83FA001
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: 0b7a249c896903fda1821357289c1526f6c4040a36f27e72b7596d768e5868dd; retrieved 2026-09-21T07:42:30.267Z.