Arbc INC DBA Lindstrand 260A accident near Custer, South Dakota, July 12, 2023
On July 12, 2023 at about 12:48 pm local time, a 2022 Arbc INC DBA Lindstrand 260A (balloon), registered N605KD, was involved in an accident during landing (flare/touchdown) near Custer, South Dakota. It was an aerial observation flight under general aviation rules (Part 91). 1 person was seriously injured; 10 others were unhurt. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot’s weather encounter that resulted in a high speed landing, the balloon tipping over, and serious injury to a passenger.
Source: NTSB aviation accident database, copy made October 12, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- July 12, 2023 · about 12:48 pm local time · cases in 2023
- Place
- Custer, South Dakota · map
- Type
- Accident
- Injuries
- 1 person was seriously injured; 10 others were unhurt.
- Weather
- visual conditions (good weather)
- Aircraft
- Arbc INC DBA Lindstrand 260A, built 2022 · all 260As on the register
- Registration
- N605KD · registry record · serial 5770
- Damage
- Not recorded
- Flight
- Aerial observation flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot of the sightseeing flight stated that after departure, the balloon’s speed increased, and its direction of travel became different from preflight wind observations. During the flight, the pilot established radio contact with the pilot of another company balloon, and they decided to land at a park. The other company balloon, which was ahead of the accident balloon, landed in the park without incident. When the accident pilot attempted a similar landing, the balloon encountered wind shear, and he continued the flight and flew about 1.5 miles. The pilot found a long field sheltered by trees and terrain, in which to attempt a landing. The pilot briefed the passengers to hold on tight and to crouch down in the balloon’s basket for the landing. At 100 ft above ground level (agl), the balloon encountered wind shear and slowed to about 5 kts. At 50 ft agl, the approach was “normal,” but the balloon’s speed increased “very rapidly.” The pilot stated that he was committed to the landing due to the amount of heat he had vented from the balloon, which would not allow for a climb. The balloon touched down “fairly smoothly,” but its speed increased. The pilot pulled the rapid deflation line, but the balloon lifted off, so he reseated the deflation system to reduce a descent rate that ensued from about 20 ft agl. The pilot then pulled the rapid deflation line again when the balloon was about to touch down. During touchdown, the balloon tipped over onto its side and came to a stop after traveling about 120 ft. The balloon did not sustain damage. A passenger received serious injuries. The pilot stated there was no mechanical malfunction/failure of the balloon.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Other weather encounter during landing (flare/touchdown)
- Hard landing during landing (flare/touchdown) defining event
The NTSB's findings
- Environmental issues › Conditions/weather/phenomena › Wind › High wind › Not specified
- Aircraft › Aircraft oper/perf/capability › Performance/control parameters › (general) › Not specified
Pilot
- Certificate: commercial pilot
- Ratings: rotorcraft: balloon
- Flight time: 2,196 hours in all; 117 in this make and model; 27 in the last 90 days; 19 in the last 30 days; 2,140 as pilot in command; 23 on instruments
- Last flight review: September 29, 2022
- Medical certificate: Class 2 (without waivers/limitations)
- Seat: none
- Injury: no injuries
The aircraft
- Airframe total time: 90.3 hours
- Last inspection: annual inspection, May 1, 2023
- Maximum gross weight: 3,800 lb
- Seats: 13
- Landing gear: fixed
- Operator: Flying Circus Inc
The flight
- Departed from: Custer SD at 11:54 am
- Flight plan: none
Weather at the time
- Light: daylight
- Wind: from 260° at 6 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 55°F (13°C), dew point 45°F (7°C)
- Altimeter: 30.05 inHg
- Observation at 11:53 am from CUT, 9 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 | 9 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.
Other NTSB records under N605KD the same tail number, which may have belonged to a different aircraft at the time
Connections how this case links to the rest of the register
- N605KD on the register today · the tail number may have moved to another aircraft since
- Arbc Inc Dba Lindstrand 260 6 registered today · the model family and its accident history
- Accidents and incidents in South Dakota 467 since 1982 · 67 in the last ten years
- South Dakota 2,273 aircraft registered
- Other NTSB records under N605KD 1 records · the number may have belonged to another aircraft at the time
The whole map of how records connect · these connections as data: /graph/accident/CEN23LA302.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.