LAX03LA095 · Aerostar RX-7
Aerostar RX-7 · Accident: in flight collision with object on approach
From Reno, NV to an unrecorded destination
Event
- NTSB case
- LAX03LA095
- 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
Aerostar RX-7
- Aircraft type
- Aerostar RX-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
- N6413N
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Reno, NVTo 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, transmission
- 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 › Evasive maneuver, not successful
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The balloon collided with power lines while descending toward a landing spot. The pilot was crossing a north-south ridgeline while approaching a landing spot in a meadow. The balloon flew over the descending slope and cleared a set of power lines that ran parallel to the ridgeline. A sudden wind shift occurred, blowing the balloon back towards the power lines. The pilot turned on the burner in an attempt to clear the power lines again, however, sufficient lift was not achieved. Realizing that a collision was inevitable, the burner and tanks were shut off and instruments disconnected. After the initial impact the balloon continued rising, and the pilot pulled the 'rip-cord' attached to the deflation port. A rapid decent followed, and the balloon came to rest directly under the power lines.
Probable cause
A sudden wind shift that forced the balloon to drift towards an obstruction, and the pilot's inability to perform an evasive maneuver in sufficient time to prevent a collision.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX03LA095
- Event ID
- 20030225X00260
- Case number
- LAX03LA095
- 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, coordinates. 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: e66e11330d03cf9a4b9a1e2fd07af281cc84fa1cea7ff2a957aeb18662312220; retrieved 2026-09-22T09:34:55.236Z.