GAA17CA258 · Autogyro Calidus
Autogyro Calidus · Accident: loss of control on ground during takeoff
From Bay Bridge Airport (W29) to Bay Bridge Airport (W29)
Event
- NTSB case
- GAA17CA258
- 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
Autogyro Calidus
- Aircraft type
- Autogyro CALIDUS
- 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
- N991TC
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Bay Bridge Airport (W29), Stevensville, MDTo Bay Bridge Airport (W29), Stevensville, MD
- Aircraft age
- Built the same year (2017)
- 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
- Loss of control on ground
- 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 › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot of the gyrocopter reported that, during the takeoff roll, the rotor rpm was not increasing. He continued the takeoff and kept the gyrocopter on the ground to gain airspeed by not moving the stick to the full-aft position. He added that this was an "old existing airplane habit." Subsequently, during the takeoff, the gyrocopter developed a "rotor flap," and he lost directional control. The gyrocopter came to rest on its side to the left of the runway.
The pilot added that not having the stick full aft prevented the rotor rpm from increasing and that the appropriate corrective action would have been to apply full-aft stick.
The gyrocopter sustained substantial damage to the fuselage and rotors.
The pilot reported that there were no preaccident mechanical failures or malfunctions with the gyrocopter that would have precluded normal operation.
The gyrocopter's Flight Manual stated that, during the takeoff roll, the pilot must "bring the control stick fully aft."
Probable cause
The pilot’s improper takeoff procedure, which resulted in a loss of directional control during the takeoff.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA17CA258
- Event ID
- 20170504X72527
- Case number
- GAA17CA258
- 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: 381be723e425d9bae53c351dbdf7fb546ec9fdd43d96dfbd571d5ecf0528e19e; retrieved 2026-09-16T05:14:12.320Z.