GAA15LA015 · Ultramagic SA N210
Ultramagic SA N210 · Accident: hard landing
From Phoenix, AZ to Phoenix, AZ
Event
- NTSB case
- GAA15LA015
- 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
Ultramagic SA N210
- Aircraft type
- Ultramagic N210
- 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
- N210UM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Phoenix, AZTo Phoenix, AZ
- Aircraft age
- About 2 years (built 2013)
- 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
- Landing
- 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
- Hard landing
- 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
- Environmental issues › Conditions/weather/phenomena
- Environmental issues › Physical environment
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot reported that, halfway through the flight, he determined that the wind aloft was higher than anticipated and that the original planned landing destination was no longer suitable. While the balloon was between 3,000 and 4,000 ft mean sea level, he started looking for another landing area and noted that the surface wind had increased and changed direction since the launch; the wind aloft about this time was reported to be 26 knots. The pilot stated that, during the descent to land, the balloon was traveling "about 15 mph." During the subsequent landing in an open field, the gondola impacted the ground hard twice, followed by two small hops, and then came to a stop. One of the passengers sustained two broken ankles during the two hard landings.
Probable cause
The pilot's selection of unsuitable terrain for landing after noting a higher-than-anticipated wind speed and the balloon's high descent rate, which resulted in a hard landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA15LA015
- Event ID
- 20150324X32859
- Case number
- GAA15LA015
- 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. 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: aeefc7fcc66e51c641596909a5a8a1efe2e92af4beb449d8eb7dbfca34322a79; retrieved 2026-09-16T02:10:35.052Z.