WPR21LA131
2021-03-15 · Leadore, Idaho, United States · None · 1 aircraft · Status: Completed
Airport U00
Current FAA registration · N886KH
- Make / Model
- CESSNA T210M
- Year of manufacture
- 1977 · 44 years old at event
- Engine
- CONT MOTOR TSIO-520 SER (300 hp)
- Seats / Engines
- 6 seats · 1 engine
- Last airworthiness date
- 19770203
- ADS-B equipped
- Yes — Mode-S AC3508
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The pilot’s failure to attain the proper touchdown point on a graveled surfaced runway with insufficient landing performance and subsequent loss of control during the landing roll.
Factual narrative
On March 15, 2021, about 1030 mountain daylight time, a Cessna T210M airplane, N886KH, was substantially damaged when it was involved in an accident near Leadore, Idaho. The pilot and passenger were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. In a written statement, the pilot described the flight to Leadore Airport (U00), Leadore, Idaho, as smooth and uneventful. After arriving over the airport, the pilot circled runway to determine the wind direction for landing and examine the airport runway surface conditions. After the airplane landed on runway 29, the pilot applied brake pressure. According to local law enforcement, the pilot reportedly landed about 1/3 of the length down the runway at an airspeed of about 80 knots. Shortly after the pilot’s application of brake pressure, he realized the “brakes were not effective” and that he needed to apply more pressure during the landing roll. The airplane subsequently veered to the right, exiting the runway near the departure end. The airplane continued across the airport property impacting a small berm and came to rest near a building. The elevation at U00 is 6,029 ft mean sea level (msl) and runway 29 is a 3,500 ft long “rough”-surfaced runway. Accident site photos revealed that the approach end of runway had freshly mowed bunchgrass, while the remaining runway was covered in deteriorated asphalt and gravel. The first identifiable contact with the runway surface was a set of marks consistent with skidding tires, about 2,600 ft from the approach end of the runway, with about 900 ft of runway remaining. The skid marks continued off the runway and traveled through low sagebrush, impacting a small berm, through a barbed wire fence with metal poles, and ended near the main wreckage. The main wreckage was found about 420 ft from the departure end of the runway. The right main landing gear brake line near the wheel brake assembly was bent downward and separated from the caliper’s B-nut fitting. The horizontal stabilizers and elevators had substantial damage and the left main landing gear collapsed. The flaps were set to about 30°. A postaccident examination of the airplane’s brake system was conducted. The brake pedals were activated and showed no pressure and some residual brake fluid in the system. The right main landing gear brake hydraulic line was separated near the caliper and line fitting. Examination of the separated hydraulic line fracture surfaces were consistent with an overstress fracture. No other anomalies were noted. The Pilot’s Operating Handbook contained landing distance information for a dry, paved surface runway. Investigators calculated the airplane’s landing performance based on ambient temperature, calm wind, zero runway slope, an airplane maximum weight, 6,000 ft msl and flaps at 30°. Estimated landing distance over a 50 ft obstacle and ground roll were 1,710 and 905 ft, respectively. The pilot circled the runway to determine the wind direction and examine the runway surface conditions. The runway surface consisted of deteriorated asphalt and gravel. The pilot reportedly touched down 1/3 the way down the runway and experienced a lack of braking effectiveness. He then pushed the brake pedal to the floor as he neared the end of the runway. The airplane exited the runway near the departure end, continued across the airport property, and impacted a small berm before coming to rest near a building. The first identifiable marks on the runway were skid marks that began 2,600 ft down the 3,500 ft long runway and continued off the runway. Tire marks continued over the rough terrain, over the berm and through a barbed wire fence before where the airplane came to rest. It is likely that the airplane’s brakes were not effective due to the deteriorated asphalt and gravel on the runway surface. Also, it is likely that the pilot applied an abundance of pressure due to the lack of runway remaining, preventing the proper braking for the runway surface condition. During the postaccident examination the right main landing gear brake line was separated near the caliper and line fitting. The line was examined and determined that the fracture surfaces were consistent with an overstress fracture. It likely that the line was damaged during the accident sequence. The pilot’s decision to land long on a gravel runway likely resulted in an inability to maintain control of the airplane during the landing roll. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
FAA avdata. C = Cause, F = Factor.
- — Personnel issues-Action/decision-Info processing/decision-Decision making/judgment-Pilot
- — Aircraft-Aircraft systems-Landing gear system-Landing gear brakes system-Incorrect use/operation
- — Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Surface speed/braking-Capability exceeded
- — Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Directional control-Not attained/maintained
- — Environmental issues-Operating environment-Airport facilities/design-Runway/landing area condition-Effect on equipment
- — Personnel issues-Task performance-Use of equip/info-Use of equip/system-Pilot
Verbatim from NTSB's published report. Source file
NTSB_2021_WPR21LA131.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 (loss of control). All research papers
- 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…
- 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.
- Semantic Scholar 2024 · Article (International Conference on Networking and Services) Risk Assessment of Loss of Control In-Flight Trajectories for Urban Air Mobility Safety
In Urban Air Mobility (UAM), maintaining a minimum separation between aircraft is a safety requirement, which becomes challenging amidst congested air traffic and off-nominal conditions, such as Loss …
- NTSB Aircraft Accident Reports 2022 · Accident report Loss of Control on Takeoff in Icing Conditions — Citation 560XL
Cessna Citation 560XL fatal takeoff icing accident, March 2018. Investigation of a Citation 560XL loss-of-control takeoff accident in icing conditions.
- Semantic Scholar 2021 · Article (Aviation) ANALYSIS OF GENERAL AVIATION FIXED-WING AIRCRAFT ACCIDENTS INVOLVING INFLIGHT LOSS OF CONTROL USING A STATE-BASED APPROACH
Inflight loss of control (LOC-I) is a significant cause of General Aviation (GA) fixed-wing aircraft accidents. The United States National Transportation Safety Board’s database provides a rich source…
- NASA NTRS 2021 · Presentation Use of Design of Experiments in Determining Neural Network Architectures for Loss of Control Detection
Abstract—We describe empirical methods for selecting a neural network architecture to implement belief state inference on generic commercial transport aircraft.