# Accident 20000630012729A: Piper PA28140, Pasco, WA, June 30, 2000

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: June 30, 2000
- Place: Pasco, WA
- Airport: Tri Cities Airport
- Damage: No damage
- Operating rules: General operating rules (Part 91)
- Location: 46.2101° N, 119.1604° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=46.2101&lon=-119.1604&mi=10
- Aircraft: N6887W, a cancelled registration (https://openairdocs.org/deregistered/N6887W-2001-08-09) (OpenAirDocs)
- Registry model: Piper PA-28-140 (registry code 7102802, https://openairdocs.org/model/piper-pa-28-140) (OpenAirDocs)
- Reported make and model: PIPER PA28140
- NTSB investigation: [NTSB SEA00LA119](https://openairdocs.org/ntsb/SEA00LA119) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20000630012729A

## Narrative

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

(-23) I HAD DEPARTED FROM THE WALLA WALLA AIRPORT AT ABOUT 11:18 AM. I WAS TRAVELLING TO HOOD RIVER. ON TAKE OFF I EXPERIENCED A LITTLE ENGINE ROUGHNESS BUT IT CLEARED UP WHEN I LEANED THE MIXTURE. ALL INSTRUMENTS AND ENGINE GAUGES WERE READING NORMAL AND I WAS CRUISING AT ABOUT 6500 FEET MS. AFTER ABOUT 30 MINUTES, I STARTED TO LOSE RPM'S. I AGAIN ADJUSTED THE MIXTURE AND CHECKED FUEL PRESSURES, OIL PRESSURE, AND ENGINE HEAT. ALL WERE NORMAL. THE RPM'S CONTINUED TO DROP AND THE ENGINE STOPPED. I HAD NO INDICATION OF A PROBLEM BEFORE THIS TIME. I HEARD NO UNUSUAL OR LOUD NOISES BEFORE THE ENGINE STOPPED. I WENT THROUGH MY EMERGENCY CHECK, FOUND EVERYTHING NORMAL,A ND TRIED TO RESTART THE ENGINE. THE ENGINE DID RESTART, BUT OIL STARTED COMING OUT OF THE COWLING. TO AVOID THE POSSIBILITY OF AN ENGINE FIRE, I SHUT DOWN THE ENGINE AND TURNED THE FUEL PUMP OFF. I CALLED THE WALLA WALLA TOWER, TOLD THEM I HAD AN ENGINE FAILURE AND WAS GOING TO ATTEMPT A FORCED LANDING. I TRIED TO GIBE THEM MY LOCATION AND ENTERED 7700 ON MY TRANSPONDER. I FOUND A ROAD THAT LOOKED LIKE MY BEST LANDING OPTION AND BEGAN TO SET THE PLANE FOR AN EMERGENCY LANDING. THE OIL WAS CONTINUING TO COME OUT AND WAS C OVERING THE WINDSHIELD, OBSCURING MY VISION. I WAS ABLE TO LAND THE PLANE ON THE ROAD BUT HAD LITTLE OR NO VISIBILITY OUT THE FRONT. MY LEFT WING HIT A ROAD SIGN, WHICH I COULD NOT SEE, CAUSING THE PLANE TO LEAVE THE ROAD AND COME TO REST IN A DITCH BESIDE THE ROAD.

## 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 SEA00LA119](https://openairdocs.org/ntsb/SEA00LA119), Jun 30, 2000: Piper PA-28-140 (N6887W), Kennewick, WA, substantial damage. Probable cause: A failure in the engine's number 1 piston, resulting in a total loss of engine power. Factors included the aircraft windshield being covered with oil (restricting forward visibility), a road sign,…

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.