CHI04CA116 · Robinson R22 Beta
Robinson R22 Beta · Accident: hard landing
From Dousman, WI to East Troy Municipal Airport (57C)
Event
- NTSB case
- CHI04CA116
- 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
- N215WW
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Dousman, WITo East Troy Municipal Airport (57C), East Troy, WI
- 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
- Landing
- 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 › Remedial action, inadequate
- Pilot in command › Rotor RPM, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The helicopter landed hard following a loss of rotor rpm during the landing attempt. The pilot stated that during the landing attempt, approximately 20 feet above ground level, the low rotor RPM horn sounded along with the corresponding warning light. The pilot reported the helicopter "settled rapidly" as he lowered the collective and increased the throttle. The pilot stated that the helicopter was too low for a successful recovery and impacted left skid first. The pilot reported "It may have been possible that I delayed throttle governor by initially holding throttle/collective control too tightly." The pilot also stated that the accident could have been prevented by "closer observation of [the] main rotor RPM."
Probable cause
The pilot's failure to maintain proper rotor RPM during the hover landing and his inadequate remedial action, which resulted in the hard landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI04CA116
- Event ID
- 20040524X00638
- Case number
- CHI04CA116
- 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: add84aa055b1a9ce32f3d9952861fd73c785bd33e9c268b0abae6a0440adabfb; retrieved 2026-09-22T07:35:01.802Z.