FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA17CA296 · Schweizer 269C 1

22 May 2017 · Eden Prairie, MN, United States

Hummingbird Ventures Schweizer 269C 1 · Accident: dynamic rollover during landing

From Flying Cloud Airport (FCM) to Flying Cloud Airport (FCM)

Report a problem

Event

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

Schweizer 269C 1

Aircraft type
Schweizer 269
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
N2032S
Onboard fatalities
Unknown
Route
From Flying Cloud Airport (FCM), Minneapolis, MNTo Flying Cloud Airport (FCM), Minneapolis, MN
Aircraft age
About 17 years (built 2000)
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
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
Dynamic rollover
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 › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The flight instructor in the helicopter reported that the student pilot was practicing autorotations from a hover while pointing the helicopter into the wind over tall grass from about 1 ft above the ground. He added that the student "rolled off the throttle, the helicopter descended to the ground, appeared to bounce, moved slightly to the right and began a quick roll to the right." Subsequently, the helicopter pivoted on its right skid, the main rotor impacted terrain, and the helicopter rolled over to the right.

The main rotor and windscreen sustained substantial damage.

The flight instructor reported that there were no preaccident mechanical malfunctions or failures with the helicopter that would have precluded normal operation.

Probable cause

The student pilot's loss of lateral control while practicing autorotations from a hover and the flight instructor's delayed remedial action, which resulted in a bounced landing and dynamic roll-over.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA17CA296
Event ID
20170522X73152
Case number
GAA17CA296
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. 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: 1d9d4247d0ad6d55b8d920d0e53ffb5db129b430dc64557f147d6d66933c3f6f; retrieved 2026-09-16T05:18:15.925Z.