FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN15LA300 · Balony Kubicek Spol BB60Z

2 Jul 2015 · Fort Carson, CO, United States

High but Dry Balloons Balony Kubicek Spol BB60Z · Accident: hard landing

From Colorado Springs, CO to Colorado Springs, CO

Report a problem

Event

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

Balony Kubicek Spol BB60Z

Aircraft type
Balony Kubicek BB60
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
N210GB
Onboard fatalities
Unknown
Route
From Colorado Springs, COTo Colorado Springs, CO
Aircraft age
About 5 years (built 2010)
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
None

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Task performance

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

NTSB narrative

The commercial pilot checked the weather before the air tour balloon flight. The Colorado Springs Municipal Airport (COS) automated weather system reported that the surface wind was 070 degrees at 7 mph. A National Weather Service meteorologist informed the pilot that a front north of Denver was expected to pass through Colorado Springs about 6 hours after the flight was going to take off. The pilot also attempted to contact Lockheed Martin Flight Service (LMFS) twice without success; LMFS reported that, on the morning of the accident, it experienced an abnormally high call volume, which resulted in long wait/hold times. About 15 minutes before taking off, the pilot released a pilot balloon (pibal) from the launch site to check the wind aloft. At first, the pibal drifted toward the west slowly. However, when it reached about 1,000 ft above ground level (agl), it appeared to drift back toward the launch site. The pilot reported that he also noticed a slight breeze blowing in a tall treetop located on a rise south of the launch site.

Before departure, the pilot rechecked the wind at COS, which was still 070 degrees at 7 mph. The balloon lifted off in calm wind conditions. However, as the flight continued, the balloon's groundspeed began to increase rapidly. About 22 minutes into the flight, a crew chief for another balloon company called the pilot and told him that COS was now reporting wind at 18 mph gusting to 26 mph. The pilot reported that he then began looking for a place to land and that, as he was doing this, the wind continued to increase to about 43 mph. The pilot located a large open field and set up for a high-wind landing, which involved descending to about 20 ft agl, at which point he intended to pull out the [parachute] top of the balloon envelope and make a steep, rapid descent to the ground. However, at 100 ft agl, the balloon encountered a drop in wind velocity from about 43 to 26 mph. The pilot had allowed the envelope to cool for the approach, which, along with the drop in wind velocity, caused the balloon's descent rate to increase rapidly. The pilot subsequently fully engaged the burners, but he was unable to arrest the descent, and the balloon impacted the ground hard. One passenger was ejected from the basket but was not injured. Two of the passengers remained in the basket but sustained serious injuries. Because the pilot had fully engaged the burners before it landed, the balloon lifted off again and ascended rapidly. The pilot regained control of the balloon, flew it to an open field, and subsequently conducted a controlled high-wind landing.

Probable cause

The pilot’s improper burner control, which allowed the balloon’s envelope to cool, and the balloon’s subsequent encounter with a drop in wind velocity during a highwind landing approach, both of which resulted in the balloon’s descent rate increasing too rapidly for the pilot to arrest it and led to a hard landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN15LA300
Event ID
20150708X21807
Case number
CEN15LA300
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, damage. 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: 40e005b1b9665b9bb9dc529d8d3ebc7c78b6757331b530d8f0ed11623fdfd2a1; retrieved 2026-09-16T02:30:23.277Z.