# Accident 19880411009829A: Piper PA28180, Bowling Green, KY, April 11, 1988

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: April 11, 1988, 15:23 local time
- Place: Bowling Green, KY
- Damage: Destroyed
- Phase of flight: Fcd/Prec Ldg From Cruise
- Operating rules: General operating rules (Part 91)
- Location: 37.0599° N, 86.4605° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=37.0599&lon=-86.4605&mi=10
- Aircraft: N32911, a cancelled registration (https://openairdocs.org/deregistered/N32911-1991-04-12) (OpenAirDocs)
- Registry model: Piper PA-28-180 (registry code 7102808, https://openairdocs.org/model/piper-pa-28-180) (OpenAirDocs)
- Reported make and model: PIPER PA28180
- Reported engine: LYC O360A4A
- People aboard: 1
- Fatal injuries: 1
- Pilot flight hours: 500 total
- NTSB investigation: [NTSB ATL88FA138](https://openairdocs.org/ntsb/ATL88FA138) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19880411009829A

## Narrative

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

FORCED LANDING DUE TO FUEL EXHAUSTION. CRASHED IN ROUGH TERRAIN. NO PREFLIGHT OR ENGINE RUNUP. NO MALFUNCTION FOUND

## 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 ATL88FA138](https://openairdocs.org/ntsb/ATL88FA138), Apr 11, 1988: Piper PA-28-180 (N32911), Bowling Green, KY, destroyed, 1 fatal

## Other reports on N32911 (1)

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

- [Incident 19830316019359I](https://openairdocs.org/incident/19830316019359I), Mar 16, 1983: Piper PA28* (N32911), Springfield, TN, Minor damage. Landed 150 feet short of the runway and struck a fence.

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.