FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX05LA135 · Cameron Balloons A-210

13 Apr 2005 · Marana, AZ, United States

Cameron Balloons A-210 · Accident: in flight collision with terrain/water en route

From Marana, CA to an unrecorded destination

Report a problem

Event

NTSB case
LAX05LA135
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
1 · 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 A-210

Aircraft type
Cameron A-210
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
N210EW
Onboard fatalities
Unknown
Route
From Marana, CATo 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 · climb to cruise
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 terrain/water
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

  • Copilot/second pilot › Clearance, not maintained
  • Copilot/second pilot › Proper climb rate, not attained
  • Pilot in command › Remedial action, delayed
  • Pilot in command › Supervision, inadequate

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 boulders located atop a hill, fatally injuring a passenger. After a normal departure on the for-hire sightseeing flight, the pilot transferred control authority to a crewmember who held a private pilot certificate. The purpose of the control transfer was to help the crewmember obtain more practice hours and log pilot-in-command time. He was additionally receiving instruction from the commercial pilot. As the balloon approached rising terrain the crewmember continued the ascent up to about 1,000 feet above ground level (agl). The pilot said the balloon began a gradual descent and the crewmember reacted by manipulating all the burners to produce maximum lift. The balloon's basket impacted a boulder on the peak of the hill and bounced upward. The balloon again collided with another boulder and subsequently became airborne, clearing the peak of the hill. After maneuvering the balloon over power lines, the pilot landed. A passenger reported that the balloon continued to gain altitude continuously as it proceeded toward the mountain. In the cumulative 2 minutes prior to impact, the passenger noted that the balloon did not appear to increase in altitude, and he assumed that the pilot was going to attempt to maneuver around the approaching peak. He stated that during the flight's duration only one burner was operating at a given time, with the exception of just seconds before the impact when the pilot instructed the other crewmember to "turn on both burners." The passenger said that the two burners appeared to be operating. He added that the balloon's altitude never appeared to reach higher than the top of the hill, and the flight path consisted of a continuous accent up the mountain. Safety Board investigators reviewed an atmospheric sounding of the area around the time of the accident. The data did not support any thermals and no clear air turbulence was identified at the accident altitudes. The wind profile indicated calm surface winds, defined as below 10 knots. No defined mountain wave pattern was identified. A post accident examination of the balloon found no anomalies or discrepancies with the envelope, basket, or burners. Regulations restrict private pilots from being pilot-in-command during commercial operations with fare-paying passengers; however, a private pilot can be the pilot-in-command if a commercial pilot is providing instruction.

Probable cause

the failure of the flying pilot to attain a proper climb rate and maintain an adequate clearance from rising terrain. Also causal was the commercial pilot's inadequate supervision of the flight and his delayed remedial action.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX05LA135
Event ID
20050414X00458
Case number
LAX05LA135
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: 17f7b32e2586803f29c8ac574faee0502c2ef32eda806b9791f69528a9b0858a; retrieved 2026-09-20T18:04:44.294Z.