# NTSB LAX99LA231: Cessna TU206F, N8728Q, Saline Valley, CA, June 25, 1999

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Limited investigation · Final report
- Date: June 25, 1999, 10:30 local (17:30 UTC)
- Place: Saline Valley, CA
- Phase of flight: [Enroute](https://openairdocs.org/ntsb-phases/400) (OpenAirDocs' grouping)
- Highest injury: No injuries
- Injuries: 4 uninjured
- Status: Completed, report August 14, 2001
- Report: Approved by Office Director
- NTSB case key (mKey): 46746
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=LAX99LA231
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/46746/pdf
- Page: https://openairdocs.org/ntsb/LAX99LA231

## Probable cause

The pilot's failure to verify the fuel quantity prior to departure, which led to fuel exhaustion.

## Sequence of events

In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf).

- Loss of engine power(total) - nonmechanical, cruise
  - fluid,fuel - exhaustion (cause)
  - fuel supply - not verified, pilot in command (cause)
  - refueling - not performed, pilot in command (cause)
- Forced landing, emergency descent/landing
- On ground/water encounter with terrain/water, landing - roll
  - terrain condition - dirt bank/rising embankment
  - terrain condition - rough/uneven

## Analysis

The flight departed its home base, flew to another airport, and was returning home when the engine lost power due to fuel exhaustion.  The pilot reported that he took off originally with full fuel tanks and had not refueled at the en route stop.  He stated that he had the fuel selector positioned to the right tank, but he noticed that both the left and right fuel gauges indicated decreasing amounts of fuel.  The right fuel gauge dropped to 'empty' and the engine suddenly quit.  He switched the fuel selector to the left tank, turned on the boost pump, and the engine restarted. The engine quit again as he was over a group of mountains. The pilot was high and fast during the forced landing to a road and collided with an embankment.  The airplane had been topped off with fuel 2 weeks prior to the accident, but the pilot did not remember if he had flown the airplane in that 2-week period; he did not maintain any type of pilot logbook or flight record.  He thought that the fuel strainer valve had been stuck in the open position, allowing the fuel to drain out.  According to Cessna, fuel cannot be used from both fuel tanks simultaneously, and if the fuel strainer had been stuck open, fuel would drain out only from the tank selected on the fuel selector valve.  The airplane and engine were examined by an FAA inspector, with no mechanical discrepancies found.  The pilot reported that he hadn't experienced any mechanical problems prior to the accident.

## Factual narrative

On June 25, 1999, at 1030 hours Pacific daylight time, a Cessna TU206F, N8728Q, experienced a loss of engine power and collided with ground obstructions during the subsequent forced landing in an open area in Saline Valley, California.  The accident site is about 50 miles southwest of Bishop, California.  The aircraft, owned and operated by the pilot, sustained substantial damage.  The private pilot and three passengers were not injured.  The personal cross-country flight, conducted under the provisions of 14 CFR Part 91, originated from the Bishop Airport earlier the same morning, stopped at the Boulder City, Nevada, airport, and departed about 0945 en route back to Bishop.  Visual meteorological conditions prevailed and no flight plan was filed.

The pilot reported that he took off from Bishop with full fuel tanks (80 gallons).  He estimated that each leg of the flight lasted approximately 1 hour 25 minutes.  He further estimated that with full tanks of fuel, the aircraft's endurance was about 5 hours 20 minutes, with a fuel burn of about 15 gallons per hour.  He stated that during his preflight in Boulder City, he noted that the strainer valve seemed to be binding and stuck after he drained fuel from the main fuel sump.  The pilot reported that he took off with the fuel selector positioned to the right tank, but he later noticed that the left and right fuel gauges were both indicating decreasing amounts of fuel.  He reported that the right fuel gauge dropped to "empty" and the engine suddenly quit.  The pilot stated that when he switched the fuel selector to the left tank and turned on the boost pump, the engine started back up.  He stated that the engine ran for about 3 to 4 minutes before quitting again.  He set up an approach to a dirt road located in a canyon, but came in too high and fast.  The pilot reported that he forced the airplane down to the road and applied full brakes after landing.  The aircraft impacted an embankment that was slightly higher than the wings.  Both wings, the nose gear, and part of the tail collided with the terrain.  The nose gear sheared off.

The pilot reported that after the accident, he noted a small amount of fuel on the ground underneath the main fuel sump.  He stated that it looked like the strainer valve had been stuck in the open position, which allowed the fuel to drain out.

A Federal Aviation Administration inspector from the Las Vegas Flight Standards District Office responded to the accident site.  He reported that he didn't find any mechanical discrepancies with the airplane.

According to the Cessna TU206F Pilot's Operating Handbook, fuel cannot be used from both fuel tanks simultaneously.  A representative from Cessna reported that if the strainer valve had been stuck open, fuel would drain out only from the tank selected on the fuel selector valve.  The Cessna TU206F fuel system schematic confirms that the fuel strainer is positioned after the fuel selector valve.

The pilot supplied a copy of a fuel receipt which reflected that the airplane had been topped off with fuel on June 11, 1999.  He stated that he did not remember if he had flown the airplane between then and the accident flight; he did not maintain any type of pilot logbook or flight record.

The pilot reported that he had not experienced any mechanical problems with the aircraft prior to the accident.

## Aircraft

- Registration: [N8728Q](https://openairdocs.org/deregistered/N8728Q-2007-04-26), registration cancelled 2007-04-26, S/N U20603481, built 1976 (OpenAirDocs)
- Reported make and model: Cessna TU206F
- Registry model: [Cessna TU206F](https://openairdocs.org/model/cessna-tu206f) (registry code 2073353) (OpenAirDocs)
- Registry engine: [Continental TSIO-520 series](https://openairdocs.org/engine/continental-tsio-520-series) (registry code 17040, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: U20603471
- Airframe hours: 2300
- Engines: Continental TSIO-520-C 285 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Registered owner: Ken Kessler
- Airworthiness certificate: Standard, Normal
- Last inspection: Annual, May 21, 1999
- Departed: 61B, BOULDER CITY, NV
- Destination: BIH, BISHOP, CA

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 64; private; airplane ratings: single-engine land; medical: class 3, valid medical--w/ waivers/lim; seat: left; flight hours: 3,100 total, 2,950 in this make and model, 3,100 as pilot in command

## Weather

- Conditions: Visual (VMC), Day
- Wind: 330° at 6 knots
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 90 °F, dew point 36 °F
- Altimeter: 29.00 inHg
- Observed at: BIH, 50 nm away

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 19990625007789A](https://openairdocs.org/incident/19990625007789A), Jun 25, 1999: Cessna TU206F, Death Valley, CA, Substantial damage. Acft ran out of fuel, lost power, made an emergency landing on a dirt road, and sustained damage to both wing tips, propellers, and the nose gear, other…

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.
