FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN26LA027 · Robinson Helicopter R22 BETA II

21 Oct 2025 · Springfield, MO, United States

So Fly Flight Training Academy Robinson Helicopter R22 BETA II · Accident: loss of control in flight during autorotation

From Downtown Airport (3DW) to Downtown Airport (3DW)

Report a problem

Event

NTSB case
CEN26LA027
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
0
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 II

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
N74583
Onboard fatalities
Unknown
Route
From Downtown Airport (3DW), Springfield, MOTo Downtown Airport (3DW), Springfield, MO
Aircraft age
About 20 years (built 2005)
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
Autorotation
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
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

  • Aircraft › Aircraft oper/perf/capability
  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Action/decision
  • Personnel issues › Psychological
  • Personnel issues › Task performance

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

NTSB narrative

Prior to the training flight, the flight instructor received an official weather briefing from a commercial source, and the terminal area forecast reported for high winds later in the day. The flight instructor and the pilot receiving instruction were practicing autorotations in the helicopter at the airport. During the last autorotation, after the entry and the engine power at idle, the flight instructor told the pilot to “steer” multiple times and he even gave the cyclic a “nudge.” The helicopter was oriented to about a 240° heading while drifting past the runway centerline to the south. The helicopter was drifting to the left and the flight instructor reported the pilot was unable to turn the helicopter to the right. The helicopter continued to travel to the south beyond airport property toward a public sports complex. The flight instructor initiated a flare. The helicopter impacted a grass field upright near trees in the public sports complex, and it came to rest on its left side. The helicopter sustained substantial damage to the fuselage, the main rotor system, the tail cone, the empennage, and the tail rotor system. The flight instructor was unsure if there was a flight control malfunction and he thought that if there was a flight control malfunction, initiating a power recovery during the autorotation might exacerbate a malfunction. While the flight instructor decided to use a 300 ft agl decision check altitude for the autorotations, a power recovery was not initiated. Postaccident examination of the airframe confirmed flight control continuity. Near the time of the accident and landing to runway 29, the wind originated from 310°, with a wind speed of 11 kts, and gusting to 21 kts. A review of meteorological data found some speed shear in the lowest 2,000 ft agl of about 15 kts above average surface magnitudes near the airport for a period near the accident time. It is likely that during the practice autorotation, the pilot did not compensate for the gusting wind condition and the speed shear, and the flight instructor did not execute a timely remedial action with initiating a power recovery, which resulted in the helicopter impacting terrain.

Probable cause

The pilot’s failure to maintain directional control and the flight instructor’s lack of proper remedial action during the practice autorotation that resulted in the helicopter impacting terrain. Contributing to the accident was the presence of the gusting wind condition and the presence of speed shear.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN26LA027
Event ID
20251021201908
Case number
CEN26LA027
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, cause areas. 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: 25addc48afc7eda080b502ad715a5e61466e9c6735c26e8e8e6028cb9d5126f5; retrieved 2026-09-16T20:29:57.515Z.