GAA17CA112 · Robinson Helicopter R22 BETA
Summerskyz Robinson Helicopter R22 BETA · Accident: hard landing
From University of Illinois Willard Airport (CMI) to University of Illinois Willard Airport (CMI)
Event
- NTSB case
- GAA17CA112
- 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 Helicopter 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
- N8042B
- Operator
- Summerskyz
- Onboard fatalities
- Unknown
- Route
- From University of Illinois Willard Airport (CMI), Champaign, ILTo University of Illinois Willard Airport (CMI), Champaign, IL
- Aircraft age
- About 28 years (built 1989)
- 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 · flare/touchdown
- Defining eventThe 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The student pilot reported that, while practicing 180° autorotations about 500 ft above ground level, the flight instructor reduced the throttle, and the student pilot lowered the collective while simultaneously applying aft cyclic and right pedal. He added that the helicopter began to "dive," and the flight instructor took control of the helicopter.
The flight instructor reported that he initiated a go-around by applying aft cyclic and raising the collective, but they "continued in a rapid descent." The flight instructor added that at "roughly fifty feet, [he] flared harder to attempt a next-to-final arrest." The helicopter landed hard, the skids collapsed, and the main rotor blades severed the tailboom. The helicopter slid about 300 ft down the runway toward the right; the right skid stuck into the grass, and the helicopter rotated clockwise about the right skid, tipped onto the nose, and rolled to the left.
The flight instructor reported that he and the student pilot had performed about 10 to 12 practice autorotations before the accident.
The helicopter sustained substantial damage to the fuselage.
The flight instructor reported that there were no preaccident mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation.
Robinson Helicopter Company published Safety Notice, SN-38, dated July 2003 and revised in October 2004, which addressed training accidents caused by practice autorotations and stated, in part:
A high percentage of training accidents occur after many consecutive autorotations. To maintain instructor focus and minimize student fatigue, limit practice to no more than 3 or 4 consecutive autorotations.
The Federal Aviation Administration's (FAA) Helicopter Flying Handbook, FAA-H-8083-21A, dated 2012, addressed tailboom strikes during autorotations and stated, in part:
A power recovery can be made during training in lieu of a full touchdown landing. Refer to the section on power recovery for the correct technique. After the helicopter has come to a complete stop after touchdown, lower the collective pitch to the full-down position. Do not try to stop the forward ground run with aft cyclic, as the main rotor blades can strike the tail boom. Rather, by lowering the collective slightly during the ground run, more weight is placed on the undercarriage, slowing the helicopter.
One common error is holding the helicopter off the surface versus cushioning the helicopter on to the surface during an autorotation. Holding the helicopter in the air by using all of the rotor rpm potential energy usually causes the helicopter to have a hard landing, which results in the blades flexing down and contacting the tail boom. The rotor rpm should be used to cushion the helicopter on to the surface for a controlled, smooth landing instead of allowing the helicopter to drop the last few inches.
Probable cause
The flight instructor’s failure to arrest the descent rate during the practice autorotation, which resulted in a hard landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA17CA112
- Event ID
- 20170117X34946
- Case number
- GAA17CA112
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 157c64cea127fdf29d717525fc0cde18dab889cf461ffc3db222bef4d4ee3eed; retrieved 2026-09-16T04:57:14.673Z.