ERA20LA094 · Airborne America AX9-140 2
Airborne America AX9-140 2 · Accident: low altitude operation/event while maneuvering
From Homestead, FL (no airport) to Homestead, FL (no airport)
Narrative check · The NTSB narrative appears to contradict this record's injuries. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- ERA20LA094
- 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
- Unknown
- 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
Airborne America AX9-140 2
- Aircraft type
- Airborne America AX9
- 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
- N970TC
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Homestead, FL (no airport)To Homestead, FL (no airport)
- Aircraft age
- About 31 years (built 1989)
- 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
- Maneuvering · low-altitude flying
- Defining eventThe 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
- Low altitude operation/event
- 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 › Aircraft oper/perf/capability
- Organizational issues › Support/oversight/monitoring
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The commercial pilot who owned the hot air balloon tour company departed on a revenue tour flight with eight passengers onboard. The pilot reported that his preflight review of weather conditions indicated light wind at the surface and aloft. After about 50 minutes of flight, the pilot was approaching a field for landing when, while crossing overhead a set of power lines, the balloon encountered a “downdraft” and entered a “rapid descent.” The basket contacted the power lines, then slid to the ground. The pilot did not have current flight review, and the balloon’s registration had expired. Several passengers provided statements in which they recounted that, throughout the flight, the balloon was flying low enough that they could easily communicate with people on the ground, and that the basket contacted trees twice and a power pole once during the flight. After contacting the trees, the pilot laughed and stated that he was “cleaning the bottom of the basket.” Examination of the balloon’s flightpath indicated that after departure, the balloon tracked downwind at low altitude (below 500 feet) near multiple obstacles, structures, and powerlines for most of the flight, and although the pilot reported that a downdraft occurred, the passengers did not report it, and there was no indication of any thunderstorms, convective activity, or high winds around the time of the accident. The balloon impacted the power lines with the lower part of the envelope and flying wires that held the basket to the canopy. The balloon came to rest with the envelope draped over the power lines and the basket in a small group of trees directly below the lines, 10 to 12 feet above the ground. Electrical arcing occurred and showers of sparks flew on and around the passengers. The accident resulted in serious injury to two of the passengers, and minor injury to four of the passengers. The events of the accident flight displayed a pattern of poor decision-making by the pilot both before and during the flight; including his decision to operate the balloon without a valid registration, his decision to operate the flight without a valid flight review, and his decision to fly the balloon at very low altitudes in proximity to obstructions, structures, and powerlines, which increased the potential of collision. The Federal Aviation Administration had conducted no surveillance of the operator/pilot before the accident. Given the circumstances of this accident, it is likely that with a more robust system of oversight and surveillance of balloon operators, the Federal Aviation Administration could have identified the accident pilot/operator as a potential safety risk and taken steps to mitigate this risk.
Probable cause
The pilot's decision to operate the balloon at low altitude near obstructions, structures, and powerlines, which resulted in the balloon contacting powerlines. Contributing to the accident was the Federal Aviation Administration's inadequate oversight of balloon tour operators.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA20LA094
- Event ID
- 20200119X92859
- Case number
- ERA20LA094
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, coordinates, cause areas. 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: 703f888618290cf49272fb24baca2a51637e425217db982ec8e0b880aaf4954e; retrieved 2026-09-16T10:57:51.727Z.