SEA96FA039 · Convair 340
Convair 340 · Accident: total loss of engine power (non-mechanical) on approach
From Phoenix Deer Valley Airport (DVT) to Spokane International Airport (GEG)
Event
- NTSB case
- SEA96FA039
- 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
- 0
- 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
- Instrument Meteorological Cond
Convair 340
- Aircraft type
- Convair 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
- N358SA
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Phoenix Deer Valley Airport (DVT), Deer Valley, AZTo Spokane International Airport (GEG)
- 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 · IFR final approach
- 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
- 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 as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Before the ferry flight, the pilot (PIC) & inexperienced copilot noted the left & right, float-type, underwing, fuel gauges indicated about 3,900 & 4,050 lbs of fuel, respectively. After takeoff, they noted that the cockpit gauges showed an opposite fuel imbalance of 4,100 & 3,600 lbs in the left & right tanks. Due to this indication, the PIC crossfed fuel from the left tank to both engines for about 30 min to rectify the perceived fuel imbalance. Later as they approached the destination, the left tank was exhausted of fuel, & the left engine lost power, although the left gauge indicated about 500 lbs of fuel remaining in that tank. The PIC then crossfed fuel from the right tank to both engines, & left engine power was restored. ATC vectored the flight for an emergency ILS runway 3 approach. The PIC was distracted during the approach & maneuvered the airplane to re-intercept the localizer. About 500' agl in IMC, both engines lost power. During a forced landing at night, the airplane struck a raised berm & was damaged. No evidence of fuel was found in the left tank; 125 gal of fuel was found in the right tank. Unusable fuel was published as 3 gal. During an exam of the engines & fuel system components, no preimpact failure was found. Historical data from the manufacturer indicated that when the airplane had a low fuel state, unporting of fuel tank outlets could occur during certain maneuvers. This information was not in the Convair 340 flight manual, although unporting of the outlets on this flight was not verified.
Probable cause
the pilot's improper management of the fuel/system, which resulted in loss of power in both engines, due to fuel starvation. Factors relating to the accident were: false indications of the cockpit fuel gauges, darkness, and the presence of a berm in the emergency landing area.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA96FA039
- Event ID
- 20001208X05197
- Case number
- SEA96FA039
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1996-01-05.
- API snapshot SHA-256: f5c276d3a83e4eb9b55e196c87e76cea0f5aebcba422310d852bdceedc7fb32f; retrieved 2026-09-21T21:59:07.497Z.