The U.S. aircraft register, updated daily
Accidents · NTSB CEN18LA306 · Final report

Bell 47G 3B accident near Custer, South Dakota, August 2, 2018

On August 2, 2018 at about 3:20 pm local time, a 1962 Bell 47G 3B (helicopter), registered N347BH, was substantially damaged in an accident during approach near Custer, South Dakota (Crazy Horse Base airport). It was an instructional flight under general aviation rules (Part 91). 1 person had minor injuries; 2 others were unhurt. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot’s mismanagement of rotor RPM and subsequent forced landing on uneven terrain which led to a dynamic rollover.

Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
August 2, 2018 · about 3:20 pm local time · cases in 2018
Place
Custer, South Dakota · Crazy Horse Base · cases near this airport · map
Type
Accident
Injuries
1 person had minor injuries; 2 others were unhurt.
Weather
visual conditions (good weather)
Aircraft
Bell 47G 3B No Series, built 1962 · all 47G 3Bs on the register
Registration
N347BH · registry record · serial 2771
Damage
Substantial damage
Flight
Instructional flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The commercial-rated pilot and flight instructor were completing familiarization training in the accident helicopter. After successful training flights the morning of the accident, the flight instructor decided to remove the dual controls from the helicopter, and one additional passenger was loaded before practicing hovering and a low-rpm recovery. On approach to land during the accident flight, about 100 feet above ground level (agl), the pilot noticed the rotor rpms drop below the normal operating range. The pilot increased throttle but was unable to recover rotor rpms within the normal range. The flight instructor stated that the helicopter lost a lot of altitude quickly and there was no time to recover. The pilot attempted a forced landing on the side of a roadway but caught the right skid on uneven ground, which led to a dynamic rollover and substantially damaged the tail section and tail rotor. The flight instructor stated that the engine had no mechanical anomalies before the flight and that the engine had “performed well” during both the accident flight and previous flights. The helicopter likely lost power and altitude due to the pilot’s mismanagement of rotor rpm resulting in the pilot having to attempt a forced landing on uneven terrain and a subsequent dynamic rollover.

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

  1. Loss of control in flight during approach defining event
  2. Dynamic rollover during landing

The NTSB's findings

  • Personnel issues › Action/decision › Action › Delayed action › Pilot

Pilot

  • Certificate: flight instructor, commercial pilot
  • Ratings: instructor: helicopter; instructor: instrument helicopter; instrument: helicopter; rotorcraft: helicopter
  • Flight time: 1,063 hours in all; 2 in this make and model; 176 in the last 90 days; 86 in the last 30 days; 884 as pilot in command; 245 on instruments
  • Last flight review: May 23, 2018
  • Medical certificate: Class 2 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

Pilot-Rated Passenger

  • Certificate: flight instructor, commercial pilot, foreign licence
  • Flight time: 1,100 hours in all
  • Seat: ctr
  • Injury: minor injuries

Passenger

  • Seat: rgt
  • Injury: no injuries

The aircraft

  • Airframe total time: 1,998.1 hours
  • Last inspection: 100-hour inspection, January 1, 2018; 47.8 hours since
  • Maximum gross weight: 2,900 lb
  • Seats: 3
  • Landing gear: fixed
  • Engine: Lycoming TVO-435D1B (piston); 584 hours total

The flight

  • Departed from: OSD9 Custer SD at 3:10 pm
  • Flight plan: none

Weather at the time

  • Light: daylight
  • Wind: from 320° at 3 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 75°F (24°C), dew point 32°F (0°C)
  • Altimeter: 30.07 inHg
  • Observation at 8:53 am from KCUT, 405 miles away

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers11

Photographs from the investigation 2 pictures from the NTSB's docket, as the NTSB released them

The NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.

Documents from the investigation the NTSB's docket: the evidence folder behind the report

4 documents, released by the NTSB on April 19, 2021. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Other NTSB records under N347BH the same tail number, which may have belonged to a different aircraft at the time

2026-01-29ERA26LA100 · accident near Floral City, FL · destroyed · no injuries

Connections how this case links to the rest of the register

Aircraft
Place
Record

The whole map of how records connect · these connections as data: /graph/accident/CEN18LA306.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.