NTSB CAROL · Event
Event CEN18LA052
Aircraft involved
Probable cause & findings
The pilot's loss of directional control during the rejected takeoff. Contributing to the accident were the pilot's lack of familiarity with the airport runway configuration, which led to his premature attempt to take off, and the airplane’s inoperative landing light.
Factual narrative
On December 24, 2017, about 1740 mountain standard time, a Piper PA-28R-200 airplane, N550D, was substantially damaged during a runway excursion on takeoff from runway 28 (8,204 feet by 150 feet, asphalt) at the Riverton Regional Airport (RIW), Riverton, Wyoming. The pilot and four passengers were not injured. The airplane was registered to Oracle Aviation, LLC and operated by the pilot as a 14 Code of Federal Regulations Part 91 personal flight. Visual meteorological conditions prevailed, and the flight was not operated on a flight plan. The flight was originating at the time of the accident. The intended destination was the Stanford Field Airport (U12), St Anthony, Idaho.The pilot stated that he initially departed from Millard Airport (MLE), with planned fuel stops at Gordon Municipal Airport (GRN) and RIW. After refueling at RIW, the pilot recognized that the landing light was not working. He noted that it was working during the previous flight into RIW. The pilot recalled having good visibility with the runway lights, but he did not have good depth perception. As the airplane approached the intersection with the crossing runway during the takeoff roll, he thought that they were approaching the end of the runway. He rotated the airplane in an attempt to lift off, but the airplane had not gained enough airspeed to become airborne at that point. He decided to reject the takeoff and, as he reduced engine power, he lost directional control and the airplane departed the left side of the runway. The pilot stated that there were no issues with the airplane during the accident takeoff, other than the inoperative landing light. He noted that a functioning landing light and a better review of the airport diagram might have prevented the accident. A review of the available weight and balance data indicated that pilot's calculation was complete and correct, and that the airplane was loaded within limits during the accident takeoff. The airplane was equipped with four seats and seatbelts. The pilot stated that two children occupied one seat and were sharing a seatbelt at the time of the accident takeoff. Federal Aviation Administration regulations do not require a landing light for operations under Part 91 unless they are conducted for hire. However, any inoperative equipment must be deactivated and placarded according to the regulations. The private pilot was attempting to take off and noted that the airplane's landing light was not working. Although the runway lights provided him with good visibility, his depth perception was limited. As the airplane approached the intersection with the crossing runway during the takeoff roll, the pilot thought that the airplane was approaching the end of the runway. He rotated the airplane to lift off, but it had not gained enough airspeed to become airborne, so he decided to reject the takeoff. As he reduced engine power, he lost directional control, and the airplane departed the left side of the runway. The pilot stated that there were no issues with the airplane during the accident takeoff other than the inoperative landing light. He noted that a better review of the airport diagram and a working landing light might have improved his situational awareness during the takeoff. 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 Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot - C
- C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Directional control-Not attained/maintained - C
- F Personnel issues-Task performance-Planning/preparation-Flight planning/navigation-Pilot - F
- F Personnel issues-Task performance-Use of equip/info-Use of charts-Pilot - F
- F Aircraft-Aircraft systems-Lighting system-Exterior lighting-Inoperative - F
Verbatim from NTSB's published report. Source file
NTSB_2017_CEN18LA052.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.
- 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,…
Browse the full corpus — academia portal ↗