SEA03FA124 · Beech A36TC
Beech A36TC · Accident: loss of engine power en route
From Cashmere-Dryden Airport (8S2) to Pangborn Memorial Airport (EAT)
Event
- NTSB case
- SEA03FA124
- 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
- 1 · 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
Beech A36TC
- Aircraft type
- Beechcraft 36
- 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
- N279WP
- Operator
- Gary R. Loveness · private individual
- Onboard fatalities
- Unknown
- Route
- From Cashmere-Dryden Airport (8S2), Cashmere, WATo Pangborn Memorial Airport (EAT), Wenatchee, WA
- 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
- Loss of engine power
- 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
- Substantial
Cause areas
- Fluid, fuel › Starvation
- Fuel system › Unapproved
- Pilot in command › Planning/decision, inadequate
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The modified single-engine, turboprop airplane had a commercial-rated pilot/owner in the right front seat who was the pilot in command (PIC), a private pilot in the left front seat, and a student pilot in the rear seat. The purpose of the flight was to proceed to a nearby airport in order to refuel the aircraft prior to a longer flight back to its home base. According to the private pilot in the left seat, after the engine was started, the after-market, panel-mounted, fuel management system/fuel flow meter indicated a "Fuel Remaining" of 235 pounds, and at that same point in time, the left main fuel tank gauge was at the top of the yellow arc (approximately 15 gallons), and the right main fuel tank gauge needle was at the bottom of the yellow arc (approximately empty). There was no operating restriction indicating the aircraft could not be operated in that fuel configuration. Believing that there was adequate fuel for the flight, the PIC departed for what should have been a flight of ten minutes or less. After departure, a climbing right turn was made followed by the aircraft leveling off approximately 2,000 feet above the terrain, and soon thereafter the right fuel tank "Fuel Low" light came on. About one minute later the engine lost power. The PIC was not able to restart the engine, and therefore found it necessary to execute a forced landing in a wheat field located among hilly terrain. Because there were power lines at the approach end of the field, the PIC was not able to touch down until the aircraft was just past half-way down the field. Although the touchdown was successful, the PIC was unable to stop the aircraft before it exited the far end of the field and rolled/slid into a deep ravine. Subsequent inspections of the airframe, and an inspection/test run of the engine, revealed no system malfunctions. A post-accident review revealed that the aircraft's fuel system had been significantly modified during a major alteration that was never approved by the FAA. As part of the alteration, the route by which the excess fuel in the header tank was rerouted through the fuel system was significantly lengthened, and no approved flight tests had been performed to ensure that, after the alteration, adequate fuel would be supplied to the engine at all attitudes, power settings, fuel load totals, and fuel load distributions. It was also determined that, during the installation of the after-market fuel management system/fuel flow meter by an avionics shop, an incorrect calibration factor was entered in the unit, which would result in displaying an erroneous indication of the amount of fuel used by about 9 percent less than the actual amount. With an unaltered fuel system, the aircraft should have arrived at its destination with about 11 minutes of fuel remaining, and because there were no major alteration-related amendments made to the Pilot’s Operating Manual, the pilot had no way of knowing that the engine would lose power en route.
Probable cause
Loss of engine power due to fuel starvation that resulted from the right wing tank reaching an unusable fuel level. Also causal was an unapproved alteration of the aircraft’s fuel system. Contributing to the accident were the incorrect installation of an aftermarket fuel management system, the presence of power lines at the approach end of the emergency landing area, and terrain unsuitable for a landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA03FA124
- Event ID
- 20030714X01095
- Case number
- SEA03FA124
- 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: d3482a6f3ed3f4499ec9aade40b5721b785eaa36be27fa17ca605b65cab30f0a; retrieved 2026-09-20T19:04:09.912Z.