NTSB CAROL · Event
Event CEN18LA332
Aircraft involved
Probable cause & findings
A runway excursion during takeoff for reasons that could not be determined based on the available evidence.
Factual narrative
On August 15, 2018, about 1145 central daylight time, an Aero Commander S2R, N5521X, was substantially damaged during a runway excursion on takeoff from runway 9 at the Rolling Hills Airport (3MN4), Westbrook, Minnesota. The operator stated that the airplane did not climb as expected after takeoff and it encountered a corn field off the end of the runway. The pilot was not injured. The airplane was registered to and operated by Olsem Aerial Application Service as a Title 14 Code of Federal Regulations Part 137 flight. Day visual meteorological conditions prevailed. The local flight was not operated on a flight plan. The flight was originating at the time of the accident.The pilot informed a Federal Aviation Administration (FAA) inspector that he had experienced a loss of engine power at rotation during takeoff. The pilot reported that there were two small rises along the turf runway. The airplane normally became airborne at the second rise. The accident takeoff proceeded normally past the first rise. However, as the airplane approached the second rise, the tail of the airplane dropped to the ground. The pilot perceived a loss of engine power and began to drop the application load immediately afterward. The operator stated that the airplane was fueled before the accident flight and was within the maximum gross weight limitation at the time of the accident. The airstrip was oriented east-west and the accident takeoff was preformed toward the east. A soybean field was located immediately off the end of the runway, followed by a two-lane roadway, and a corn field. The soybean field exhibited evidence of the application load being dropped as the airplane passed over but appeared to be otherwise undisturbed. The airplane continued across the intervening two-lane roadway and traveled about 300 ft into the corn field, leveling the existing 8-foot corn crop, before nosing over and coming to rest. A postaccident examination conducted by FAA inspectors did not reveal any anomalies consistent with a loss of engine power or a failure or malfunction of the flight control system. The airplane was equipped with an engine monitor unit which was recovered from the wreckage and downloaded. A review of the data indicated that the accident takeoff was the fifth of the day. The data revealed a momentary exceedance of the interstage turbine temperature (ITT) on the initial engine start of the day consistent with a hot start event. Otherwise, the engine parameters appeared to be within normal operating limits during the previous flights. The engine was not shutdown between flights. The data revealed that, at the beginning of the accident takeoff, the engine speed increased smoothly from an idle speed of about 64% to 99% over a period of 5 seconds, and it remained at or above 97% for the remainder of the takeoff run. The fuel flow and oil pressure increased in conjunction with the engine speed. The engine torque increased in conjunction with the engine speed and subsequently stabilized at 100% about 35 seconds later. Each of the noted parameters stabilized within normal operating limitations during the takeoff run and were consistent with the engine operating normally at full takeoff power. About 50 seconds after the takeoff began, the engine speed and torque parameters decayed abruptly. The engine speed decreased from 98.3% to zero over a 4-second time interval. The engine torque increased momentarily to 106% before decreasing to zero over the following 3-second interval. The abrupt decrease in engine speed and torque was consistent with the encounter with the corn field. The commercial pilot reported that the airplane experienced a loss of engine power at rotation during takeoff. The airplane cleared a soybean field off the end of the runway and then a two-lane road before entering a corn field on the opposite side of the road. The airplane traveled about 300 ft into the corn field with 8-ft-tall corn before nosing over and coming to rest. A postaccident examination did not reveal any anomalies consistent with a loss of engine power or a mechanical failure or malfunction of the flight control system. Engine monitor data revealed that the accident takeoff was the fifth takeoff of the day. At the beginning of the takeoff, the engine speed and torque increased smoothly to full power. About 50 seconds after the takeoff began, the engine speed and torque decreased abruptly over 3 or 4 seconds consistent with the encounter with the corn field. The distance that the airplane traveled into the corn field was consistent with normal acceleration under full engine power during the takeoff run. The engine monitor data revealed that the engine was producing full power until encountering the corn field with no evidence of a loss of engine power. Thus, because the available evidence indicated that the airplane was operating normally at the time of the accident, the investigation was unable to determine why the runway excursion occurred. 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 Not determined-Not determined-(general)-(general)-Unknown/Not determined - C
- — Environmental issues-Physical environment-Terrain-(general)-Contributed to outcome
Verbatim from NTSB's published report. Source file
NTSB_2018_CEN18LA332.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 ↗