Bell 206 N98KR accident near Gumboro Township, Delaware

Aug 24, 2009 · NTSB number ERA09CA482 · Final report

Probable cause

The pilot’s failure to secure the flight controls before exiting the running helicopter. Contributing to the accident was the operator’s practice of exiting the helicopter while it was still running.

NTSB analysis

The helicopter pilot stated that he was completing an aerial application flight due to deteriorating weather. After landing on a wet, elevated platform, he exited the running helicopter, which was a common company practice during refueling and reloading operations. Moments later, the helicopter yawed to the right, slid off the platform and landed on the mast, resulting in substantial damage to the rotor assembly, left side fuselage, and tail boom. The pilot later stated that he did not recall securing the flight controls before exiting the helicopter. A Federal Aviation Administration examination of the accident scene revealed that the flight control friction locks were not tight, and that the landing platform was not level. A representative of the helicopter manufacturer stated that there was nothing published by the company that restricted a pilot from exiting a helicopter while it was running. However, there is a note in the pilot’s operating handbook for the engine shutdown procedure that states, “Pilot -- remain at flight controls until rotor has come to a complete stop.” A representative of the National Agricultural Aviation Association stated that although the practice of hot refueling was common in the industry, the practice of exiting a running helicopter was not.

Text from the NTSB. Open the NTSB docket for ERA09CA482 for the full record.

Event

Date
Aug 24, 2009
Type
Accident
Place
Gumboro Township, Delaware
Highest injury
None
Weather
Visual (VMC)
Light
Day

Bell 206

N-number
N98KR
Category
Helicopter
Damage
Substantial
Operating rule
Part 137 (agricultural)
Purpose of flight
Aerial application

From the NTSB aviation accident database: N-registered aircraft, events since 2008, data through Oct 28, 2026. The file is published monthly, so the latest weeks are incomplete and recent records can change. The official source is the NTSB aviation investigation search. CheckAero is independent and not affiliated with the NTSB.