Amateur-built AUTOGYRO MTO SPORT accident near Wallisville, Texas, October 17, 2015
On October 17, 2015 at about 5:00 pm local time, a 2013 amateur-built AUTOGYRO MTO SPORT (gyroplane), registered N3232Z, was substantially damaged in an accident during maneuvering (low-alt flying) near Wallisville, Texas (Chambers County airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
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.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- October 17, 2015 · about 5:00 pm local time · cases in 2015
- Place
- Wallisville, Texas · Chambers County · cases near this airport · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Amateur-built AUTOGYRO MTO SPORT, built 2013
- Registration
- N3232Z · no longer on the register · serial M01054
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Sys/Comp malf/fail (non-power) during maneuvering (low-alt flying) defining event
- Loss of engine power (partial) during maneuvering
- Off-field or emergency landing during emergency descent
- Roll over during landing (flare/touchdown)
The NTSB's findings
- cause Aircraft › Aircraft propeller/rotor › Propeller system › Propeller blade section › Damaged/degraded
- cause Environmental issues › Physical environment › Object/animal/substance › (general) › Contributed to outcome
- Environmental issues › Physical environment › Terrain › Wet/muddy terrain › Contributed to outcome
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 432 hours in all; 132 in this make and model
- Last flight review: September 1, 2015
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: frt
- Injury: no injuries
The aircraft
- Airframe total time: 132 hours
- Last inspection: condition inspection, July 1, 2015
- Maximum gross weight: 1,102 lb
- Seats: 2
- Landing gear: fixed
- Engine: Rotax 914 UL (piston); 132 hours total
The flight
- Departed from: T00 Wallisville TX at 4:30 pm
- Destination: T00 Wallisville TX
- Flight plan: none
Weather at the time
- Light: daylight
- Wind: from 050° at 11 knots
- Visibility: 10 statute miles
- Sky: broken clouds at 25,000 ft
- Temperature: 75°F (24°C), dew point 41°F (5°C)
- Altimeter: 30.28 inHg
- Observation at 4:50 pm from KEFD, 26 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
5 documents, released by the NTSB on April 30, 2019. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot's Statement | PDF, 2 pages | View Download |
| 2 | Manufacturer Representative's Statement | PDF, 1 page | View Download |
| 3 | Maps of the Accident Location | PDF, 3 pages | View Download |
| 4 | Gerry Speich E-mail | PDF, 3 pages | View Download |
| 5 | Photographs | PDF, 3 pages | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Connections how this case links to the rest of the register
- N3232Z: not on the register today · the record of its deregistration
- Engine: Rotax 914 UL 305 aircraft carry this series today · as the NTSB recorded it
- Chambers County · nearest airport
- Accidents and incidents in Texas 6,244 since 1982 · 1,061 in the last ten years
- Texas 29,986 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/CEN16LA015.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
