ATL03LA121 · Lancair 235
Lancair 235 · Accident: total loss of engine power (non-mechanical) on approach
From Isbell Field (4A9) to an unrecorded destination
Event
- NTSB case
- ATL03LA121
- 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
Lancair 235
- Aircraft type
- Lancair 235
- 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
- N7156W
- Operator
- John J Shippey · private individual
- Onboard fatalities
- Unknown
- Route
- From Isbell Field (4A9), Fort Payne, ALTo 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 · VFR pattern final
- First occurrenceThe 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
- Total loss of engine power (non-mechanical)
- 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
- Mixture control, cable › Not connected
- Pilot in command › Maintenance, installation
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
According to the pilot, he removed the carburetor from the accident airplane to troubleshoot another airplane. He reinstalled the carburetor on the accident airplane, and flew it for approximately 20 minutes. While on final approach to land on runway 4, the engine lost power. The airplane collided with trees during an attempted emergency landing. Examination of the engine revealed no mechanical malfunctions. Examination of the carburetor control system revealed that the mixture control cable was not connected. The mixture control arm on the carburetor was in the idle cut-off position.
Probable cause
The pilot's failure to properly reconnect the mixture control cable resulting in a total loss of engine power, and subsequent in-flight collision with the trees.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL03LA121
- Event ID
- 20030801X01250
- Case number
- ATL03LA121
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: fae24344cc7d8c006723d00061087a7c87b46194e0b6ebf552f11c0f4ef61d46; retrieved 2026-09-21T19:24:13.805Z.