# NTSB CEN14TA116: Autogyro Mtosport, N250TX, Spring, TX, January 16, 2014

- Type: NTSB accident investigation
- Classification: Accident · Minor injuries · Final report
- Date: January 16, 2014, 11:40 local (17:40 UTC)
- Place: Spring, TX
- Coordinates: 30.061944, -95.55278
- Nearby events: https://openairdocs.org/map.md?lat=30.0619&lon=-95.5528&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Defining event: [Landing-landing roll: Loss of control on ground](https://openairdocs.org/ntsb-events/230)
- Highest injury: Minor injuries
- Injuries: 2 minor
- Status: Completed, report April 23, 2014
- Report: Approved by Office Director
- NTSB office: Central Region
- Parties: FAA Houston FSDO
- NTSB case key (mKey): 88701
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN14TA116
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/88701/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=88701
- Page: https://openairdocs.org/ntsb/CEN14TA116

## Probable cause

The pilot’s failure to maintain the gyroplane’s rotor control during the landing roll in gusting crosswind conditions.

## Findings

NTSB's coded findings; those marked are part of the probable cause.

- [Action: incorrect action performance](https://openairdocs.org/ntsb-findings/02041015): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Auto Gyro MTOSPORT, 1 case](https://openairdocs.org/ntsb-findings/02041015/cases.md?model=05629Y9), [All aircraft, 1,386 cases](https://openairdocs.org/ntsb-findings/02041015/cases.md)
- [Main rotor system: main rotor blade system](https://openairdocs.org/ntsb-findings/01046210): Aircraft › Aircraft propeller/rotor · Not specified; cases with it: [Auto Gyro MTOSPORT, 1 case](https://openairdocs.org/ntsb-findings/01046210/cases.md?model=05629Y9), [All aircraft, 60 cases](https://openairdocs.org/ntsb-findings/01046210/cases.md)
- [Wind: crosswind](https://openairdocs.org/ntsb-findings/03034040): Environmental issues › Conditions/weather/phenomena · Contributed to outcome; cases with it: [Auto Gyro MTOSPORT, 1 case](https://openairdocs.org/ntsb-findings/03034040/cases.md?model=05629Y9), [All aircraft, 1,008 cases](https://openairdocs.org/ntsb-findings/03034040/cases.md)
- [Wind: gusts](https://openairdocs.org/ntsb-findings/03034045): Environmental issues › Conditions/weather/phenomena · Contributed to outcome; cases with it: [Auto Gyro MTOSPORT, 1 case](https://openairdocs.org/ntsb-findings/03034045/cases.md?model=05629Y9), [All aircraft, 1,199 cases](https://openairdocs.org/ntsb-findings/03034045/cases.md)
- [Performance/control parameters](https://openairdocs.org/ntsb-findings/01062000): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Auto Gyro MTOSPORT, 1 case](https://openairdocs.org/ntsb-findings/01062000/cases.md?model=05629Y9), [All aircraft, 1,269 cases](https://openairdocs.org/ntsb-findings/01062000/cases.md)

## Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event best describes what happened.

- [Landing-landing roll: Loss of control on ground](https://openairdocs.org/ntsb-events/230) (defining event); cases with it: [Auto Gyro MTOSPORT, 1 case](https://openairdocs.org/ntsb-events/230/sequence.md?model=05629Y9), [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md)
- [Landing-landing roll: Dragged wing/rotor/float/other](https://openairdocs.org/ntsb-events/093); cases with it: [Auto Gyro MTOSPORT, 1 case](https://openairdocs.org/ntsb-events/093/sequence.md?model=05629Y9), [All aircraft, 319 cases](https://openairdocs.org/ntsb-events/093/sequence.md)
- [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Auto Gyro MTOSPORT, 1 case](https://openairdocs.org/ntsb-events/300/sequence.md?model=05629Y9), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md)
- [Landing-landing roll: Roll over](https://openairdocs.org/ntsb-events/097); cases with it: [Auto Gyro MTOSPORT, 1 case](https://openairdocs.org/ntsb-events/097/sequence.md?model=05629Y9), [All aircraft, 261 cases](https://openairdocs.org/ntsb-events/097/sequence.md)

## Analysis

The pilot stated that, as he approached the runway, the tower controller reported that the wind was 210 degrees at 11 knots, gusting to 19 knots. He performed a go-around due to the wind gusts blowing the gyroplane off course. He was then cleared to land on the parallel runway. The pilot reported that a quartering crosswind existed as he flew the approach; however, he landed the gyroplane without incident. As the pilot was reaching forward to change the pneumatic mode selector button from the "flight" to the "brake" position, a strong westerly wind gust lifted the gyroplane. The right wheel came off the ground, which caused the main rotor blade to strike the runway. The pilot attempted to straighten the gyroplane, but it veered off the runway and rolled onto its right side, which resulted in substantial damage to the empennage and main rotor. The pilot reported no preaccident mechanical malfunctions or failures with the gyroplane that would have precluded normal operation. The calculated crosswind component of 10 knots was below the allowable maximum landing crosswind component of 20 knots. The gyroplane's flight manual states that, after landing, "use lateral control into wind to maintain rotor disc in level flight. Adjust lateral control input as rotor speed decays" before changing the pneumatic mode selector to the "brake" position.

## Factual narrative

On January 16, 2014, about 1140 central standard time, an AutoGyro MTOsport gyroplane, N250TX, sustained substantial damage during landing roll when it veered off the runway and rolled over after its main rotor struck the runway at the David Wayne Hooks Memorial Airport (DWH), Spring, Texas. The pilot and one passenger received minor injuries. The gyroplane was registered to and operated by the City of Tomball, Texas, as a public use aircraft. Visual meteorological conditions prevailed at the time of the accident, and no flight plan was filed. The gyroplane departed DWH at 1030 on a local flight. The pilot stated that the control tower reported the wind was 210 degrees at 11 knots gusting to 19 knots as he attempted to land on runway 17L (3,987 feet by 35 feet, asphalt). He performed a go-around due to the wind gusts blowing the gyrocopter off course, and he was cleared to land on runway 17R (7,009 feet by 100 feet, asphalt). The pilot reported a quartering crosswind as he flew the approach to 17R; however, he landed the gyroplane without incident. He reported that as he was reaching forward to change the pneumatic mode selector button from "Flight" to "Brake," a strong gust of wind from the west lifted the gyrocopter. The right wheel came off the ground allowing the main rotor blade to strike the runway surface. The pilot attempted to straighten the gyroplane, but it veered off the runway and rolled onto its right side, resulting in substantial damage to the empennage and main rotor. The pilot reported no preaccident mechanical malfunctions or failures with the gyroplane that would have precluded normal operation. The flight manual for the gyroplane state that the maximum crosswind component for take-off and landings is 20 knots. The maximum tailwind component for take-off and landing is 5 knots. The maximum wind speed or gust intensity is 40 knots. The calculated crosswind component during the landing was about 10 knots. The flight manual for the gyroplane lists the following "After Landing" procedures: 1. Control stick full forward to level-off rotor disc, at latest when rotor speed leaves green arc! Be prepared for reduced rotor drag! 2. Use lateral control into wind to maintain rotor disc in level attitude. Adjust lateral control input as rotor speed decays. 3. Bring pneumatic mode selector to BRAKE position and return to wheel brake with left hand. 4. Apply rotor brake pressure by using AFT TRIM. Monitor pressure gauge. 5. Taxi carefully, preferably not above walking speed and mind high center of gravity when taking turns. 6. Do not vacate gyroplane until engine and rotor is at a complete stop.

## Aircraft

- Registration: [N250TX](https://openairdocs.org/aircraft/N250TX), registered now, S/N US10S01 (OpenAirDocs)
- Reported make and model: AUTOGYRO MTOSPORT
- Registry model: [Auto Gyro MTOSPORT](https://openairdocs.org/model/auto-gyro-mtosport) (registry code 05629Y9) (OpenAirDocs)
- Registry engine: [Rotax 912ULS series](https://openairdocs.org/engine/rotax-912uls-series) (registry code 55572, 4 cycle) (OpenAirDocs)
- Category: Gyroplane
- Serial number: US10S01
- Year built: 2010
- Airframe hours: 522
- Engines: ROTAX 912 ULS 100 horsepower reciprocating
- Damage: Substantial damage
- Flight: Public aircraft - local, Public use
- Operator: City Of Tomball
- Registered owner: City Of Tomball
- Airworthiness certificate: Special, Experimental (Special)
- Departed: DWH, Spring, TX
- Destination: DWH, Spring, TX
- Airport: DWH, David Wayne Hooks Memorial, runway 17R, 7,009 × 100 ft, asphalt

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 42; injuries: none; student; medical: class 3, without waivers/limitations; seat: front; flight hours: 228 total, 155 in this make and model, 16 in the last 90 days

## Weather

- Conditions: Visual (VMC), Day
- Wind: 210° at 17 knots, gusting 24
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 66 °F, dew point 37 °F
- Altimeter: 30.14 inHg
- Observed at: DWH

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 20140116000829A](https://openairdocs.org/incident/20140116000829A), Jan 16, 2014: Auto Gyro Gmbh MTOSPORT, Tomball, TX, Substantial damage. The houston FSDO received notice of the Tomball police departments gyrocopter being involved in an accident on 01/16/2014 at 1215. There were no injuries and…

## Docket (4 files)

The files NTSB released with the investigation on February 6, 2014, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=88701. 6.9 MB in all.

- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 4.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40408872&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF
- Aircraft Operator's Manual Excerpts (item 2, .PDF, 2.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40408930&FileExtension=.PDF&FileName=Aircraft%20Operator%27s%20Manual%20Excerpts-Master.PDF
- Crosswind Component Calculation (item 3, .PDF, 146 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40408993&FileExtension=.PDF&FileName=Crosswind%20Component%20Calculation-Master.PDF
- Photo 1. View of gyroplane lying on its side. (item 4, .PDF, 462 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40408878&FileExtension=.PDF&FileName=Photo%201.%20View%20of%20gyroplane%20lying%20on%20its%20side.-Master.PDF

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.
