CHI83LA310 · Balloon Works FIREFLY 8-24 FIREFLY 8-
Balloon Works FIREFLY 8-24 FIREFLY 8- · Accident: airframe, component or system failure en route
From Excelsior, MN to an unrecorded destination
Event
- NTSB case
- CHI83LA310
- 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
- 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
Balloon Works FIREFLY 8-24 FIREFLY 8-
- Aircraft type
- Balloon Works FIREFLY 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
- N1509W
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Excelsior, MNTo 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 · cruise
- 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
- Airframe, component or system failure
- 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
- Pilot in command › Fuel system, inadvertent deactivation
Approximate · Estimated position: the centre of Hamel, MN, the place the record names. Not the accident site.
NTSB narrative
DURING FLT, THE PLT USED FUEL FROM 2 OF 4 PROPANE TANKS, THEN SWITCHED TO THE 2ND 2 TANKS & STARTED A DESCENT. AT APRX 300 FT AGL, HE TRIED TO START THE BURNER, BUT COULD NOT GET A LIGHT BECAUSE THE PILOT LIGHT WAS OUT. HE ATTEMPTED TO MANUALLY RELIGHT THE BURNER WITH A FLINT SPARKER, BUT THE BURNER WOULD NOT RELIGHT. SUBSEQUENTLY, THE BALLOON STRUCK A METAL FENCE, BOUNCED & HIT A TRACTOR. FIVE OF THE PASSENGERS FELL OUT. THE PLT & ONE OTHER PASSENGER WERE CARRIED ANOTHER 200 YARDS INTO A SWAMPY AREA. AN EXAM OF THE FUEL SYS SHOWED THAT THE PILOT LIGHT VALVE WAS A TOGGLE TYPE SWITCH NEAR THE 'FIRE 2' VALVE. THE PLT REPORTED THAT HE COULD HAVE INADVERTENTLY STRUCK & SHUT OFF THE PILOT LIGHT VALVE AS HE ROTATED THE 'FIRE 2' VALVE. WHEN CHECKED, THE PILOT LIGHT & BURNER OPERATED NORMALLY. THE 'FIRE 2' WOULD ONLY LIGHT WITH THE FLINT SPARKER WHEN THE VALVE WAS ONLY SLIGHTLY OPENED.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record CHI83LA310
- Event ID
- 20001214X43672
- Case number
- CHI83LA310
- 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: 61d03c346c32e710aa673cad58d8efc01f264cfcce3efe7c5cdc89cd1dc18d42; retrieved 2026-09-21T17:52:43.642Z.