# NTSB LAX00LA235: Piper PA-28-180, N32322, Selma, CA, June 20, 2000 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: June 19, 2000, 20:00 local (Jun 20, 2000, 03:00 UTC) - Place: Selma, CA - Coordinates: 36.529064, -119.639953 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=36.5291&lon=-119.6400&mi=10 - Phase of flight: [Enroute](https://openairdocs.org/ntsb-phases/400) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report August 21, 2001 - Report: Approved by Office Director - NTSB case key (mKey): 49486 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=LAX00LA235 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/49486/pdf - Page: https://openairdocs.org/ntsb/LAX00LA235 ## Probable cause The pilot's inadequate preflight planning that resulted in fuel exhaustion and subsequent collision with grapevines during an off airport forced landing. ## 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) - preflight planning/preparation - inadequate, pilot in command (cause) - Forced landing, descent - emergency - In flight collision with object, descent - emergency - terrain condition - high vegetation ## Analysis The airplane collided with grapevines during a forced landing following a loss of engine power while in cruise flight. The pilot was in contact with air traffic control just prior to the forced landing and reported he had experienced fuel exhaustion. An examination of the airplane following the accident indicated there was no fuel in the fuel tanks and no evidence of fuel spillage or fuel tank rupture. ## Factual narrative On June 19, 2000, about 2000 Pacific daylight time, a Piper PA-28-180, N32322, collided with terrain following a loss of engine power during cruise flight near Selma, California. The private pilot, the owner and operator of the airplane, and his passenger were not injured. The airplane sustained substantial damage during the forced landing and subsequent impact with grapevines and a fence. The flight was operated under 14 CFR Part 91 and was destined for Ontario, California. The pilot did not file a flight plan but was receiving flight following when the engine lost power. The personal cross-country flight had departed from Eugene, Oregon, approximately 1600. According to the pilot, he was originally going to stop in Merced, California, and found there was no fuel available. He then headed for Visalia, California, and was about 2 miles south of Selma when the engine lost power. In his report, the pilot stated that the engine quit while he was in cruise flight. He stated he completed the emergency engine restart procedure without success. He then attempted to reach the nearest airport, Selma, and force landed in a vineyard. At the time of the engine power loss, the pilot was in contact with Fresno TRACON. He reported to the controller that he had exhausted the fuel. An inspector from the Federal Aviation Administration Fresno Flight Standards District Office examined the airplane on June 20, 2000. Upon arrival at the accident site the inspector checked the airplane's fuel tanks. He stated he did not find any fuel in either fuel tank, and that there was no evidence of fuel spillage or fuel tank rupture. A copy of a fuel receipt indicated that the airplane had been fueled with 37 gallons of 100LL fuel at Eugene, at 1332, on the day of the accident. ## Aircraft - Registration: [N32322](https://openairdocs.org/deregistered/N32322-2000-11-07), registration cancelled 2000-11-07, S/N 28-7505049 (OpenAirDocs) - Reported make and model: Piper PA-28-180 - Registry model: [Piper PA-28-180](https://openairdocs.org/model/piper-pa-28-180) (registry code 7102808) (OpenAirDocs) - Category: Airplane - Serial number: 750504928 - Airframe hours: 1724 - Engines: Lycoming O-360 180 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Registered owner: Bc And Ku Enterprises - Airworthiness certificate: Standard, Normal - Last inspection: Annual, August 11, 1999, 12 hours before - Departed: EUG, EUGENE, OR - Destination: ONT, ONTARIO, CA ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 63; private; airplane ratings: single-engine land; medical: class 3, valid medical--w/ waivers/lim; seat: left; flight hours: 414 total, 275 in this make and model, 10 in the last 90 days, 10 in the last 30 days, 10 in the last 24 hours ## Weather - Conditions: Visual (VMC), Not reported - Wind: 270° at 6 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 190 °F, dew point 142 °F - Altimeter: 29.00 inHg - Observed at: FAT ## 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 20000619040469A](https://openairdocs.org/incident/20000619040469A), Jun 19, 2000: Piper PA28180, Selma, CA, Substantial damage. (.4) On June 19, 2000, about 2000 pacific daylight time, a Piper PA-28-180, N32322, collided with terrain following a loss of engine power during cruise flight… ## Other investigations on N32322 (1) 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. - [NTSB DEN76FTE93](https://openairdocs.org/ntsb/DEN76FTE93), Aug 18, 1976: Piper PA-28 (N32322), Monte Vista, CO, substantial damage 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.