CEN16LA314 · Aero Commander S2R -
Lakeview Aviation Aero Commander S2R - · Accident: fuel exhaustion while maneuvering
From Sanborn, ND to Sanborn, ND
Event
- NTSB case
- CEN16LA314
- 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
- 0
- 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
- N5599X
- Operator
- Lakeview Aviation
- Onboard fatalities
- Unknown
- Route
- From Sanborn, NDTo Sanborn, ND
- Aircraft age
- About 44 years (built 1972)
- 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
- Maneuvering
- 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
- Fuel exhaustion
- 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
- Aircraft › Fluids/miscellaneous hardware
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The commercial pilot reported that, before departure for the agricultural application flight, the airplane was loaded with 300 gallons of water and spray solution and an undetermined amount of fuel was added to the left fuel tank. The pilot did not visually check the fuel tanks during the preflight inspection. After departure, he flew 5 miles south of the private strip and proceeded to spray a 130-acre field. When the spray solution was depleted, the pilot flew back toward the private strip and noticed that the fuel quantity indicators showed 1/4 full in the right tank and 1/8 full in the left tank. The pilot stated that, about 1.5 miles southeast of the private strip and about 400 ft above ground level, the engine "sputtered" and experienced a loss of power. He made a forced landing to a field, and the airplane entered a swampy area and then nosed over. The pilot reported that there were no mechanical malfunctions or failures with the airplane that would have precluded normal operation.
During a postaccident examination of the airplane, no fuel was found in the fuel lines to the engine or in the fuel tanks. Based on the evidence, it is likely that the airplane was not fueled with sufficient fuel to complete the flight and that this, combined with the pilot's failure to check the fuel quantity before departure and ensure that sufficient fuel was onboard for the flight, resulted in fuel exhaustion.
Probable cause
The pilot's inadequate preflight inspection and fuel planning, which resulted in a loss of engine power due to fuel exhaustion.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN16LA314
- Event ID
- 20160809X25153
- Case number
- CEN16LA314
- 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: daefe0f040ef1fd44baeab24edfdc498b7150a8a035595ac835caa44a4100147; retrieved 2026-09-16T04:08:14.589Z.