CEN21LA133 · Aero Commander S2R
Aero Commander S2R · Accident: fuel contamination before flight
From Mid-Valley Dusters Inc Airport (43TX) to an unrecorded destination
Event
- NTSB case
- CEN21LA133
- 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
- N5679X
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Mid-Valley Dusters Inc Airport (43TX), Alamo, TXTo not recorded
- Aircraft age
- About 47 years (built 1974)
- 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
- Prior to flight
- 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
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot departed for the aerial application flight and noticed an abnormal engine sound as the airplane reached an altitude of about 25 ft above ground level. Concerned that the engine could lose power over obstacles further along the departure leg that included a high traffic highway and a low power line, the pilot elected to make an immediate precautionary landing. During the landing roll, both wings sustained substantial damage due to impact with trees.
During postaccident examination of the engine, a small amount of water was observed in the rear carburetor bowl; therefore, it is likely that water-contaminated fuel resulted in a temporary loss of engine power and the abnormal engine sound reported by the pilot. An engine run was conducted with no anomalies noted.
Probable cause
The partial loss of engine power due to water-contaminated fuel.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN21LA133
- Event ID
- 20210223102661
- Case number
- CEN21LA133
- 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, cause areas. 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: 6c09cfb3be47a467c98d725e0a2bd40b1e15efbdfa32aeab8d43f996dcaae25f; retrieved 2026-09-16T13:44:09.922Z.