# Accident 20000421009439A: Piper PA36300, Pendleton, OR, April 21, 2000

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: April 21, 2000, 17:45 local time
- Place: Pendleton, OR
- Damage: No damage
- Operating rules: General operating rules (Part 91)
- Location: 45.5709° N, 119.6003° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=45.5709&lon=-119.6003&mi=10
- Aircraft: N82698, a cancelled registration (https://openairdocs.org/deregistered/N82698-2023-04-27) (OpenAirDocs)
- Registry model: Piper PA-36-300 (registry code 7103612, https://openairdocs.org/model/piper-pa-36-300) (OpenAirDocs)
- Reported make and model: PIPER PA36300
- NTSB investigation: [NTSB SEA00LA078](https://openairdocs.org/ntsb/SEA00LA078) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20000421009439A

## Narrative

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

(-23) DURING TAKEOFF FROM LANDING STRIP (19 MILES SW OF PENDLETON, OREGON) THE PILOT ENCOUNTERED A WIND SHIFT ALONG WITH HIGH GUSTS. HE ABORTED THE TAKEOFF BUT LOST DIRECTIONAL CONTROL AND DEPARTED THE RUNWAY, DAMAGING THE RIGHT LANDING GEAR AND THE RIGHT WING TIP. THE A/C SUSTAINED DAMAGE TO THE LANDING GEAR AND FUSELAGE. THERE WERE NO INJURIES.

## 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 SEA00LA078](https://openairdocs.org/ntsb/SEA00LA078), Apr 22, 2000: Piper PA-36-300 (N82698), Lexington, OR, substantial damage. Probable cause: The pilot's failure to adequately compensate for wind conditions upon encountering a wind shift on takeoff. A factor was variable winds.

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.