DEN90FA176 · Cameron O-84
Cameron O-84 · Accident: in flight collision with object during landing
From Taos, NM to an unrecorded destination
Event
- NTSB case
- DEN90FA176
- 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
Cameron O-84
- Aircraft type
- Cameron O-84
- 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
- N74000
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Taos, NMTo 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
- Landing · aborted
- 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
- Minor
Cause areas
- Clearance › Not possible
- Pilot in command › Go-around, attempted
- Pilot in command › In-flight planning/decision, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE BALLOON WAS APPROACHING AN OPEN FIELD FOR LANDING AFTER AN UNEVENTFUL SIGHTSEEING FLIGHT. THE PILOT SAID THE WINDS WERE LIGHT AND THE BALLOON'S RATE OF DESCENT WAS SUFFICIENT TO CLEAR A POWERLINE, WHICH IT DID. APPROXIMATELY 5-10 FEET AGL, THE PILOT NOTICED THE WIND HAD SHIFTED AND WAS MOVING THE BALLOON TOWARDS THE POWERLINE, WHICH AT THAT TIME WAS ABOUT 100 FEET AWAY. THE PILOT FIRED BOTH PROPANE BURNERS IN AN ATTEMPT TO GO-AROUND. THE BALLOON BEGAN CLIMBING BUT CONTACTED THE POWERLINE. ONE PASSENGER WAS ELECTROCUTED AND FELL OUT OF THE BASKET. THE PILOT LANDED THE BALLOON IN AN ADJOINING FIELD.
Probable cause
THE PILOT'S IMPROPER DECISION TO ATTEMPT A GO-AROUND. A FACTOR WAS THE UNFAVORABLE WIND ENCOUNTERED LATE IN THE ATTEMPTED LANDING.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN90FA176
- Event ID
- 20001212X23978
- Case number
- DEN90FA176
- 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: 635ab7af44de0134a343dfe92e1e46053dfd2e47cdf4895e26f019774f01b0fe; retrieved 2026-09-21T02:19:29.232Z.