# Accident 20000730036679A: Piper PA24250, Bluffton, OH, July 30, 2000

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: July 30, 2000, 14:30 local time
- Place: Bluffton, OH
- Airport: Bluffton Airport
- Damage: No damage
- Operating rules: General operating rules (Part 91)
- Location: 40.8898° N, 83.8790° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=40.8898&lon=-83.8790&mi=10
- Aircraft: N5271P, a cancelled registration (https://openairdocs.org/deregistered/N5271P-2001-01-20) (OpenAirDocs)
- Registry model: Piper PA-24-250 (registry code 7102404, https://openairdocs.org/model/piper-pa-24-250) (OpenAirDocs)
- Reported make and model: PIPER PA24250
- People aboard: 1
- Fatal injuries: 1
- NTSB investigation: [NTSB IAD00FA067](https://openairdocs.org/ntsb/IAD00FA067) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20000730036679A

## Narrative

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

(-23) AT ABOUT 2:10 P.M., N5271P CONTACTED BLUFFTON AIRPORT (5G7) BY RAKIO AND ASKED FOR THE ACTIVE RUNWAY. N5271P WAS GIVEN THE CURRENT RUNWAY (RUNWAY 23) AND THE WINDS AT THE AIRPORT. AT ABOUT 2:30 P.M., N5271P CRASHED INTO AN ALREADY HARVESTED WHEAT FIELD ABOUT 3/4 MILE SHORT OF RUNWAY 23. THERE WAS NO POST CRAFT FIRE AND THE PILOT EXPIRED AT THE SCENE.

## 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 IAD00FA067](https://openairdocs.org/ntsb/IAD00FA067), Jul 30, 2000: Piper PA-24-250 (N5271P), Bluffton, OH, substantial damage, 1 fatal. Probable cause: Pilot's improper fuel calculations, which resulted in fuel exhaustion. Also causal, was his abrupt maneuver during the forced landing, which resulted in an inadvertent stall.

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.