FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN14LA007 · Cameron Balloons US V 77

9 Oct 2013 · Rio Rancho, NM, United States

Cameron Balloons US V 77 · Accident: controlled flight into terrain/object (CFIT) on approach

From Albuquerque, NM to Rio Rancho, NM

Report a problem

Event

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

Cameron Balloons US V 77

Aircraft type
Cameron V-77
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
N9528A
Onboard fatalities
Unknown
Route
From Albuquerque, NMTo Rio Rancho, NM
Aircraft age
About 23 years (built 1990)
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
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
Controlled flight into terrain/object (CFIT)
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
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

  • Environmental issues › Physical environment
  • Personnel issues › Action/decision

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

NTSB narrative

The pilot and passenger departed on a balloon flight and had been airborne for a little over an hour before making three attempts to land. The wind was too strong on the first attempt; on the next attempt, they found themselves over a residential subdivision that prevented them from landing. The pilot then saw an open area on the other side of a street with power lines running along it. His intent was to get over the power lines and then drop the balloon down to the ground. They were over the road and a couple of feet over the power lines when the balloon dropped and struck the power lines. The pilot engaged the burner and the basket slid off the first two wires, but when the basket touched the third wire there was an electrical short and then an explosion. The pilot reported the explosion was the last thing he remembered until he found himself on the ground with the envelope going down.

Probable cause

The pilot's failure to maintain adequate clearance from power lines on approach to land, resulting in a collision with the wires, a spark, and a subsequent explosion and on-board fire.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN14LA007
Event ID
20131010X15655
Case number
CEN14LA007
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. 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: 2aec4f27e47b0ee0564f25a0bcc18cc745abec5fa684ad9dc5f447a238802e41; retrieved 2026-09-15T22:57:01.767Z.