CEN17LA009 · Aero Smart Solutions Inc LANCAIR EVOLUTION
Aero Smart Solutions Inc LANCAIR EVOLUTION · Accident: fuel contamination en route
From Allen County Airport (K88) to Ogden Hinckley Airport (OGD)
Event
- NTSB case
- CEN17LA009
- 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 Smart Solutions Inc LANCAIR EVOLUTION
- Aircraft type
- Aero Smart Solutions LANCAIR EVOLUTION
- 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
- N38DM
- Operator
- Aero Smart Solutions
- Onboard fatalities
- Unknown
- Route
- From Allen County Airport (K88), Iola, KSTo Ogden Hinckley Airport (OGD), Ogden, UT
- Aircraft age
- About 3 years (built 2013)
- 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 91: General Aviation
- 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
- En route · climb to cruise
- 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 contamination
- 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 › Aircraft power plant
- Aircraft › Fluids/miscellaneous hardware
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot was flying the airplane in cruise flight at 11,000 ft when the engine lost power. He attempted to restart the engine by switching fuel tanks, turning on the igniters, and holding down the start button but was unsuccessful. He elected to turn back toward the departure airport and feathered the propeller. During the descent, the pilot decided he was unable to make it back to the airport and conducted a forced landing on a dirt road. During the landing rollout, both wings struck trees, which resulted in substantial damage.
Examination of the flight controls, engine, and fuel systems revealed no mechanical malfunctions or failures that would have precluded normal operation. However, fuel samples recovered from the airplane tested positive for water. Data recovered from the engine monitor showed an abrupt power loss that coincided with a loss of fuel flow. The flight instructor who completed transition training with the pilot reported the pilot did not sump the fuel before every flight. Thus, it is likely that the pilot did not perform an adequate preflight inspection and water remained in the fuel system, which led to a total loss of engine power.
The pilot's operating handbook (POH) recommended that the configuration for a forced landing is landing gear up, flaps up, propeller feathered, and airspeed at 110 knots to achieve maximum glide performance. This configuration provides a maximum glide performance of about 500 ft per minute (fpm) descent and about 3.5 nautical miles glide distance per 1,000 ft of altitude lost. Data from the engine monitoring system revealed that, about 3 minutes after the fuel flow stopped and about 2-3 minutes before the accident, the flaps were extended to takeoff position, the airplane achieved 110 kts, and the propeller was feathered. During this time, the rate of descent exceeded 1,000 fpm and was, at times, in excess of 4,000 fpm. The pilot did not mention of the use of an emergency engine-out checklist or consultation of the POH during the event. The pilot's failure to accomplish all of the steps in the emergency engine-out checklist promptly after the loss of engine power led to an accelerated loss of altitude and the subsequent inability to glide to the airport.
Probable cause
Water contamination of the fuel due to the pilot’s inadequate preflight inspection, which led to a total loss of engine power. Contributing to the accident was the pilot’s failure to complete the engine-out checklist, which resulted in an excessive loss of altitude and the inability to glide to the intended airport.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN17LA009
- Event ID
- 20161004X23836
- Case number
- CEN17LA009
- 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, coordinates. 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: ef205421c3edbd2ef287bbdc378bb76b51e3cfa2ec7102b0e9b55685492f76de; retrieved 2026-09-16T04:20:53.284Z.