# Accident 19980927034609A: Piper PA16, Medford, OR, September 27, 1998

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: September 27, 1998
- Place: Medford, OR
- Airport: Rogue Valley International
- Damage: Substantial damage
- Phase of flight: Roll-Out (Fixed Wing)
- Operating rules: General operating rules (Part 91)
- Location: 42.3307° N, 122.7895° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=42.3307&lon=-122.7895&mi=10
- Aircraft: N5932H, a cancelled registration (https://openairdocs.org/deregistered/N5932H-2019-10-05) (OpenAirDocs)
- Registry model: Piper PA-16 (registry code 7101602, https://openairdocs.org/model/piper-pa-16) (OpenAirDocs)
- Registry engine: Lycoming 0-235 series (registry code 41505, https://openairdocs.org/engine/lycoming-0-235-series) (OpenAirDocs)
- Reported make and model: PIPER PA16
- People aboard: 1
- Fatal injuries: 0
- Pilot certificates: Student
- NTSB investigation: [NTSB SEA98LA187](https://openairdocs.org/ntsb/SEA98LA187) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19980927034609A

## Narrative

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

ON SEPTEMBER 27, 1998, AT 1630 PACIFIC DAYLIGHT TIME, A PIPER PA-16, N5932H, REGISTERED TO AND OPERATED BY THE PILOT AS A 14 CFR PART 91 INSTRUCTIONAL FLIGHT, NOSED OVER WHILE TAXIING ON THE RUNWAY AT THE ROGUE VALLEY INTERNATIONAL AIRPORT, MEDFORD, OREGON. VISUAL METEOROLOGICAL CONDITIONS PREVAILED AT THE TIME AND NO FLIGHT PLAN WAS FILED. THE AIRPLANE WAS SUBSTANTIALLY DAMAGED AND THE STUDENT PILOT, THE SOLE OCCUPANT, WAS NOT INJURED. THE FLIGHT HAD DEPARTED ROM ASHLAND, OREGAN, ABOUT 20 MINUTES PRIOR TO THE ACCIDENT. TOWER CONTROL PERSONNEL REPORTED THAT THE PILOT WAS INSTRUCTED TO MAKE A STRAIGHT IN APPROACH TO RUNWAY 32. WHEN THE AIRCRAFT WAS OUT APPROXIMATELY ONE MILE, THE PILOT WAS INSTRUCTED TO GO-AROUND AND SEQUENCE IN BEHIND A LANDING UNITED 737. THE PILOT RETURNED FOR LANDING ON RUNWAY 32. THE UNITED 737 WAS AT THE OPPOSITE END OF THE RUNWAY AND TAXIING BACK ON THE WEST SIDE OF THE RUNWAY WHEN THE AIRCRAFT LANDED. PRIOR OT LANDING, THE PILOT INDICATED TO TOWER PERSONNEL THAT HE WANTED TO LAND LONG, HOWEVER, THE AIRCRAFT TOUCHED DOWN NEAR THE THRESHOLD AND WAS TAXIING ON THE RUNWAY WHEN THE AIRCRAFT SUDDENLY VEERED TO THE RIGHT JUST NORTH OF THE INTERSECTING RUNWAYS AT TAXIWAY A4. THE AIRPLANE NOSED OVER AND CAME TO REST INVERTED. (-23)STUDENT PILOT LANDING AT MEDFORD, OR, LOST CONTROL OF AIRCRAFT WHILE TAXIING TO PARKING.  PILOT CLAIMS HE WAS BLOWN OVER BY UNITED AIRLINES 737.  ATC STATEMENTS AND PILOT STATMENTS DO NOT SUPPORT HIS CLAIM.  WILL REFER TO SPM FOR COUNSELING

## 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 SEA98LA187](https://openairdocs.org/ntsb/SEA98LA187), Sep 27, 1998: Piper PA-16 (N5932H), Medford, OR, substantial damage. Probable cause: Directional control was not maintained.

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.