CEN18LA332 · Aero Commander S2R
Olsem Aerial Application Service Aero Commander S2R · Accident: runway excursion during takeoff
From Rolling Hills Airport (3MN4) to Rolling Hills Airport (3MN4)
Event
- NTSB case
- CEN18LA332
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Aero Commander S2R
- Aircraft type
- Aero Commander S2
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N5521X
- Operator
- Olsem Aerial Application Service
- Onboard fatalities
- Unknown
- Route
- From Rolling Hills Airport (3MN4), Westbrook, MNTo Rolling Hills Airport (3MN4), Westbrook, MN
- Aircraft age
- About 45 years (built 1973)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 137: Agricultural
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Takeoff
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Runway excursion
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Not determined › Not determined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
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.
Probable cause
A runway excursion during takeoff for reasons that could not be determined based on the available evidence.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN18LA332
- Event ID
- 20180816X05046
- Case number
- CEN18LA332
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 9c7f60f40968adbae7b846082621a8f78148f6a72355561b4b6b0ce48381fca0; retrieved 2026-09-16T08:06:02.492Z.