CEN24LA302 · Arbc Inc DBA Lindstrand 260A
Marketing Services Inc of Pueblo Arbc Inc DBA Lindstrand 260A · Accident: hard landing
From City of Colorado Springs Municipal Airport (COS) to an unrecorded destination
Event
- NTSB case
- CEN24LA302
- 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
- Event fatalities
- Unknown
- 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
Arbc Inc DBA Lindstrand 260A
- Aircraft type
- Lindstrand 260
- 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
- N26464
- Operator
- Marketing Services Inc of Pueblo
- Onboard fatalities
- Unknown
- Route
- From City of Colorado Springs Municipal Airport (COS), Colorado Springs, COTo not recorded
- Aircraft age
- About 10 years (built 2014)
- 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
- 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
- None
Cause areas
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Following an uneventful flight, the pilot descended the balloon at a steep angle into a vacant field. The pilot had briefed the passengers on the proper brace position before the flight and then again just before the landing. The basket touched down firmly, bounced several times and came to rest on its side. Following the landing a passenger experienced pain in his leg. It was later determined the passenger had a broken ankle. The pilot stated that there were no mechanical malfunctions with the balloon that would have precluded normal operations.
Probable cause
The pilot’s failure to maintain the proper descent rate during the balloon’s approach to landing, which resulted in a hard landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN24LA302
- Event ID
- 20240805194847
- Case number
- CEN24LA302
- 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, 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: 81b6d1aaccb0412126243ff13b24cb861e6c6ff068562868bd2cab443d6895f7; retrieved 2026-09-16T19:08:02.262Z.