FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW84LA164 · Eagle Balloons EAGLE C-7

10 Mar 1984 · Houston, TX, United States

Eagle Balloons EAGLE C-7 · Accident: on ground/water collision with object during landing

Report a problem

Event

NTSB case
FTW84LA164
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
Instrument Meteorological Cond

Eagle Balloons 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
N6081L
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo not recorded
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
On ground/water collision with object
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

  • Pilot in command › Aircraft handling, inadequate

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

NTSB narrative

THE PLT STATED THAT THE WX AT THE ACCIDENT SITE WAS SCATTERED CLOUDS BETWEEN 150-650 FT AGL WITH A DEFINITE CEILING AT 650 FT (BROKEN). VISIBILITY WAS 1 MI WITH RAPIDLY FORMING FOG LAYER. THE PLT DESCENDED WITH THE INTENTION OF LANDING AS SOON AS POSSIBLE. HE SAW THE POWERLINES & IMMEDIATELY PULLED THE PRESSURE TOP & CONTACTED THE GROUND ABOUT 150 FT FROM THE POWERLINES. HOWEVER, THE BALLOON DRAGGED ABOUT 80 FT & THE PYROMETER WIRE ON TOP OF THE ENVELOPE CONTACTED THE LOWEST POWERLINE. A PATH TO GROUND WAS MADE THROUGH THE PYROMETER CABLE/LINES, UPRIGHT LINES, FUEL TANK & SUPPORT CABLES. THE INSTANTANEOUS CHARGE (TO GROUND) SPLIT THE ENVELOPE DOWN THE PYROMETER WIRE, BLEW CONVERTING PINS OUT OF THEBURNER & UPRIGHT SUPPORTS, & SENT THE HIGH VOLTAGE/CURRENT FLOW INTO THE BASKET.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record FTW84LA164
Event ID
20001214X39033
Case number
FTW84LA164
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: c27559bea31289d75794b063e27df7ededcf788d8050da58b04d4fd41f61b8ff; retrieved 2026-09-22T02:21:20.243Z.