FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

IAD97LA106 · Robinson R22 BETA

6 Aug 1997 · Willimantic, CT, United States

Northeast Helicopter Robinson R22 BETA · Accident: uncontrolled altitude deviation while maneuvering

From Ellington Airport (7B9) to Ellington Airport (7B9)

Report a problem

Event

NTSB case
IAD97LA106
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
0
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
N717GT
Onboard fatalities
Unknown
Route
From Ellington Airport (7B9), Ellington, CTTo Ellington Airport (7B9), CT
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 · hover in ground effect
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
Uncontrolled altitude deviation
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 › Instructions, written/verbal, not understood
  • Dual student › Throttle/power control, removed
  • Pilot in command(cfi) › Remedial action, delayed

Approximate · Estimated position: the centre of Willimantic, CT, the place the record names. Not the accident site.

NTSB narrative

The student pilot flew his first two flights with another instructor. After practicing various maneuvers and while hovering at about 10 feet AGL with a new instructor, the student pilot was asked to return to their home airport to practice auto rotations. The student pilot turned the throttle to idle and the helicopter impacted the ground before the instructor could recover. The student pilot stated that he mistakenly thought the instructor requested an auto rotation from their present location, as he had done on his previous flights. No mechanical problems were reported by the instructor or the student.

Probable cause

The student pilot misunderstood the flight instructor's instructions and reduced the engine power to idle, and the Certificated Flight Instructor's delayed remedial action.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record IAD97LA106
Event ID
20001208X08650
Case number
IAD97LA106
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. 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: ea4b4b2d85a5b461c86c5ccbac93748aaa2602ec15b33f966977791709b08136; retrieved 2026-09-22T18:52:52.731Z.