CEN24LA013 · Magni M24
Magni M24 · Accident: loss of control in flight on approach
Event
- NTSB case
- CEN24LA013
- 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
Magni M24
- Aircraft type
- Magni M24
- Category
- Gyroplane
- 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
- N90HM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 3 years (built 2020)
- 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 · VFR pattern downwind
- 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
- Aircraft › Aircraft propeller/rotor
- Personnel issues › Psychological
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that, while on the downwind leg of the traffic pattern, he was distracted while looking for other traffic in the pattern when he noticed that his airspeed had decayed to 37 mph, below the aircraft flight manual’s recommended traffic pattern airspeed of 65 mph. The pilot attempted to correct by increasing engine throttle but subsequently lost control. The gyroplane impacted terrain while in the left downwind leg, which resulted in substantial damage to the main rotor system and empennage. Postaccident examination of the gyroplane revealed no preaccident mechanical failures or malfunctions that would have precluded normal operation. Based on the available information, the pilot likely unloaded the rotor blades inadvertently, known as buntover, when he applied engine throttle to correct for the decaying airspeed. The sudden throttle application caused the gyroplane to abruptly pitch forward and tumble. The FAA Rotorcraft Flying Handbook notes that, in most cases, the proper recovery procedure for the condition is to immediately remove power and load the rotor blades.
Probable cause
The pilot’s failure to maintain gyroplane control on the downwind leg, which resulted in impact with terrain. Contributing to the accident was the pilot’s distraction.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN24LA013
- Event ID
- 20231016193246
- Case number
- CEN24LA013
- 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: 9c6c3271fd12d185cfb30ee6cc13b4953abf2cd6cbe05fad5344f7369151c85b; retrieved 2026-09-16T18:13:14.242Z.