CEN17LA274
2017-07-15 · Colorado Springs, Colorado, United States · None · 1 aircraft · Status: Completed
Airport FLY
N181AL has since been reassigned. It is now registered to a different aircraft (DJI AGRAS T100), which was not involved in this event.
Aircraft involved
Probable cause & findings
The pilot's failure to lock the castering tailwheel in accordance with the airplane Owner's Manual and a checklist item and to abort the takeoff after the airplane exceeded its normal takeoff distance and/or reached the limit of the rudder control authority during the takeoff roll, which resulted in a loss of directional control and a subsequent runway excursion and impact with a light.
Factual narrative
"***This report was modified on September 17, 2019. Please see the docket for this accident to view the original report.***" On July 15, 2017, about 1300 mountain daylight time, an experimental amateur-built Endler Glasair SH2 (Glasair 1-TD), N181AL, ground looped and veered off runway 15 (6,000 feet by 60 feet, asphalt) during takeoff from Meadow Lake Airport (FLY), Colorado Springs, Colorado. The airplane impacted a taxiway light and was destroyed by fire. The pilot and passenger were uninjured. The airplane was registered to and operated by an individual under 14 Code of Federal Regulations Part 91 as a personal flight that was not operating on a flight plan. Visual meteorological conditions prevailed at the time of the accident. The local flight was originating at the time of the accident. The pilot stated that the airport automated weather observing system reported winds from 050 degrees at 7 knots, which was a "direct crosswind" to runways 15 and 33. The pilot decided to use runway 15 because an American Champion Decathlon or Citabria airplane "just landed" on runway 15, and runway 15 was the "favored runway" for the airport. The pilot said that there was a 1-2 knot tailwind for the accident takeoff. During the takeoff roll on runway 15, the airplane "continued to creep" to the left side of the runway even with application of [right] brake and rudder. The pilot made "one last big effort" to return the airplane to runway centerline, by "swerving." The airplane veered toward the left and off the runway surface. The airplane ground looped and a fire ensued from the right main landing gear well. Post-accident examination of witness marks along runway 15 revealed a mark consistent with continued application of right main landing gear wheel brake. The airplane veered off the runway about 2,400 down the runway and struck a taxiway light. The grass area located about 10-20 feet preceding the taxiway light exhibited burning. The right main landing gear was collapsed under the fuselage. The airplane was equipped with a castering tailwheel with a locking pin. The tailwheel was not a steerable assembly. The pilot said that the normal takeoff distance for the airplane was about 1,000 feet and when asked why the airplane impacted about 2,400 feet down the runway, he said "I don't know." He said that he discussed this in his analysis of the statement he provided. He said maybe it was an engine issue and did not know what the engine rpm was at the time of takeoff. The airplane owner's manual states that the tailwheel locks in the straight position for takeoff and landing. In the unlocked position, the tailwheel full swivels 360 degrees. The airplane checklist states that the tailwheel is to be in the locked position for takeoff. The pilot stated that the tailwheel was in the unlocked position during the takeoff. The National Transportation Safety Board Investigator-in-Charge asked the pilot what the maximum demonstrated crosswind velocity was for the airplane and the airplane's center of gravity (CG) location for the flight; the pilot said that he did not know the velocity and would check with the airplane owner and try to obtain the weight and balance form. The pilot said that based on the owner's information, the maximum demonstrated cross wind for the airplane was 15 knots. The pilot said his personal maximum crosswind velocity limit was 10 knots. The airplane owner's manual does not cite a maximum demonstrated crosswind velocity but a recommended velocity of 20 mph. The pilot said that the airplane weight and balance form was in the airplane and destroyed by the fire. The CG location for the flight could not be determined. The pilot said that the accident takeoff weight was about 470 lbs. He said that the fuel and passenger locations are roughly the moment arm from the airplane CG, so all weight has the same CG effect. The airline transport pilot reported that he was attempting to take off in a nonsteerable, castering, tailwheel-equipped experimental airplane with the tailwheel unlocked. During the takeoff roll, the airplane veered left. The pilot applied right rudder pedal input and then applied the right brake, but the airplane continued to veer left. The airplane veered off the runway about 2,400 ft down the runway and struck a taxiway light; the airplane's normal takeoff distance is 1,000 ft. A postcrash fire erupted from the right main landing gear well area. The continued application of right brake after full rudder deflection, as evidenced by witness marks along the runway, did not correct the airplane's path; instead, it likely increased the takeoff distance and created a heat source for the initiation of the fire. Further, when applying full rudder deflection did not correct the airplane's path, the pilot should have recognized there was a problem and aborted the takeoff. According to the airplane Owner's Manual and a checklist item in the manual, the tailwheel was to be in the locked position for takeoff and landing. Given the evidence, the pilot likely had not locked the castering tailwheel in accordance with applicable guidance, which resulted in the loss of directional control during takeoff. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
FAA avdata. C = Cause, F = Factor.
- C Aircraft-Aircraft systems-Landing gear system-Nose/tail landing gear-Not specified - C
- C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Directional control-Not attained/maintained - C
- C Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot - C
- C Personnel issues-Action/decision-Action-Lack of action-Pilot - C
- C Personnel issues-Task performance-Use of equip/info-Use of checklist-Pilot - C
- C Personnel issues-Task performance-Use of equip/info-Use of equip/system-Pilot - C
- C Environmental issues-Physical environment-Object/animal/substance-Sign/marker-Effect on operation - C
Verbatim from NTSB's published report. Source file
NTSB_2017_CEN17LA274.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Search this event elsewhere
External sources are reported, not agency: signal that something happened, not fact about what happened.
- TallyAero Live Wire Aviation press
- NTSB CAROL Agency ↗
- NTSB Docket Agency ↗
- Aviation Safety Network Aviation press ↗
- Kathryn's Report Aviation press ↗
- Aviation Herald Aviation press ↗
- AVweb Aviation press ↗
- Pilots of America Community ↗
- Reddit /r/flying Community ↗
- FlightAware Aviation press ↗
- AOPA accident database Aviation press ↗
- Google News News ↗
- DuckDuckGo News ↗
Related research
Matched on aircraft type or causal vocabulary (runway excursion). All research papers
- SKYbrary (Eurocontrol) 2024 · SKYbrary article Runway Excursion — SKYbrary Knowledge Base
SKYbrary runway excursion review — RE-OE (overruns) + RE-LO (lateral). Risk drivers: long landing, high approach speed, contaminated surface, tailwind, mis-set autobrakes.
- NTSB Aircraft Accident Reports 2019 · Accident report Embraer ERJ 175 Runway Excursion at Charlotte Douglas
Republic Airline ERJ-175 runway excursion CLT, January 2018. Examines a low-energy runway excursion involving misuse of autobrakes + thrust reverser response after a high-crosswind landing on a contam…
- NASA NTRS 2025 · Presentation Uncovering Resilient Behavior in the Aviation Safety Reporting System Using Large Language Models
Resiliency is present in everyday life, both in system design and exhibited by the operators that function within these systems.
- NASA NTRS 2025 · Conference Paper Uncovering Resilient Behavior in the Aviation Safety Reporting System Using Large Language Models
Resiliency is present in everyday life, both in system design and exhibited by the operators that function within these systems.
- Flight Safety Foundation 2024 · FSF / AeroSafety World Runway Safety Initiative Final Report (RSI)
Foundation Runway Safety Initiative final report — comprehensive analysis of runway excursion + incursion risk drivers worldwide.
- Semantic Scholar 2020 · Article Towards online prediction of safety-critical landing metrics in aviation using supervised machine learning
Abstract In recent years, due to the increased availability of data and improvements in computing power, application of machine learning techniques to various aviation safety problems for identifying,…