FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN13LA347 · Aerostar International Inc RX 8

8 Jun 2013 · Arvada, CO, United States

Aerostar International Inc RX 8 · Accident: collision during takeoff/landing

From Gunbarrel, CO to Arvada, CO

Report a problem

Event

NTSB case
CEN13LA347
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 International Inc RX 8

Aircraft type
Aerostar RX-8
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
N7059U
Onboard fatalities
Unknown
Route
From Gunbarrel, COTo Arvada, CO
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
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
Collision during takeoff/landing
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

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

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

NTSB narrative

The pilot reported that, before the flight, he checked the weather forecast and received weather information from several sources. He and the other balloon pilots flying that day compared the weather information and agreed that the forecast weather provided suitable conditions for a safe flight that morning. However, because the wind conditions on the ground were light and erratic, they delayed taking off. The pilots continued monitoring the current and forecast weather using their wireless devices. The wind eventually calmed, and, after putting up additional pibals, they determined that the wind at altitude would take the balloons to the east-southeast and then south at 3 to 5 miles per hour. At takeoff, the wind was calm. The balloon traveled to the east-southeast and then, about 1,000 to 1,200 feet above ground level, the balloon turned toward the south. The first 30 to 40 minutes of flight were smooth, and the balloon traveled slowly to the southeast. About 40 minutes into the flight, at an altitude of 6,200 feet mean sea level, a wind gust buffeted the balloon. The pilot reported the condition to the other pilots who were flying in the area, and they responded that they were experiencing similar conditions at various altitudes. As he looked at the other balloons, the pilot noticed significant distortions in the envelopes indicative of high winds. The pilot briefed his passengers on a high-wind landing and landed in a cleared construction area. As the balloon touched down, he pulled the deflation lines, and the balloon deflated in seconds; however, the envelope concaved, and the balloon was dragged for several hundred feet until it came to rest on the side of a highway.

A review of meteorological data available at the time of the preflight briefing indicated, in part, that wind from the west existed at 10 knots or less before takeoff. The National Weather Service (NWS) terminal area forecast expected easterly wind shifting to the northwest at 13 knots during the anticipated flight with wind from the north gusting to 23 knots after 1000 mountain daylight time. The NWS area forecast did not expect any high winds across Colorado. The NWS Aviation Forecast Center had no advisories current for low-level turbulence or high winds over Colorado surrounding the anticipated flight. However, shortly after takeoff, a sudden increase in windspeed occurred across the region with wind gusts from 20 to 38 knots. The NWS misjudged the timing and underestimated the magnitude of the frontal boundary moving across the region. It is likely that, if the pilot had known about the gusting wind at the time of takeoff, he may not have chosen to fly that day.

Probable cause

The balloon's encounter with unforecast strong gusting wind, which resulted in a high-wind landing. Contributing to the accident was the National Weather Service's misjudgment of the timing and underestimation of the magnitude of the frontal boundary moving across the region.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN13LA347
Event ID
20130613X20505
Case number
CEN13LA347
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: 5704ddc7c8baa72e3a585f76c5ae396239ec3cd4b0605e610f23ce7f57204e93; retrieved 2026-09-15T21:51:28.287Z.