# Accident 19960525019959A: Amtrbd BEDEBD4, Pacific City, OR, May 25, 1996

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: May 25, 1996, 12:15 local time
- Place: Pacific City, OR
- Airport: Pacific City State Airport
- Damage: Substantial damage
- Phase of flight: Level Off Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 45.1902° N, 123.9602° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=45.1902&lon=-123.9602&mi=10
- Aircraft: N239CP, registered now (https://openairdocs.org/aircraft/N239CP) (OpenAirDocs)
- Registry model: Powers BD-4 (registry code 1130603, https://openairdocs.org/model/powers-bd-4) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: AMTRBD BEDEBD4
- Reported engine: LYC O320A2B
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 1,450 total, 300 in this make and model, 7 in the last 90 days
- NTSB investigation: [NTSB SEA96LA097](https://openairdocs.org/ntsb/SEA96LA097) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19960525019959A

## Narrative

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

CROSSWIND GUST BLEW HOMEBUILT LEFT OF RUNWAY ON FLARE. LEFT GEAR LANDED SOFT MUD OFF RUNWAY. CARTWHEELED.

## 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 SEA96LA097](https://openairdocs.org/ntsb/SEA96LA097), May 25, 1996: Powers Bede BD-4 (N239CP), Pacific City, OR, substantial damage. Probable cause: the pilot's inadequate compensation for wind conditions during the landing flare, and his failure to maintain runway alignment, which resulted in an encounter with tall grass beside the intended…

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.