CEN16LA015 · Bobby Martin AUTOGYRO MTO SPORT
Bobby Martin AUTOGYRO MTO SPORT · Accident: system/component malfunction/failure (non-power) while maneuvering
From Chambers County Airport (T00) to Chambers County Airport (T00)
Event
- NTSB case
- CEN16LA015
- 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
Bobby Martin AUTOGYRO MTO SPORT
- Aircraft type
- Bobby Martin AUTOGYRO MTO SPORT
- 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
- N3232Z
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Chambers County Airport (T00), Wallisville, TXTo Chambers County Airport (T00), Wallisville, TX
- Aircraft age
- About 2 years (built 2013)
- 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
- Maneuvering · low-altitude flying
- 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
- System/component malfunction/failure (non-power)
- 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 propeller/rotor
- Environmental issues › Physical environment
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The private pilot departed in a gyroplane on a local sightseeing flight. About 30 minutes into the flight, at an altitude of about 250-300 ft above the ground, the pilot reported hearing and feeling something break loose behind him, located near the engine, followed by a severe vibration. The pilot reduced power, which reduced the vibration but resulted in the gyroplane descending. He added power again, but the gyroplane vibrated severely and did not regain performance. The pilot performed a forced landing into a swamp, where the gyroplane's right main landing gear sank and the gyroplane rolled over onto its right side.
Postaccident examination of the pusher propeller showed that one of the three carbon fiber blades had split and come apart. Further examination of the propeller blade showed characteristics consistent with damage from impact with an object; however, no object that could have caused the impact damage was located. The examination did not reveal evidence of any other preimpact malfunctions or failures of the gyroplane that would have precluded normal operation.
Probable cause
Fracture of the pusher propeller blade due to impact damage from an unknown object while in flight, which resulted in a severe vibration and a loss of thrust.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN16LA015
- Event ID
- 20151019X55704
- Case number
- CEN16LA015
- 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: 52674b97a6f31db106368fa96a73b1a85d48584463fdf1e6a4168b1ada9f513a; retrieved 2026-09-16T02:54:03.061Z.