CHI08CA118 · Luscombe 8A
Luscombe 8A · Accident: fuel contamination on approach
From W53 · Remus, MI to an unrecorded destination
Event
- NTSB case
- CHI08CA118
- 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
Luscombe 8A
- Aircraft type
- Luscombe 8
- 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
- N28403
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From W53 · Remus, MITo not recorded
- Aircraft age
- Not recorded
- 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
- Approach
- 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 from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot reported that during a local flight while on a base leg the engine began running rough. He turned final, applied power, and the engine began running smoothly. The engine then ran rough and smooth again according to the pilot. He said that the airplane contacted the ground short of the runway due to the loss of engine power. He stated that a wing impacted a tree during the landing. The airplane subsequently nosed over. Federal Aviation Administration Inspectors examined the wreckage. A brown varnish like substance was found seeping from the carburetor's fuel line. No further pre-impact anomalies were detected. The pilot reported that he used "automobile" gas and that "some fuel in the gas tank was left over from last year." His safety recommendation was that he "will never use other than fresh fuel [and] will completely drain old gas from tank at end of flying season."
Probable cause
The loss of engine power during approach due to fuel contamination. Contributing to the accident were the unsuitable terrain and a tree.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI08CA118
- Event ID
- 20080602X00769
- Case number
- CHI08CA118
- 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: 3d8318bca2bf876cff53b89a1817f3fb9e17a4f6e4524e836d05119ba909cce3; retrieved 2026-09-15T09:42:50.064Z.