# Accident 20000619040469A: Piper PA28180, Selma, CA, June 19, 2000

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: June 19, 2000, 20:00 local time
- Place: Selma, CA
- Damage: Substantial damage
- Phase of flight: Fcd/Prec Ldg From Cruise
- Operating rules: General operating rules (Part 91)
- Location: 36.5291° N, 119.6400° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=36.5291&lon=-119.6400&mi=10
- Aircraft: N32322, a cancelled registration (https://openairdocs.org/deregistered/N32322-2000-11-07) (OpenAirDocs)
- Registry model: Piper PA-28-180 (registry code 7102808, https://openairdocs.org/model/piper-pa-28-180) (OpenAirDocs)
- Reported make and model: PIPER PA28180
- Reported engine: LYC O360*
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 414 total, 275 in this make and model, 10 in the last 90 days
- NTSB investigation: [NTSB LAX00LA235](https://openairdocs.org/ntsb/LAX00LA235) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20000619040469A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

(.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 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.

## The NTSB's investigation of this event (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 LAX00LA235](https://openairdocs.org/ntsb/LAX00LA235), Jun 20, 2000: Piper PA-28-180 (N32322), Selma, CA, substantial damage. Probable cause: The pilot's inadequate preflight planning that resulted in fuel exhaustion and subsequent collision with grapevines during an off airport forced landing.

## Other reports on N32322 (1)

Matched to the same aircraft by N-number and date.

- [Accident 19760818026189A](https://openairdocs.org/incident/19760818026189A), Aug 18, 1976: Piper PA28180 (N32322), Monte Vista, CO, Substantial damage

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
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.