NTSB CAROL · Event
Event WPR24LA071
Registry · N558RA
FAA Aircraft Registry record.
Make / Model
LEARJET INC 55
Year of manufacture
1983 · 41 years old at event
TCDS
A10CE · LEARJET INC
Engine
HONEYWELL TFE-731-SER
Seats / Engines
13 seats · 2 engines
Last airworthiness date
20170804
ADS-B equipped
Yes — Mode-S A71E9B
Registrant of record
BAS PART SALES LLC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The flight crew’s decision to land on a snow-covered runway with a tailwind, resulting in a runway excursion and subsequent impact with terrain. Contributing to the accident, was the failure of the airport authority to plow the runway.
Factual narrative
The pilot in command of the airplane reported that, while on an instrument GPS approach, they listened to the automated surface observing system several times and determined that they would be landing with a “light quartering tailwind” on an upsloping runway. Once clear of clouds and with the runway in sight, the pilot canceled the instrument flight rules clearance, announced their position over the airport’s common traffic advisory frequency and received a reply with a report of 1/4 inch of dry snow covering the runway, unplowed. During the landing roll, they applied brakes, extended spoilers, and thrust reversers. Initially the airplane slowed; however, about halfway down the runway, the airplane’s antiskid system was functioning continuously, and the airplane’s rate of deceleration decreased. The pilot was unsure if the thrust reversers deployed, and he cycled the thrust reversers and did not feel any effects. The pilot stated that, in his experience, the airplane’s thrust reversers do not feel very effective. The pilot considered aborting the landing, started to clean up the airplane but thought it was too late. The airplane overran the departure end of the runway, onto a grass covered area and into a deep ravine, resulting in substantial damage to the fuselage and both wings. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. The automated weather observation station located on the airport reported that, about 44 minutes before the accident, the wind was from 090° at 12 knots. The same automated station reported that, about 16 minutes after the accident, the wind was from 090° at 12 knots. The airplane landed on runway 22. The fixed based operator owner reported that, on the day of the accident, his review of the runway conditions at the airport appeared to be around an inch of snow on the runway surface. Additionally, plowing at the airport so far this year had been “abysmal.” Big windrows and ice chunks have been left; taxiway corners had been built up to the point there could be an occurrence should an airplane be taxiing by. Earlier this year, several departures were delayed due to the runway not being plowed. According to the chairman of the airport board, there is no formal process to conduct runway assessments. However, an airport board member lives in the area and routinely visits the airport to conduct runway assessments. The runway assessments and frequency of the observations are not documented but are conveyed verbally to the airport board via cell phone. To the best of his knowledge, there is no formal snow or ice removal plan. When the runway is required to be cleared, a board member will use county provided equipment to clear the runway. The frequency of the snow removal is not documented. The airport snow removal equipment is limited to clear substance to ½ inch of the runway surface. On the day of the accident, he was not aware of a Notice to Air Misson (NOTAM) issued for the conditions of the runway environment. According to the airplane manufacturer, the estimated landing distance on a dry runway was about 3,350 ft, with loose snow and no tailwind the estimated landing distance was about 6,700 ft, and on loose snow with tailwind, the estimated landing distance was 7,531 ft. According to the Federal Aviation Administration, the airport is not required to have a snow and ice control plan. However, the airport was provided federal funds (grant) to purchase/acquire a snowplow to maintain the airport surfaces during inclement weather conditions. There may be times where issues arise, and action is delayed. In that case it is expected that a NOTAM be issued as outlined in the grant agreement. 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).
- — Personnel issues-Action/decision-Info processing/decision-Identification/recognition-Pilot
- — Personnel issues-Action/decision-Info processing/decision-Identification/recognition-Copilot
- — Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Surface speed/braking-Attain/maintain not possible
- — Environmental issues-Physical environment-Runway/land/takeoff/taxi surface-Snow/slush/ice covered surface-Effect on equipment
- — Environmental issues-Operating environment-Airport facilities/design-Snow removal service/equipment-Response/compensation
Verbatim from NTSB's published report. Source file
NTSB_2024_WPR24LA071.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 (runway excursion). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- NASA NTRS 2013 · Conference Paper
Cockpit Resource Management (CRM) training in the 1550th combat crew training wing
The training program the 1550th Combat Crew Training Wing at Kirtland Air Force Base, New Mexico, implemented in September 1985 is discussed.
- 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.
- arXiv 2025 · arXiv preprint
Aerobatic maneuvers in insect-scale flapping-wing aerial robots via deep-learned robust tube model predictive control
Aerial insects exhibit highly agile maneuvers such as sharp braking, saccades, and body flips under disturbance. In contrast, insect-scale aerial robots are limited to tracking non-aggressive trajecto…
- 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.
Browse the full corpus — academia portal ↗