FTW98LA231 · Balloon Works FIREFLY 7-B FIREFLY 7-
Balloon Works FIREFLY 7-B FIREFLY 7- · Accident: in flight encounter with weather during landing
From Twin Lakes, CO (no airport) to CO (no airport)
Event
- NTSB case
- FTW98LA231
- 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 7-B FIREFLY 7-
- Aircraft type
- Balloon Works FIREFLY 7
- 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
- N1527M
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Twin Lakes, CO (no airport)To CO (no airport)
- 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 encounter with weather
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- None
Cause areas
- Pilot in command › Procedures/directives, not followed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
During the landing approach, the winds were from the south at 5 to 7 knots. At 30 to 40 feet above the ground, the pilot encountered wind shear out of the east at 30 to 35 knots, and the intended landing was aborted. The pilot climbed to 150 agl and set up for a high wind landing. Upon touchdown, the pilot's foot was caught between the wicker siding and the solid floor of the basket, and the pilot's ankle was broken. According to the pilot, the accident would not have occurred had he not improperly placed his foot between the wicket basket and the floor plate of the balloon at the time the balloon impacted the ground.
Probable cause
The pilot's failure to properly position his foot for a high wind landing. Factors were high winds and windshear.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW98LA231
- Event ID
- 20001211X10081
- Case number
- FTW98LA231
- 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, damage. 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: 602ab2427bee45e2468a1c33f55fcc9c9acb97c88a6af1d55ea53b636df1dc0a; retrieved 2026-09-21T11:32:27.118Z.