FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

BFO94LA078 · Cameron ET-90

26 Apr 1994 · Louisville, KY, United States

Brown Foreman Beverage Cameron ET-90 · Accident: in flight collision with object on approach

Report a problem

Event

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

Cameron ET-90

Aircraft type
Cameron ET-90
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
N898ET
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
Approach
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
In flight collision with object
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, static
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 › Clearance, not maintained

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

NTSB narrative

THE PILOT STATED THAT HE RECEIVED A WEATHER BRIEFING AND SENT UP THREE WEATHER BALLOONS PRIOR TO LAUNCHING ON THE FLIGHT. IMMEDIATELY AFTER INITIATING FLIGHT, THE PILOT NOTICED DARKENING SKIES AND DECIDED TO LAND THE BALLOON SHORT OF THE DESTINATION. THE PILOT CHOSE A LANDING AREA IN CLOSE PROXIMITY TO POWERLINES AND AN INTERSTATE HIGHWAY. HE STATED THAT HE ESTABLISHED A GLIDE PATH SO THAT HE WOULD CLEAR THE TOPS OF THE POWERLINES BY 20 FEET. THE PILOT FURTHER STATED THAT THE BALLOON ENCOUNTERED A DOWNDRAFT AND STRUCK THE POWERLINES.

Probable cause

THE PILOT-IN-COMMAND'S FAILURE TO MAINTAIN CLEARANCE FROM WIRES DURING THE LANDING APPROACH. A FACTOR RELATED TO THE ACCIDENT IS A DOWNDRAFT THAT EXCEEDED THE BALLOON'S AVAILABLE CLIMB CAPABILITY.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record BFO94LA078
Event ID
20001206X01058
Case number
BFO94LA078
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: 027b7e4426a2c8fb8d9f75dcc4973d016d0fbc8383246f4b8a3ae38b961957a8; retrieved 2026-09-21T22:39:36.536Z.