CEN21LA129
2021-02-05 · Larned, Kansas, United States · None · 1 aircraft · Status: Completed
Airport LQR
Current FAA registration · N115FP
- Make / Model
- COLUMBIA AIRCRAFT MFG LC42-550FG
- Year of manufacture
- 2007 · 14 years old at event
- Engine
- CONT MOTOR IO-550-N (310 hp)
- Seats / Engines
- 4 seats · 1 engine
- Last airworthiness date
- 20070420
- ADS-B equipped
- Yes — Mode-S A03F51
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The pilot’s failure to allow sufficient time for the brakes to cool after a previous aborted takeoff, resulting in a runway excursion during a second aborted takeoff due to degraded braking performance. Contributing to the accident was the contact of the hot brakes with a dry grassy area during the second aborted takeoff.
Factual narrative
On February 5, 2021, about 1445 central standard time, a Columbia LC42-550FG airplane, N115FP, was substantially damaged when it was involved in an accident at Pawnee County Airport (LQR), Larned, Kansas. The private pilot and the pilot-rated passenger were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. After conducting a preflight check, the pilot (who was the owner of the airplane) started the engine about 1415, taxied on the airplane to runway 35, and began the takeoff about 1430. After the airplane reached liftoff speed, the pilot felt a “strong” gust of wind and sensed a “stickiness of the plane on the runway.” The pilot stated that this situation was “not normal” and unlike anything that he had experienced while operating the airplane. The pilot decided to abort the takeoff with intermittent braking and reduce thrust to idle. After the aborted takeoff, the pilot taxied the airplane to the runup area for runway 17 and checked the airplane’s flight controls and systems. The pilot reported that “everything inside the cockpit, and what I could see outside appeared and felt normal.” About 1445, the pilot began a takeoff roll on runway 17. The pilot noticed that the airplane was again “sticking to the runway,” so he decided to abort the takeoff. He applied intermittent braking and stated that, about 10 to 20 yards from the departure end of runway 17, the brakes “faded.” The airplane then rolled into a dry grassy area south of the runway. The airplane came to a stop, and the pilot smelled and saw smoke rising behind the right wing. The pilot advanced the throttle enough to move the airplane into a field beyond the runway and shut down the engine. The pilot exited the airplane and saw that the left and right main landing gear were on fire. The passenger then exited the airplane, and the pilot used onboard fire extinguishers to try to contain the fire. Fire trucks arrived and extinguished the fire on the airplane and the nearby grass. The pilot reported that the engine and flight controls were operating normally during both takeoff attempts. The airplane came to rest on a 156º magnetic heading about 250 ft southeast of the end of runway 17. Both main landing gear wheel assemblies, brakes, wheel pants, strut coverings, and brake lines sustained severe fire damage. The underside of the left wing and fuselage were scorched, as shown in the figure below, resulting in structural damage to the left wing. Figure. Fire damage to the main wheel assemblies and underside of the left wing (Source: Federal Aviation Administration). Detailed examination of the airplane showed that both main landing gear brake and wheel assemblies had severe fire damage. The fire appeared to originate from the wheel brakes. Both brake and wheel assemblies were examined and found to be mechanically intact with no anomalies (other than the severe fire damage). The parking brake was not engaged. Flight control continuity was confirmed from the cockpit to all flight control surfaces. The airplane was determined to be under its maximum gross takeoff weight. The pilot attempted two consecutive takeoffs from opposite runways. Both takeoffs were aborted because the airplane would not lift off from the runway. The pilot reported that the engine and flight controls were operating normally during both takeoff attempts. During the second aborted takeoff, the pilot reported that the brakes “faded,” and the airplane departed the end of the runway and entered a dry grassy area. The pilot then noticed that the left and right main landing gear were on fire; the fire resulted in structural damage to the left wing. Postaccident examination of the wheel and brake assemblies revealed no mechanical anomalies. Flight control continuity was established from the cockpit to all flight control surfaces, and the airplane was under its maximum gross takeoff weight. Thus, the reason that the airplane did not lift off during the pilot’s two attempted takeoffs could not be determined from the available evidence for this accident. The fire appeared to originate from the wheel brakes. The time between the two attempted takeoffs was about 15 minutes. The pilot reported that he applied intermittent braking during the first aborted takeoffs. Thus, the brakes likely faded during the second aborted takeoff because they were hot from the consecutive aborted takeoffs and did not have enough time to cool. The fire was most likely caused by the hot wheel brakes entering a dry grassy area after the runway excursion. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
FAA avdata. C = Cause, F = Factor.
- — Aircraft-Aircraft systems-Landing gear system-Brake-Damaged/degraded
- — Personnel issues-Task performance-Use of equip/info-Use of equip/system-Pilot
Verbatim from NTSB's published report. Source file
NTSB_2021_CEN21LA129.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,…