FTW02FA070 · Cessna 340A
Cessna 340A · Accident: total loss of engine power (non-mechanical) en route
From SPX · League City, TX to Skylark Field (ILE)
Event
- NTSB case
- FTW02FA070
- 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
- 3 · 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
Cessna 340A
- Aircraft type
- Cessna 340
- 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
- N339S
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From SPX · League City, TXTo Skylark Field (ILE), Killeen, TX
- 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
- En route · cruise
- 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
- Fuel starvation; Tree(s); Wire, transmission
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Fluid, fuel › Starvation
- Pilot in command › Fuel management, improper
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
While on an IFR clearance, the pilot reported to approach control that he was unable to maintain 4,000 feet msl, and did not give a reason. Shortly there after, the pilot contacted approach control and stated that he had "fuel starvation" in the right engine and the left engine had just quit. Radar data depicted the aircraft at an altitude of 3,400 feet. The controller asked the pilot if they were completely without power, and the pilot responded, "yes, we're now gliding." The controller gave the pilot instructions to the nearest airport, which was approximately 4.5 nautical miles away. After passing 2,100 feet, the pilot informed the controller that he would be landing short. During the forced landing, the airplane struck the top of a tree, crossed over a house, struck another tree, struck a telephone wire which crossed diagonally over a street, and then cleared a set of wires which paralleled the street. The airplane then impacted a private residence within a residential area, and a fire erupted damaging the airplane and the private residence. Ten gallons of fuel were drained from the left locker tank, which supplements the left main fuel tank. Examination of the airframe and engines did not disclose any structural or mechanical anomalies that would have prevented normal operation. Examination of the propeller revealed that neither propeller had been feathered.
Probable cause
The pilot's mismanagement of fuel, which resulted in a total loss of engine power due to fuel starvation. Contributing factors were the pilot's failure to follow the checklist to feather the propellers in order to reduce drag.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW02FA070
- Event ID
- 20020125X00132
- Case number
- FTW02FA070
- 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: b63725f60b96ec3dd5580cd147eea9e11f798b6634e77d5d43e1def088512063; retrieved 2026-09-20T20:14:33.045Z.