# Incident 19950810031259I: Piper PA30, Corvallis, OR, August 10, 1995

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: August 10, 1995, 11:40 local time
- Place: Corvallis, OR
- Airport: Corvallis Municipal
- Damage: Minor damage
- Phase of flight: Level Off Touchdown
- Operating rules: General operating rules (Part 91)
- Operator: GMDV
- Location: 44.4969° N, 123.2895° W: Placed by OpenAirDocs at CORVALLIS MUNI (CVO), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=44.4969&lon=-123.2895&mi=10
- Aircraft: N8F, registered now (https://openairdocs.org/aircraft/N8F) (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
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 6,000 total, 200 in this make and model, 20 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19950810031259I

## Narrative

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

SINGLE ENGINE PRACTICE. CFI OBSERVE STUDENTS HAND BY GEAR. LOOKED AWAY. STUDENT LANDED GEAR UP.

## Other reports on N8F (2)

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

- [Incident 20090429005639I](https://openairdocs.org/incident/20090429005639I), Apr 29, 2009: Piper PA30 (N8F), Corvallis, OR, No damage. (-23) The pilot in command stated that the left engine of N8F failed during the descent into mcnary field, Oregon. He also indicated that he was using the…
- [Incident 20030128001469I](https://openairdocs.org/incident/20030128001469I), Jan 28, 2003: Piper PA30 (N8F), Corvallis, OR. (-23) During landing approach at Corvallis, Oregon airport, the flap system failed with the flaps at 15 degrees. The aircraft landed without further incident.…

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.
