# Accident 20001001015859A: Piper PA32300, Champion, PA, October 1, 2000

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: October 1, 2000, 11:58 local time
- Place: Champion, PA
- Damage: No damage
- Operating rules: General operating rules (Part 91)
- Location: 40.0394° N, 79.3199° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=40.0394&lon=-79.3199&mi=10
- Aircraft: N3039Y, a cancelled registration (https://openairdocs.org/deregistered/N3039Y-2001-02-26) (OpenAirDocs)
- Registry model: Piper PA-32-300 (registry code 7103212, https://openairdocs.org/model/piper-pa-32-300) (OpenAirDocs)
- Reported make and model: PIPER PA32300
- NTSB investigation: [NTSB NYC01FA001](https://openairdocs.org/ntsb/NYC01FA001) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20001001015859A

## Narrative

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

(-23) ON OCTOBER 1, 2000, AT 11:58 LOCAL TIME, A PIPER PA-32-300, N3039Y, WAS DESTROYED WHILE LANDING AT SEVEN SPRINGS AIRPORT (7SP), SEVEN SPRINGS, PA. THE PRIVATE PILOT AND TWO PASSENGERS WERE SERIOUSLY INJURED, AND A THIRD PASSENGER WAS FATALLY INJURED. VFR CONDITIONS PREVAILED AND AN IFR FLIGHT PLAN HAD BEEN FILED FOR THE FLIGHT THAT ORIGINATED FROM WOOD COUNTY AIRPORT (PKB), PARKERSBURG, WEST VIRGINIA. A WITNESS, RIDING HIS BICYCLE ADJACENT TO THE RUNWAY, STATED THE FOLLOWING: HE SAW THE AIRPLANE APPROACH RUNWAY 28, THE AIRPLANE DID NOT SEEM ALIGNED WITH THE RUNWAY AS IT TOUCHED DOWN, AND VEERED OFF THE LEFT SIDE OF THE RUNWAY ONTO THE GRASS. THE ENGINE REVVED AS IF THE AIRPLANE WAS GOING TO TAKEOFF AGAIN, BUT IT VEERED TO THE RIGHT, TOUCHED DOWN BACK ONTO THE RUNWAY, AND TRAVELED OFF THE RIGHT SIDE OF THE RUNWAY. THE ENGINE REVVED AGAIN, AS IF THE AIRPLANE WAS GOING TO TAKE OFF, BUT IT DID NOT CLEAR TREES OFF THE RIGHT SIDE OF THE RUNWAY. AFTER IMPACTING THE TREES, CAME TO REST AT THE BOTTOM OF A STEEP DROP, ABOUT 70 FT BELOW THE RUNWAY.

## 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 NYC01FA001](https://openairdocs.org/ntsb/NYC01FA001), Oct 1, 2000: Piper PA-32-300 (N3039Y), Seven Springs, PA, substantial damage, 1 fatal. Probable cause: The pilot's improper recovery from a bounced landing.

## Other reports on N3039Y (1)

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

- [Incident 19951130046759I](https://openairdocs.org/incident/19951130046759I), Nov 30, 1995: Piper PA32300 (N3039Y), Cleveland, OH. Narrative: pilot thought he had turned to proper runway and did not realize he landed on a taxiway. He did not see number on the runway. Pilot became…

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.