NTSB CAROL · Event
Event WPR18LA190
Aircraft involved
Probable cause & findings
The pilot's failure to properly configure the gyrocopter for takeoff, which resulted in it developing high speed and led to a subsequent loss of control.
Factual narrative
On July 7, 2018, about 1300 Pacific daylight time an Autogyro, Calidus, gyrocopter, N623AG, struck the runway shortly after takeoff at the Tacoma Narrows airport (TIW), Tacoma, Washington. The commercial pilot and the passenger received minor injuries. The gyrocopter received substantial damage to the rotor system, and fuselage. The gyrocopter was registered to and operated by the pilot under the provisions of Title 14 Code of Federal Regulations Part 91 as a personal flight. Visual meteorological conditions prevailed, and no flight plan was filed. The local flight was originating at the time of the accident. The pilot stated he had received clearance from the tower for takeoff on runway 17. He taxied onto the runway and reported to the tower he would need about 30 seconds to be ready for takeoff. While on the runway he had difficulty getting the pre-rotator to engage with the rotor ring gear. The pilot said that the tower controller transmitted to him and stated, "that sure is a long 30 seconds." The pilot cancelled his takeoff clearance and taxied off the runway to a run up area where he successfully engaged the pre-rotator to the rotor ring gear. He then requested and received clearance from the tower controller to depart from runway 17. He taxied onto the runway, achieved 200 RPM on the rotor and began his takeoff roll. The pilot stated that he recalled pulling the control stick aft while the gyrocopter was accelerating down the runway. During the takeoff roll the gyrocopter suddenly became airborne, began shaking violently, descended, and struck the runway where it then skidded approximately 100 ft, exited the left side of the runway and came to rest on its left side. The pilot and passenger egressed with the help of witnesses. According to a witness, the gyrocopter began the takeoff roll with the rotor parallel with the runway. He observed the rotor tilt back to what appeared to be a 45° angle. The gyrocopter then climbed, rolled onto its side, struck the ground, then slid off the runway. In an interview with the pilot's flight instructor, who trained the pilot in the gyrocopter, she explained the proper sequence of events for getting the gyrocopter ready for takeoff. She stated when engaging the pre-rotator, it is essential to keep the control stick fully forward to protect the airframe from the slow spinning rotor. A fully forward control stick would place the rotor level to the ground. The rotor needs the 200 RPM to protect the fuselage when the control stick is then moved fully aft for the takeoff roll. She explained that beginning the takeoff roll with a level rotor would allow the gyrocopter to accelerate quickly and build undesirable speed. Any attempt to then bring the control stick back, which tilts the rotor aft, would cause the gyrocopter to go straight up. She stated pilots may forget to pull the control stick fully aft after pre-rotating the rotor to 200 RPM. This creates the potential for takeoff rolls with the control stick not fully aft and the rotor level with the ground. A review of the Owner's Manual revealed a warning that states "Prior to releasing the wheel brake, make sure that the control stick is fully aft, if headwind components allows. A takeoff run with a flat rotor system may have fatal consequences." During an examination of the gyrocopter, after the accident, it was observed the aft seat had a control stick installed. The Owner's Manual states "the aft control stick must be removed unless the passenger seat is occupied by a qualified flight instructor". While preparing for takeoff in the gyrocopter, the commercial pilot had difficulty getting the prerotator to engage with the rotor ring gear, so he aborted the takeoff attempt. He then taxied off the runway to a run-up area and successfully engaged the prerotator to the rotor ring gear. The pilot then taxied onto the runway, and the rotor reached 200 rpm, after which he began the second takeoff attempt. The pilot stated that he recalled pulling the control stick aft while the gyrocopter was accelerating down the runway. Subsequently, the gyrocopter suddenly began climbing and shaking violently. The pilot then lost control of the gyrocopter, and it descended, struck the runway, skidded about 100 ft, exited the left side of the runway, and then came to rest on its left side. A witness reported that the gyrocopter began the takeoff roll with the rotor level with the runway. During an interview with the flight instructor who trained the pilot in the gyrocopter, she stated that, when engaging the prerotator for takeoff, it is essential to keep the control stick fully forward to protect the airframe from the slow-spinning rotor. A fully forward control stick would place the rotor level with the ground, as described by the witness. The rotor then needs to achieve 200 rpm, followed by the control stick being moved fully aft for the takeoff roll, tilting the rotor. Further, the Airplane Owner's Manual contained a warning stating that "Prior to releasing the wheel brake, make sure that the control stick is fully aft…A takeoff run with a flat rotor system may have fatal consequences." Given the pilot and witness statements and that the gyrocopter skidded 100 ft after impacting the runway, it is likely that the pilot did not pull the control stick fully aft after prerotating the rotor to 200 rpm and conducted the second takeoff attempt with the control stick not fully aft and with the rotor level with the ground. The pilot’s failure to properly configure the gyrocopter for takeoff resulted in it developing high speed during the takeoff roll and the subsequent loss of control. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).
- C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Configuration-Incorrect use/operation - C
- C Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot - C
Verbatim from NTSB's published report. Source file
NTSB_2018_WPR18LA190.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (stall, loss of control). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- Semantic Scholar 2016 · Article (Interacción)
Trajectory Recovery System: Angle of Attack Guidance for Inflight Loss of Control
This paper describes the design and development of an ecological display to aid pilots in the recovery of an In-Flight Loss of Control event due to a Stall (ILOC-S).
- NTSB Aircraft Accident Reports 2010 · Accident report
Loss of Control on Approach — Colgan Air Flight 3407
Colgan Air 3407 / Continental Connection (Q400) Buffalo NY, February 12, 2009 — 50 fatalities. Definitive investigation of the Colgan 3407 stall-stick-pusher crash on approach to Buffalo.
- NASA NTRS 2026 · Conference Paper
Computational Analysis of Steady State Aerodynamics of Transonic Truss-Braced Wing Configuration in Deep Stall
This study presents a computational investigation of steady state aerodynamics of the Subsonic Ultra-Green Aircraft Research (SUGAR) Transonic Truss-Braced Wing (TTBW) configuration over a wide range …
- Embry-Riddle Scholarly Commons 2025 · Journal article (JAAER)
A Scoping Review of Aviation Loss of Control Inflight Research
Loss of control – inflight (LOC-I) contributes to aircraft accidents at unacceptably high rates. Significant industry efforts and research have aimed to improve LOC-I prevention, detection, and recove…
- arXiv 2025 · arXiv preprint
Quadratic Programming Approach to Flight Envelope Protection Using Control Barrier Functions
Ensuring the safe operation of aerospace systems within their prescribed flight envelope is a fundamental requirement for modern flight control systems.
- SKYbrary (Eurocontrol) 2024 · SKYbrary article
Loss of Control In-Flight (LOC-I) — SKYbrary Knowledge Base
SKYbrary comprehensive knowledge-base entry on Loss of Control In-Flight — definitions, contributing factors, accident case studies (Air France 447, Colgan 3407), and prevention strategies.
Browse the full corpus — academia portal ↗