FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA05CA182 · Robinson R22 Beta

27 Aug 2005 · Boise, ID, United States

Robinson R22 Beta · Accident: hard landing while maneuvering

From Boise Air Terminal/Gowen Field (BOI) to Boise Air Terminal/Gowen Field (BOI)

Report a problem

Event

NTSB case
SEA05CA182
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

Robinson R22 Beta

Aircraft type
Robinson R22
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
N845SH
Operator
Unknown
Onboard fatalities
Unknown
Route
From Boise Air Terminal/Gowen Field (BOI), Boise, IDTo Boise Air Terminal/Gowen Field (BOI), Boise, ID
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
Maneuvering
First occurrenceThe 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

  • Dual student › Relinquishing of control, delayed
  • Pilot in command(cfi) › Communications, inadequate

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The instructor pilot reported that he and the student pilot were practicing power recovery autorotations at the Boise airport. During the tenth practice autorotation, with the student pilot on the controls, the instructor noted a lower than normal main rotor RPM (approximately 94 percent) and elected to take the controls in an effort to make the necessary inputs to recover from the maneuver. The instructor pilot reported that during the transition (approximately 60 feet agl), there was a "struggle" for the controls and corrective action was delayed resulting in a hard landing and substantial damage to the helicopter. The instructor pilot stated that he does not recall verbalizing the transfer of control to the student pilot.

Probable cause

Inadequate communications between the certified flight instructor and student pilot, and the student pilot's delay in relinquishing controls resulting in a hard landing during a practice autorotation.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA05CA182
Event ID
20050914X01453
Case number
SEA05CA182
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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, coordinates. 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: 7a19231945f64157add39cf30150c8a5fc0eb867e3309acb8303c83e7ad1e77e; retrieved 2026-09-21T18:55:00.751Z.