FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

IAD05LA108 · Robinson R22

22 Jul 2005 · Nashua, NH, United States

Robinson R22 · Accident: loss of control in flight while maneuvering

From Nashua Airport / Boire Field (ASH) to Nashua Airport / Boire Field (ASH)

Report a problem

Event

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

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
N8041J
Operator
Unknown
Onboard fatalities
Unknown
Route
From Nashua Airport / Boire Field (ASH), Nashua, NHTo Nashua Airport / Boire Field (ASH)
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
Loss of control in flight
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

  • Pilot in command(cfi) › Aircraft control, not maintained
  • Pilot in command(cfi) › Remedial action, 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 purpose of the flight was to give a student an introductory flight. After conducting a local flight, they returned for "hover work" at the airport and then air taxied to a point just short of a runway. While waiting to cross the runway, the instructor placed the helicopter in a hover and had the student try to hold the helicopter steady while he kept his hands on the controls. The student then "pulled the controls" from his hands, and moments later, the instructor realized that the student had let go of the controls. The helicopter then "rolled hard left, very fast" and the instructor could not regain control. The main rotor blades then struck the ground. Examination of the helicopter revealed no evidence of any preimpact malfunctions.

Probable cause

The flight instructor's failure to maintain aircraft control during a introductory flight and his inadequate remedial actions.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record IAD05LA108
Event ID
20050820X01293
Case number
IAD05LA108
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: 0185540aaa0aa0adba301e399abe7d549cb4e4ec2d498943ddd8845eac83691d; retrieved 2026-09-22T05:37:14.730Z.