FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

IAD03CA061 · Robinson R22 Beta

27 Jun 2003 · Nashua, NH, United States

Robinson R22 Beta · Accident: hard landing on approach

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

Report a problem

Event

NTSB case
IAD03CA061
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
N185MH
Operator
Unknown
Onboard fatalities
Unknown
Route
From Nashua Airport / Boire Field (ASH), Nashua Boire Fi, NHTo Nashua Boire, NH
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
Approach
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

  • Pilot in command › Compensation for wind conditions, inattentive

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

NTSB narrative

While the student pilot was practicing departures and approaches-to-a-hover, he had to apply more right torque pedal during departure than usual. While completing another normal approach, when the helicopter was about 10 feet agl, the pilot increased the collective to enter into a hover. When he increased the collective, the helicopter descended rapidly to the ground and landed on the rear skids. Then the nose dropped, and the helicopter slid forward. The pilot stated that in retrospect, he recalled needing a "great deal" of right peddle to maintain heading, "perhaps nearly full travel." He did not realize until later that he had landed with a tailwind, and subsequently remembered looking directly into the mouth of the windsock.

Probable cause

The pilot's failure to determine the wind direction, which resulted in a hard, tailwind landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record IAD03CA061
Event ID
20030819X01361
Case number
IAD03CA061
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: 4571a7cf78ba30ca2f6684bd3d4e36877df62b6538e7ce4163bfece17c274f1b; retrieved 2026-09-22T09:05:29.795Z.