FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX99FA177 · Aerostar RALLY RX-8

9 May 1999 · Morgan Hill, CA, United States

Balloons By the Sea Aerostar RALLY RX-8 · Accident: in flight collision with object during initial climb

Report a problem

Event

NTSB case
LAX99FA177
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
2 · 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

Aerostar RALLY RX-8

Aircraft type
Aerostar RALLY RX-8
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
N70290
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
Initial climb
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, 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

  • Aircraft performance, climb capability › Restricted
  • Fuel system, line › Not connected
  • Fuel system, tank › Ruptured
  • Fuel system, tank › Unapproved part
  • Pilot in command › Aborted takeoff, not performed
  • Pilot in command › Aircraft preflight, inadequate
  • Pilot in command › All available runway, not used
  • Pilot in command › Maintenance, installation, improper
  • Pilot in command › Procedures/directives, not followed

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

NTSB narrative

In the takeoff initial climb, the balloon contacted power lines, caught fire, and crashed into a field. The pilot setup the balloon for takeoff from a 798-foot-long open field, 298 feet upwind from 21,000-volt power lines. The FAA approved flight manual specifies that a horizontal distance of 100 feet for each 1-knot of wind speed be allowed between the takeoff point and any obstacle in the takeoff path. During the envelope inflation process, a 7- to 10-mph surface wind developed, which started dragging the basket toward the lines. The pilot elected to continue with the planned flight. He and the two fare-paying passengers took off and drifted into the power lines, which shorted and arced. An unapproved aluminum fuel tank in the basket ruptured and ignited the basket, envelope, and occupants. The pilot jumped from the basket and sustained serious injuries. The passengers remained in the basket and succumbed to thermal injuries. The balloon had been modified by the addition of an uncertified aluminum fuel tank to the two existing factory tanks that were composed of steel. During postaccident examination of the wreckage, a fuel line to one of the two burners was found not connected; with one burner inoperative, the balloon's climb capability was significantly reduced. The envelope's emergency deflation panel was found in the closed position and subsequent testing found it functional. According to the flight manual, the pilot's preflight actions should have included providing safety helmets to the passengers, ascertaining the winds aloft by launching a pibal, and ensuring that both burners were connected to fuel tanks and operational; none of the actions were completed. In addition, the pilot did not vent activate the envelope's emergency deflation panel to land when the collision with the power lines was eminent.

Probable cause

The pilot's selection of an inadequate takeoff site that did not allow sufficient horizontal clearance from obstacles in the takeoff path, and, his failure to ensure that all burners were connected to fuel sources, which reduced the available climb capability of the balloon. Also causal was the pilot's failure to activate the emergency vent panel and land prior to contact with the power lines, and, his use of an unapproved aluminum fuel tank, which ruptured during the power line contact and ignited a fire. A factor in the accident was the pilot's failure before takeoff to use pibals to quantify the wind speed.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX99FA177
Event ID
20001212X18796
Case number
LAX99FA177
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: cbd46eea5bf6124c369e577b81605ca2f47a8aef9c524907147fbe712fa2e22e; retrieved 2026-09-20T22:07:29.973Z.