DEN87FA069 · Raven S-77A
Raven S-77A · Accident: in flight collision with object en route
From Park City, UT to an unrecorded destination
Event
- NTSB case
- DEN87FA069
- 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
- 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
Raven S-77A
- Aircraft type
- Raven S-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
- N40968
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Park City, UTTo 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 · descent
- 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 object
- 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, transmission
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Clearance, not maintained
- Pilot in command › Emergency procedure, not followed
- Pilot in command › In-flight planning/decision, improper
- Pilot in command › Visual lookout, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
WHILE ON A COMMERCIAL PAX SIGHTSEEING FLT, THE PLT ALLOWED A NON-RATED STUDENT PLT TO FLY THE BALLOON UNTIL IT NEARLY COLLIDED WITH BUILDINGS. THE PLT TOOK OVER THE CONTROLS AND APPLIED MAXIMUM BURNER HEATING TO AVOID IMPACT WITH THE BUILDINGS, WHICH RESULTED IN RAPID ASCENT TO APPROXIMATELY 3,000 FEET AGL. WINDS AT THAT ALTITUDE BLEW THE BALLOON OUT OF THE SMALL OPEN VALLEY WHERE THE FLTS WERE NORMALLY CONDUCTED. IT CROSSED A RIDGELINE AND WAS FLYING OVER MOUNTAINOUS/HILLY TERRAIN WHERE THE PLT INITIATED A DESCENT FOR LANDING. THE BALLOON IMPACTED TRANSMISSION POWER LINES AT APPROXIMATELY 50 FEET ABOVE THE GROUND. THE GONDOLA WAS SEVERED FROM THE BALLOON BY ELECTRICAL ARCING AND FELL TO THE GROUND. THE NATURAL GAS FUEL TANKS EXPLODED AND BURNED, DESTROYING THE GONDOLA.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record DEN87FA069
- Event ID
- 20001213X30419
- Case number
- DEN87FA069
- 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. 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: ebc94385197d075a86ed244103e9d48434f2baa732e5c06d8895fe5a40a31868; retrieved 2026-09-21T04:11:46.490Z.