# Accident 19730730023019A: Piper PA16, Beaver Falls, PA, July 30, 1973

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: July 30, 1973
- Place: Beaver Falls, PA
- Airport: Bever Co
- Damage: Substantial damage
- Phase of flight: Takeoff Ground Roll
- Location: 40.7594° N, 80.3226° W: Placed by OpenAirDocs: center of Beaver Falls, PA, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=40.7594&lon=-80.3226&mi=10
- Aircraft: N5680H, registered now (https://openairdocs.org/aircraft/N5680H) (OpenAirDocs)
- Registry model: Piper PA-16 (registry code 7101602, https://openairdocs.org/model/piper-pa-16) (OpenAirDocs)
- Registry engine: Lycoming 0-235 series (registry code 41505, https://openairdocs.org/engine/lycoming-0-235-series) (OpenAirDocs)
- Reported make and model: PIPER PA16
- People aboard: 3
- Fatal injuries: 0
- Pilot flight hours: 208 total, 208 in this make and model, 1 in the last 90 days
- NTSB investigation: [NTSB NYC74DGM02](https://openairdocs.org/ntsb/NYC74DGM02) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19730730023019A

## Narrative

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

ENCOUNTERED CROSS WIND ON TAKE OFF.

## 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 NYC74DGM02](https://openairdocs.org/ntsb/NYC74DGM02), Jul 30, 1973: Piper PA-16 (N5680H), Beaver Falls, PA, substantial damage

## Other reports on N5680H (1)

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

- [Incident 19860206005459I](https://openairdocs.org/incident/19860206005459I), Feb 6, 1986: Piper PA16 (N5680H), Gahanna, OH. Less than normal power available during local flight. Landed in field. Type of malfunction not reported.

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.