ERA20LA076 · Magni M-24 PLUS
Magni M-24 PLUS · Accident: medical event during takeoff
From Nashua Airport / Boire Field (ASH) to Nashua Airport / Boire Field (ASH)
Event
- NTSB case
- ERA20LA076
- 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 M-24 PLUS
- Aircraft type
- Magni M-24
- 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
- N327JD
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Nashua Airport / Boire Field (ASH), Nashua, NHTo Nashua Airport / Boire Field (ASH), Nashua, NH
- Aircraft age
- About 1 year (built 2019)
- 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
- Takeoff
- 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
- Medical event
- 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
- Personnel issues › Physical
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
According to a witness, the gyroplane used more runway than typical to become airborne before it began to drift toward the left edge of the runway. About halfway down the runway, the gyroplane departed the runway, bounced over a taxiway, porpoised, and came to rest inverted. The witness stated that he saw no indication that the pilot had attempted to slow down or correct the left deviation from centerline. After the accident, a medical evaluation identified that the pilot had experienced a cerebral infarction (stroke). Symptoms often develop suddenly and can include numbness or weakness of the face, arm, or leg; confusion; difficulty speaking; trouble seeing; severe headache; and loss of coordination. It is likely that the pilot was incapacitated by the stroke during the takeoff roll.
Probable cause
The pilot's incapacitation during the takeoff roll due to a stroke.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA20LA076
- Event ID
- 20200115X02226
- Case number
- ERA20LA076
- 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, 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: 3c3eb7024b5272a937c90640337d145e033029339f67a2c02dde221f10a81c41; retrieved 2026-09-16T10:55:59.853Z.