NYC89LA212 · Balloon Works FIREFLY
Balloon Works FIREFLY · Accident: in flight collision with object during landing
From North Wales, PA to an unrecorded destination
Event
- NTSB case
- NYC89LA212
- 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
- Aircraft type
- Balloon Works FIREFLY
- 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
- N7406F
- Operator
- John W. Edling · private individual
- Onboard fatalities
- Unknown
- Route
- From North Wales, PATo 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
- 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
- Pilot in command › Clearance, not maintained
- Pilot in command › Planning/decision, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE BALLOON DEPARTED ON A PLEASURE FLT WITH 4 PASSENGERS ABOARD. THE WINDS WERE REPORTED FROM THE SOUTHEAST AT 5 KTS, VISIBILITY WAS UNLIMITED & THE TEMP WAS 72 DEGS. ABOUT 30 MIN AFTER TAKEOFF, THE PLT DISCOVERED THE #2 PROPANE TANK WAS EMPTY. HE IMMEDIATELY SWITCHED TO THE #1 RESERVE TANK. WHILE ATTEMPTING TO LAND IN AN APPROPRIATE LANDING SPOT, THE BURNER PRESSURE DROPPED & THE PLT WAS UNABLE TO AVOID POWERLINES. SUBSEQUENTLY, THE GONDOLA CONTACTED & CAME TO REST ON THE POWERLINES. THE PLT WAS ABLE TO DISLODGE THE GONDOLA, BUT IT FELL TO THE GROUND & ONE PASSENGER WAS SERIOUSLY INJURED; THE OTHER PASSENGERS RECEIVED MINOR INJURIES.
Probable cause
IMPROPER IN-FLIGHT PLANNING/DECISION BY THE PILOT WHICH RESULTED IN HIS FAILURE TO MAINTAIN CLEARANCE OBSTRUCTIONS. A RELATED FACTOR WAS: THE LOW LEVEL OF PROPANE (FUEL), WHICH RESULTED IN LOW BURNER PRESSURE.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC89LA212
- Event ID
- 20001213X29250
- Case number
- NYC89LA212
- 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: b0fcaf8acd7a9e72645679a4a79a9fa79e541be49682f18021f4e9e2a1aaca9e; retrieved 2026-09-21T15:50:15.623Z.