FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR13CA329 · Bell Helicopter Textron 206L-1

13 Jul 2013 · Inyokern, CA, United States

Southwest Heliservices Bell Helicopter Textron 206L-1 · Accident: hard landing during autorotation

From Inyokern Airport (IYK) to Inyokern Airport (IYK)

Report a problem

Event

NTSB case
WPR13CA329
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
API-reported fatalities
0 · all aircraft and ground
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

Bell Helicopter Textron 206L-1

Aircraft type
Bell 206
Category
Helicopter
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
N123HP
Onboard fatalities
Unknown
Route
From Inyokern Airport (IYK), Inyokern, CATo Inyokern Airport (IYK), Inyokern, CA
Aircraft age
Not recorded
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
Autorotation
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
Substantial

Cause areas

  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

During a flight for the purpose of the pilot to acquire the minimum flight hours to act as pilot-in-command, he and a pilot providing training (who was not a flight instructor) of the helicopter were practicing autorotation's from flight to a power recovery. The pilot providing training stated that on the fourth autorotation the pilot allowed the rotor rpm to decay and then froze on the controls, not allowing him to increase the throttle. He was able to level the helicopter; however, it landed hard and the main rotor blades struck and severed the tail boom.

The pilot reported that at the initiation of the maneuver, the pilot providing training rolled the throttle off, and the downwind glide was established. The pilot stated that as he leveled the helicopter and collective was pulled, he realized that the engine was not completely back on line. The pilot providing training subsequently took over the flight controls and flew the helicopter to the ground.

Both pilots reported the need for better verbal commands or stating intentions throughout the maneuver.

Neither pilot reported a preimpact mechanical malfunction or failure with the helicopter that would have precluded normal operation.

Probable cause

The failure of the pilot to maintain aircraft control during a practice autorotation maneuver and the pilot providing training's delayed remedial action which resulted in a hard landing. Contributing to the accident was the lack of communication between the two pilots.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR13CA329
Event ID
20130715X74541
Case number
WPR13CA329
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. 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: 053430a903081828e04c972d8906d16d92184932faca3cc910bb5544881aa2cc; retrieved 2026-09-15T22:13:08.203Z.