20230712006639A

Accident · No damage

FAA accident report · Arbc Inc DBA Lindstrand 260A · Custer, SD · July 12, 2023

Date
July 12, 2023 · 06:45 local
Place
Custer, SD
Airport
Custer County Airport
Phase of flight
Landing: Touchdown
Operating rules
General operating rules (Part 91)
Operator
2PYR
Damage
No damage
Aircraft
N605KD
NTSB investigation
NTSBCEN23LA302
Reported as
Arbc Inc DBA Lindstrand 260A
Reported engine
NONE NONE
People aboard
13
Fatal injuries
0
Other injuries
1
Pilot’s certificate
Commercial pilot
Pilot’s flight hours
2,200 total

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry by N-number and event date, checked against the reported make and model; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

On July 12, 2023, at 6:45 am a hot air balloon privacy data omitted was involved in an accident during landing while on a sight-seeing flight. Visual flight rules (VFR) prevailed and no IFR flight plan was filed. The hot air balloon was not damaged. One of the twelve passengers was injured during landing. The pilot holds a commercial certificate. The flight originated 4 miles west of Custer, SD, just south of hwy 16 near "privacy data omitted", on July 12, 2023, at 05:54AM.

As the FAA filed it

ON JULY 12, 2023, AT 6:45 AM A HOT AIR BALLOON ^PRIVACY DATA OMITTED^ WAS INVOLVED IN AN ACCIDENT DURING LANDING WHILE ON A SIGHT-SEEING FLIGHT. VISUAL FLIGHT RULES (VFR) PREVAILED AND NO IFR FLIGHT PLAN WAS FILED. THE HOT AIR BALLOON WAS NOT DAMAGED. ONE OF THE TWELVE PASSENGERS WAS INJURED DURING LANDING. THE PILOT HOLDS A COMMERCIAL CERTIFICATE. THE FLIGHT ORIGINATED 4 MILES WEST OF CUSTER, SD, JUST SOUTH OF HWY 16 NEAR "^PRIVACY DATA OMITTED^", ON JULY 12, 2023, AT 05:54AM.

NTSB investigation

The NTSB’s investigation of this event, with its probable cause and findings. Matched to this report by N-number and date.