# Accident 20000729007149A: Piper PA32300, Vernonia, OR, July 29, 2000

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: July 29, 2000, 14:00 local time
- Place: Vernonia, OR
- Damage: No damage
- Operating rules: General operating rules (Part 91)
- Location: 46.0606° N, 123.2702° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=46.0606&lon=-123.2702&mi=10
- Aircraft: N934PH, registered now (https://openairdocs.org/aircraft/N934PH) (OpenAirDocs)
- Registry model: Piper PA-32-300 (registry code 7103212, https://openairdocs.org/model/piper-pa-32-300) (OpenAirDocs)
- Registry engine: Lycoming TI0-540 series (registry code 41533, https://openairdocs.org/engine/lycoming-ti0-540-series) (OpenAirDocs)
- Reported make and model: PIPER PA32300
- NTSB investigation: [NTSB SEA00LA162](https://openairdocs.org/ntsb/SEA00LA162) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20000729007149A

## Narrative

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

(-23) THE PILOT ATTEMPTED AN OFF AIRPORT, SHORT FIELD LANDING. THE A/C WAS NOT DECELERATING AT AN ACCEPTABLE RATE SO THE PILOT INITIATED A GO-AROUND. THE RIGHT LANDING GEAR STRUCK A FENCE POST ON THE BOUNDRY OF THE FIUELD CAUSING IT TO SEPARATE FROM THE A/C. THE SUBSEQUESNT LANDING CAUSED SUBSTANTIAL DAMAGE TO A/C.

## 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 SEA00LA162](https://openairdocs.org/ntsb/SEA00LA162), Jul 29, 2000: Piper PA-32-300 (N934PH), Birkenfeld, OR, substantial damage. Probable cause: The pilot's delayed go-around, which resulted in the aircraft not clearing the fence posts. A contributing factor was the fence posts.

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.