FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX99FA273 · Balloon Works FIREFLY 11

19 Aug 1999 · Cave Creek, AZ, United States

Hot Air Expeditions Balloon Works FIREFLY 11 · Accident: in flight encounter with weather en route

Report a problem

Event

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

Balloon Works FIREFLY 11

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
N7021U
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
En route · descent
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 encounter with weather
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Minor

Cause areas

  • Aircraft performance, climb capability › Exceeded
  • Balloon equipment, envelope › Excessive flow/output
  • Descent › Excessive
  • Weather condition › Microburst/dry

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

NTSB narrative

While attempting a high wind landing, the balloon hit hard and one passenger sustained serious injuries. The pilot checked weather prior to departure, and said that at 0610, the weather was mostly cloudy with surface winds from the south at 3 to 5 mph. About 0635, the nearby Deer Valley airport ATCT told the pilot that surface winds were 12 knots from 220 degrees. In addition, another company pilot told him by radio that surface winds in his location were now 25 mph. The pilot's ground crew also confirmed that surface winds had increased substantially. The pilot said that he was 3,000 feet msl when the change in wind velocity was reported, and he selected an alternate landing site and briefed his passengers on high wind landing procedures. The approach was initiated at a descent rate of 700 fpm. During this time he told the two standing passengers to sit down because they would be experiencing a very rough landing. After descending through 500 feet agl at 700 fpm, the balloon's vertical sink rate suddenly increased substantially. He said this encounter had caused distortion in the envelope that resulted in the envelope losing hot air (lift), and increasing his rate of descent. His attempt to slow the descent in the time remaining was unsuccessful and the balloon landed short of the intended site, rebounded into the air, and then skidded about 100 yards before coming to a stop with the carriage lying on its side. Another balloon pilot, who saw the landing, said that the balloon appeared to have encountered a sudden microburst that resulted in an inadvertent hard landing. Other witnesses described the final descent as rapid, and noted that the envelope was distorted (flattened) downward as if the balloon was being pushed down. According to the FAA approved performance data sheet, terminal velocity (Vt) of the balloon under maximum gross weight conditions is 1,200 fpm with a recovery time to equilibrium 90 seconds, and altitude lost during recovery (from application of burner to equilibrium) to be 1,000 feet. The POH states that should weather conditions deteriorate while in flight, the pilot should land immediately, and "to risk damage if necessary to land while the flight is still under control." The manufacturer reported that the maximum demonstrated wind speed at landing during certification testing was 7 knots.

Probable cause

An unforecast encounter with a low level microburst that resulted in a distortion of the balloon envelope, an excessive outflow of hot air (loss of lift), creating an excessive rate of descent that was beyond the performance capability of the balloon to recover in the altitude available. The failure of a passenger to follow the emergency procedures directives of the pilot was a factor in this accident.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX99FA273
Event ID
20001212X19550
Case number
LAX99FA273
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: e795f7bcba9441a5cd585d999e07a822ffd611ad66f9949a74d3f60143b9021b; retrieved 2026-09-21T10:53:48.218Z.