# Accident 19980829022409A: Piper PA30, Dayton, OH, August 29, 1998

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: August 29, 1998, 22:05 local time
- Place: Dayton, OH
- Airport: James M Cox Dayton International
- Damage: Substantial damage
- Operating rules: General operating rules (Part 91)
- Location: 39.7603° N, 84.2103° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=39.7603&lon=-84.2103&mi=10
- Aircraft: N8349Y, a cancelled registration (https://openairdocs.org/deregistered/N8349Y-2017-02-28) (OpenAirDocs)
- Registry model: Piper PA-30 (registry code 7103002, https://openairdocs.org/model/piper-pa-30) (OpenAirDocs)
- Registry engine: Lycoming IO-320 series (registry code 41509, https://openairdocs.org/engine/lycoming-io-320-series) (OpenAirDocs)
- Reported make and model: PIPER PA30
- Fatal injuries: 0
- NTSB investigation: [NTSB IAD98LA104](https://openairdocs.org/ntsb/IAD98LA104) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19980829022409A

## Narrative

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

(.19) ON AUGUST 29, 1998, AT 2205 EASTERN DAYLIGHT TIME, A PIPER PA-30, N8349Y, WAS SUBSTANTIALLY DAMAGED DURING LANDING AT THE DAYTON INTERNATIONAL AIRPORT (DAY), DAYTON, OHIO. THE CERTIFICATED COMMERCIAL PILOT WAS SERIOUSLY INJURED. THE AIRLINE TRANSPORT RATED COPILOT RECEIVED MINOR INJURIES. VISUAL METEOROLOGICAL CONDITIONS PREVAILED FOR THE LOCAL PERSONAL FLIGHT THAT ORIGINATED AT DAY, EXACT TIME UNKNOWN. NO FLIGHT PLAN WAS FILED FOR THE FLIGHT CONDUCTED UNDER 14 CFR PART 91. IN A TELEPHONE INTERVIEW WITH A FEDERAL AVIATION ADMINISTRATION (FAA) SAFETY INSPECTOR, THE PILOT STATED THEY FLEW TO MUNCIE, INDIANA (MIE), FOR PRACTICE LANDINGS, THEN FLEW TO RICHMOND, INDIANA (RID), FOR ANOTHER LANDING BEFORE RETURNING TO DAYTON. THE PILOT STATED THE AIRPLANE WAS CONFIGURED FOR LANDING ON FINAL APPROACH TO DAY AND HE EXPECTED "... A NEAR PERFECT LANDING SINCE THE WINDS WERE CALM." HE SAID HIS NEXT RECOLLECTION WAS WAKING UP IN THE HOSPITAL. IN A TELEPHONE INTERVIEW WITH THE FAA INSPECTOR, THE COPILOT STATED HIS ATTENTION WAS INSIDE THE AIRPLANE AS HE ANNOUNCED "... AIRSPEED, ETC..." TO THE PILOT. HE WAS NOT LOOKING OUTSIDE. THE COPILOT SAID THE POWER INCREASED AND THE "..AIRCRAFT PITCHED UP AND ROTATED LEFT LIKE A VMC STALL." HE REMEMBERED HEARING METAL CRUNCHING AND SEEING THE GROUND THROUGH THE WINDSHIELD. THE AIRPLANE DEPARTED THE LEFT SIDE OF THE LANDING RUNWAY AND CAME TO REST INVERTED. THE AIRPLANE WAS SUBSEQUENTLY MOVED TO A SECURE FACILITY ON DAY FOR EXAMINATION AT A FUTURE DATE. (-23) OWNER/PILOT MADE HARD LANDING, BOUNCED, LOST CONTROL AND CRASHED.

## 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 IAD98LA104](https://openairdocs.org/ntsb/IAD98LA104), Aug 30, 1998: Piper PA-30 (N8349Y), Dayton, OH, substantial damage. Probable cause: the pilot's inadequate recovery from a bounced landing.

## Other reports on N8349Y (1)

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

- [Incident 19880625049119I](https://openairdocs.org/incident/19880625049119I), Jun 25, 1988: Piper PA30 (N8349Y), Winamac, IN. Two engine failures due to fuel starvation. Restarted one and landed. Found foreign matter in crossfeed valve.

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.