CEN16LA183 · Cameron Balloons US Z-150
Cameron Balloons US Z-150 · Accident: hard landing
From Edmond, OK to Edmond, OK
Event
- NTSB case
- CEN16LA183
- 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
Cameron Balloons US Z-150
- Aircraft type
- Cameron Z-150
- 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
- N6952D
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Edmond, OKTo Edmond, OK
- Aircraft age
- About 4 years (built 2012)
- 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 · flare/touchdown
- 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
- Substantial
Cause areas
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.
NTSB narrative
During the landing approach at the conclusion of the sightseeing flight, the commercial pilot of the balloon began a "quick" descent from an altitude of about 500 ft in order to land in a field that was about ¼ mile away. The pilot then activated the burners in order to slow the balloon's descent rate. About 50 ft above the ground, the pilot turned off the burners and pulled the quick deflation port at the top of the envelope. The basket impacted the ground, and the pilot and one passenger were ejected from the basket. The pilot continued to hold onto the quick deflation port line, and was dragged alongside the basket as the balloon subsequently became airborne. The balloon continued across the field until it contacted trees and came to rest. The pilot reported there were no mechanical malfunctions or anomalies with the balloon that would have precluded normal operation.
Probable cause
The pilot’s failure to control the balloon’s descent rate during the landing approach, which resulted in a hard landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN16LA183
- Event ID
- 20160516X15413
- Case number
- CEN16LA183
- 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: 59f0822f2044dff5101e071b8a895c1a29d509648e3e057bf849cdfc5a818783; retrieved 2026-09-16T03:23:24.379Z.