# Accident 20000521006969A: Amtr PIK30, Minden, NV, May 21, 2000

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: May 21, 2000, 14:50 local time
- Place: Minden, NV
- Airport: Douglas County Airport
- Damage: Substantial damage
- Phase of flight: Normal Cruise
- Operating rules: General operating rules (Part 91)
- Location: 39.0091° N, 119.7502° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=39.0091&lon=-119.7502&mi=10
- Aircraft: N30PK, registered now (https://openairdocs.org/aircraft/N30PK) (OpenAirDocs)
- Registry model: Issoire Siren PIK-30 (registry code 8270320, https://openairdocs.org/model/issoire-siren-pik-30) (OpenAirDocs)
- Registry engine: Bombardier ROTAX (ALL) (registry code 09050, https://openairdocs.org/engine/bombardier-rotax-all) (OpenAirDocs)
- Reported make and model: AMTR PIK30
- People aboard: 1
- Fatal injuries: 1
- Pilot flight hours: 2,000 total
- NTSB investigation: [NTSB LAX00LA201](https://openairdocs.org/ntsb/LAX00LA201) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20000521006969A

## Narrative

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

(-23) A POWER (RETRACTALBE ROATX ENGINE), N30PX, LOST LIFT APPROXIMATELY 2 MILES EAST OF THE MINDEN, NV. AIRPORT (MEV). THE PIOLOT, WAYNE MARTIN, ATTEMPTED TO MAKE IT TO RUNWAY 30 BUT LANDED SHORT.  THE GLIDER LANDED IN SAGE BRUSH, TRAVELED 60 YARDS WHERE IT HIT A FENCE.  THE GLIDER WENT THROUGH THE FENCE AND TRAVELED ANOTHER 30 YARDS BEFORE COMING TO A STOP.  A TOW PLANE PILOT, WHO WITNESSED THE ACCIDENT, STATED HE SAW THE ENGINE EXTENDED AS IF THE PILOT WAS GOING TO START IT BUT WHEN THE GLIDER CAME TO REST THE ENGINE WAS STOWED BACK IN THE FUSELAGE.                                         (.4)WHILE RETURNING TO LAND AT THE AIRPORT, WITNESSES SAW THE GLIDER MAKE A SHALLOW APPROACH, AND TOUCHDOWN OUTSIDE OF THE AIRPORT PERIMETER FENCE. THE GLIDER BECAME AIRBORNE AND FLEW THROUGH A FIVE-STRAND BARBED WIRE FENCE. THE TOP TWO STRANDS BROKE THE CANOPY AND STRUCK THE PILOT. COMPILATION OF WITNESS INTERVIEWS REVEALED THAT THE GLIDER APPEARED TOO LOW FOR A NORMAL FLIGHT PATTERN, AND THEY DID NOT THINK THAT THE GLIDER WOULD MAKE IT BACK TO THE RUNWAY. THEY SAW IT DESCEND TO THE GROUND APPROXIMATELY 50 YARDS SHORT OF THE RUNWAY AND COLLIDE WITH THE FENCE. AN INSPECTION OF THE GLIDER REVEA LED NO PREIMPACT ANOMALIES. THE ENGINE WAS ALSO INSPECTED WITH NO DISCREPANCIES NOTED. A GPS UNIT FOUND ONBOARD THE GLIDER WAS REMOVED AND DOWNLOADED; NO INFORMATION WAS AVAILABLE ON THE UNIT.

## 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 LAX00LA201](https://openairdocs.org/ntsb/LAX00LA201), May 21, 2000: Issoire-Aviation PIK-30 (N30PK), Minden, NV, substantial damage, 1 fatal. Probable cause: The pilot's inadequate in-flight planning/decision to attempt to make it back to the runway for landing after experiencing a loss of lift and not maintaining a proper descent rate.

## Other reports on N30PK (1)

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

- [Accident 19950618020679A](https://openairdocs.org/incident/19950618020679A), Jun 18, 1995: Amtr PIK30 (N30PK), Dayton, NV, Substantial damage. Impacted mountainous terrain on glider meet. Was cranking out engine to stabize flight. Blamed downdraft.

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.
